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: Most helpful
  1. Anonymous
    2016-10-13T21:57:23+00:00

    Hi all,

    We have enough logs now, thank you.  Our preliminary analysis shows that the issue lies in the Exchange server.  We are working with the server team to get this fixed as soon as possible, but don't have any timelines at this point.  Thanks for your patience.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-10-13T21:36:22+00:00

    Hi John,

    I have experienced the same problem since 3 or 4 Oct.

    I have switched on logging - can I send you the logs when the error occurs?

    Regards,

    Henri

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-10-13T18:48:03+00:00

    Yes, I've just sent you a private message so you can attach the logs.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-10-13T17:29:49+00:00

    John- 

    I have my logging turned on and I just had the error message pop up. Would you like me to send the log files to you? 

    Thanks,

    ~Riika

    Was this answer helpful?

    0 comments No comments