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

86 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-10-10T19:18:31+00:00

    Kristin,

    1. Is this happening for all outgoing mail or just some of them?  Are they new messages or replies?
    2. Is there anything unusual about the messages (images, size, attachments, etc.)
    3. Is that error message from an pop-up alert?  If you go to "Window" -> "Sync Errors" do you see one or more of the same error?
    4. Are any rules being run that could be moving messages around?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-10-10T21:37:55+00:00

    Hi John

    In my case (and two other people in the team

    1. some.  Generally replies
    2. nothing unusual as far as we can tell and no obvious shared characteristics
    3. Pop up Alert.  Repeats a couple of times then isn;t an issue anymore
    4. No rules in operation

    thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-10-10T22:17:34+00:00

    Is there anything in "Window" -> "Sync Errors"?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-10-11T16:19:03+00:00

    Hi John,

    1. It's random. Sometimes new messages, sometimes replies. Sometimes only to another internal user, sometimes to external users. No pattern there.
    2. Nope. Again, totally random. Sometimes just a single line of text, other times there's a small attachment. No pattern here.
    3. The error is a smaller, black overlay that appears on screen in its own alert box, but not a traditional Mac OS pop-up alert. You don't need to hit "OK" or anything to dismiss (just the small close "x" in the top-right corner). It doesn't give the full error. To see the full error, I have to go to Window > Sync Errors. When I do, there are multiple errors (one for each error throughout the day/or until the user closes Outlook and restarts it). Same error over and over.
    4. No rules in play.

    I've contacted Microsoft. Their "solution" was to uninstall Office 2016 and delete and cache files, etc. associated with Office 2011 or 2016. Then reinstall Office 2016, setting up "new" from scratch. I did this. It made no difference. They asked me to do it again. It made no difference.

    Thanks,

    Kristin.

    Was this answer helpful?

    0 comments