Error -19761 when sending mail (The send or update operation could not be performed because the change key passed...)

Anonymous
2016-10-04T16:13:47+00:00

I’m having a problem with one user in our system. Details are as follows:

Platform: OS X 10.10.5

Outlook version: Outlook for Mac 2016 (15.26.1)

Problem: Randomly (about 5-10 times through the work day), when the user sends an email, they get an error in Outlook for Mac, the message is not sent, and the message is put in their Drafts mailbox. The error that is displays is as follows:

The send or update operation could not be performed because the change key passed in the request does not match the current change key for the item., Cannot submit message.SaveStatus: IrresolvableConflict


PropertyConflicts: Mail could not be sent. The message has been moved to your Drafts folder.

Account name: "XXX"

Error: -19761

They then open the message from their Drafts folder and attempt to resend it. It then sends without issue.

Some additional notes:

  • The error started happening 2 days ago—no changes were made to the user’s machine prior to the error appearing.
  • The error happens when sending to both internal and external contacts.
  • The error only happens when using Outlook for Mac desktop client (the issue does not happen when sending mail via OWA or iPhone, etc.)
  • We have updated Outlook for Mac to the latest available version (15.26.1).
  • We have deleted/re-added the account in Outlook.
  • We have uninstalled/reinstalled the Office 2016 package on the computer.

Any advice would be appreciated.

Thanks,

Kristin.

Outlook | MacOS | Legacy Outlook for Mac | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

86 additional answers

Sort by: Newest
  1. Anonymous
    2016-10-12T23:55:04+00:00

    I am having the same issues for the last week or so. I just upgraded to 15.27 (161010) and I am running OSX 10.10.5. Its random for me too. But only happening on one Office 365 Exchange account consistently (I have three total Exchange accounts in this Outlook profile). 

    The send or update operation could not be performed because the change key passed in the request does not match the current change key for the item., Cannot submit message.SaveStatus: IrresolvableConflict

    PropertyConflicts:

     Mail could not be sent. The message has been moved to your Drafts folder.

    Error code: -19761

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-10-12T18:15:52+00:00

    I just got reports of the same issue this morning. It appears to have started sometime last week so it's not something with Patch Tuesday yesterday (this client doesn't run updates regularly anyways). Outlook 2011, we're getting the 19812 error. 

    They did get a weird meeting notifications way out of date (it's Oct, it was from March, that they accepted and it borked Outlook) last week that caused a corruption with their Outlook profile, we had to go into Webmail and remove the meeting and emails associated with it as it was emailed back and forth a bit between the two people having the issue.

    But they can't correlate the issue since it's been a week now since this issue started.

    Any new information on resolution would be great. I'm glad someone deleted their profile and started over already as a remedy because this client has huge Outlook profiles and it'd take quite a bit of time to rebuild.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-10-12T17:27:29+00:00

    I enabled logging on this user's machine first thing this AM (before they arrived) and will let it run throughout the day. Will gather the logs tomorrow AM and send to you (disabling logging at the same time).

    Thanks,

    Kristin.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2016-10-12T00:15:49+00:00

    I have 2 users with this exact issue as well. One on Outlook 2011 and one on Outlook 2016.

    Was this answer helpful?

    0 comments No comments