locked
Outlook 2016 The messaging interfaces have returned an unknown error RRS feed

  • Question

  • Hello,

    We have Exchange 2016 with latest CU and Outlook 2016 clients on single terminal server all in online mode.

    Sometimes some users (several times a day) experience the following error when they try to send messages previously saved in drafts or return to recently opened and/or minimized messages with some text, recipients and subject already filled (it looks like attachment does not play any role here) when press Send button:

    The operation failed. The messaging interfaces have returned an unknown error. If the problem persists restart Outlook"

    After they try to save it Oulook drops another error:

    "The function cannot be performed because the message has been changed"

    Leaving user with only one choice - to completely re-create the message and to copy all the text/recipients/subject from the old one.

    I already tried most common solutions from the internet:

    1. Google or any other calendar - not our case at all - none of the users has any external calendars connected in outlook

    2. Currupted pst file - again not our case as all clients are connected only in Online mode.

    3. Re-create Outlook profile - does not help either. The problem arises after several hours.

    4. Run outlook in safe mode - also does not help.

    Terminal server is fully patched windows server 2012 R2 VM

    Please advise.

    Thank you in advance!

    Nikolay


    Friday, May 17, 2019 11:28 AM

All replies

  • Hi,

    This is a known issue and the Outlook Team is investigating this issue.

    There is a workaround for you:

    1. Go to File > Options > Mail.
    2. In the Save Messages section, either clear the Automatically save check box or increase the amount of delay time (10 minutes or more) before items are autosaved into Drafts.

    Hope this can be helpful.

    Regards,

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, May 20, 2019 7:04 AM
  • Hi,

    Please remember to mark the replies as answers if they helped.
    And if you need further assistance on this, please feel free to post back.

    Regards,

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, May 24, 2019 8:23 AM
  • Dear Aidan,

    Many thanks for your answer! I've tried to change this setting to 13 minutes however the problem still persists.

    Do you have any other suggestions?

    Regards,

    Nikolay

    Friday, May 31, 2019 10:47 AM
  • Hi Nikolay,

    Thanks for your updates.

    Please install the latest updates and see there is any difference.

    Regards,

    Aidan Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    Monday, June 3, 2019 8:15 AM
  • Hi Aidan,

    Thank you for your reply - no luck unfortunately yet: I've installed CU12 for Exchange 2016 and all available Windows+Office updates on terminal server where Outlook is used. The problem still happens.

    Regards,

    Nikolay

    Thursday, June 13, 2019 6:35 AM
  • Hi, 

    We are facing the same issue in a Outlook 2016 environment with Exchange Server 2017 CU12. 

    Has the known issue been resolved?

    Is there a KB article I can monitor for when a solution is made available?

    Regards,

    Denis

    Monday, March 16, 2020 11:25 AM