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
    2017-07-20T16:43:29+00:00

    Seems issue is back or not all the O365 servers have been patched.

    Just got a customer report from July 13 on our own application using EWS to send messages.

    Same error message.

    We had reports in the past on this, and issue had disappeared around mid-May

    Any recent change on this subject ?

    BR

    JPL

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-04-13T16:35:59+00:00

    Per the team that did the fix, it should be rolled out pretty much world wide at this point (save a few straggler machines).  Let me know if you are still seeing this behavior.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-04-13T14:37:57+00:00

    Different issue, different team, same error code.  The responsible folks have reverted the change and are validating that it fixes the issue.  It is a race condition that was not caught during automated testing.  Ill check with the team today to see what the status is of the rollout.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-04-13T13:27:13+00:00

    Same thing here (I'm the OP on this never-ending thread).

    Issue has been resolved for a few months, but as of yesterday, I'm getting multiple users complaining about the issue resurfacing. Same error code and other details as last time.

    Great job MS.

    k.

    Was this answer helpful?

    0 comments No comments