Unable to Send Email Messages using Microsoft.Exchange.WebServices Library

Ihor Kuliiev 131

Hello!

I've been using Microsoft.Exchange.WebServices 2.2.0 library to send emails from my C# application for a couple of years and have not been changed my code for a long time.

It worked seamlessly but yesterday I started constantly getting the following exception on Microsoft.Exchange.WebServices.Data.EmailMessage.Send() method call:

"Microsoft.Exchange.WebServices.Data.ServiceResponseException: The operation can't be performed because the item is out of date. Reload the item and try again."

Could you please advise why this may happen and what possible ways are to resolve this?

Thank you in advance!

Jake Zhang-MSFT 2,635 Reputation points Microsoft Vendor

2024-05-23T07:23:44.1133333+00:00

Hi @Ihor Kuliiev,

Looks like your issue is more related to development, please kindly understand that the Exchange Server tag here we mainly focus on general issues about Exchange Server. In order to better solve your problem, we will add "Exchange Server Development" tag.

Best，

Jake Zhang
Kavindra Uniyal 5 Reputation points

2024-05-23T09:12:52.84+00:00

@Ihor Kuliiev, Have you come across a solution for this problem? I am also encountering same issue from today where it works only 3 out of 10 times, and the remaining 7 times, I receive the same error "The operation can't be performed because the item is out of date. Reload the item and try again."
ArosHamlet 10 Reputation points

2024-05-23T10:46:54.3833333+00:00

Edit: Message sent prematurely, no delete button. Please remove this comment.
ArosHamlet 10 Reputation points

2024-05-23T11:11:59.8666667+00:00

Having similar issues on our end. Years long integration suddenly collapsed with the extremely lackluster explanation that "item is out of date".
Daniel Thielman 90 Reputation points

2024-05-23T11:50:32.2366667+00:00

I manage an application for 20+ separate customers that all use their own separate Exchange services, and this issue started occurring at a low volume on 5/20 and has steadily increased in impact. This is absolutely an issue with the Exchange services.
Konstantin Gapeev 1 Reputation point

2024-05-23T12:11:38.4133333+00:00

Same issue for me.

Googling shows the issue also appeared in the past, for example: https://stackoverflow.com/questions/61892649/exchange-web-services-sending-email-error-item-is-out-of-date
Daniel Thielman 90 Reputation points

2024-05-23T17:56:38.7566667+00:00

Message from MS:

I would like to inform you that we have recently integrated the High-Volume Email (HVE) feature into the Exchange Admin Center under mail flow, which has inadvertently affected the functionality of some third-party applications. Please accept our sincerest apologies for any inconvenience this may have caused you. We understand how important these services are to your daily operations, and we are committed to resolving this issue promptly.Our product team is actively working on a solution to ensure that the third-party applications are fully working as it should. We are making every effort to address this as quickly and efficiently as possible.
SHAIK Nagur M 0 Reputation points

2024-05-24T07:31:21.0866667+00:00

Hi, @Jake Zhang-MSFT We also facing the same issue for the past 2 days. Could you please provide a solution?
Lukas Kindig 5 Reputation points

2024-05-28T07:57:13.7233333+00:00

@Daniel Thielman where did you get this response? Was the issue resolved for you, or did you implement a workaround? Because for us sending is still failing sometimes.

3 answers

David Barrett 21 Reputation points Microsoft Employee

2024-05-29T10:41:26.7366667+00:00

The error message is telling you what the issue is - the item that you have a copy of has been updated on the server in the meantime, so your copy is stale and needs to be reloaded. You'll get this error if the ChangeKey you send in your request does not match the ChangeKey of the item on the server.

This is something that needs to be handled by the client (by reloading the message, or simply retrying the request with the up-to-date ChangeKey).
Please sign in to rate this answer.

2 people found this answer helpful.
John Frandolig 20 Reputation points

2024-05-29T14:15:21.46+00:00

And how would you do that if you are using the Microsoft Outlook COM Model as above (Mailitem.Send() ) ? (edited to correct api call: REF: https://video2.skills-academy.com/en-us/dotnet/api/microsoft.office.interop.outlook._mailitem.send?view=outlook-pia#microsoft-office-interop-outlook-mailitem-send - I have customers reporting a similar error with this call also, but I cannot seem to duplicate, though I can duplicate the EWS one.

David Barrett 21 Reputation points Microsoft Employee

2024-05-30T09:23:04.5466667+00:00

That's a different issue, as it's a different API. I'd suggest to raise a support case for this.
Sign in to comment
Richard Procter 5 Reputation points

2024-05-24T14:19:54.4533333+00:00

Exact same problem here, a solution that is many years old began failing intermittently on 23 May. Messages sent without an attachment always work fine, but those with attachments fail 50% of the time with this message.

Another forum has suggested a possible workaround of updating code to first save the message in drafts folder, then retrieve and send from drafts. We are going to try that next.
Please sign in to rate this answer.

1 person found this answer helpful.
Rob F 0 Reputation points

2024-05-24T14:25:54.0866667+00:00

We implemented this workaround earlier today and we haven't had any failures since it was deployed.
Sign in to comment
Rob F 0 Reputation points

2024-05-23T10:16:34.8766667+00:00
We are seeing the same issue - since this morning. Before today it has worked seamlessly for us for years.

In our case, we save the message to the 'Drafts' folder, so that we can get an InternetMessageId and retrieve the MIME content of the message before sending.

// if we need to load extra content if (loadContent) { // save email to drafts message.Save(); // load the mime content of the email message.Load(new PropertySet(ItemSchema.MimeContent, EmailMessageSchema.InternetMessageId)); } // send the email, and move it to SentItems message.SendAndSaveCopy();

If we skip that step, the messages appear to send.

This does not fix the problem for us, we do need the MIME content.
Please sign in to rate this answer.
David Joyce 150 Reputation points

2024-05-23T10:24:31.73+00:00

Hi Rob,

Thanks for your update, we were already going straight to SendAndSaveCopy() and it is intermittent but more frequent today - the same as Kavindra. We have also tried saving into the SentItems but this has not helped.

Any other suggestions would be appreciated.
Sign in to comment

Share via

Unable to Send Email Messages using Microsoft.Exchange.WebServices Library

3 answers