S
ShaneTen
Guest
Environment: On Premise Exchange 2010 SP3 Rollup 25
Client: Outlook 2016
Issue: On any new profile that is being created and after clearing the auto-correct cache by performing it via Outlook - File - Options - Mail - Empty Auto-Complete List and also Outlook.exe /CleanAutoCompleteCache. The first mail sent internal or external works, but then when you select the recipient from the drop down list the second time we receive the following error "The operation failed. The messaging interface have returned an unknown error. If the problem persist, restart Outlook. Cannot resolve recipient."
If the address is added to the Outlook Address book by - right clicking on the email - add to Outlook outlook contact - then the error message is not displayed at all. Having to add the address to the Address Book is not a solution, but a workaround we are currently using.
Additional info: This issue is only experienced for clients that are on premise, If a client is connected externally using OutlookAnywhere the issue is not present.
Has anyone experienced this before. That can point me in the correct direction.
Continue reading...
Client: Outlook 2016
Issue: On any new profile that is being created and after clearing the auto-correct cache by performing it via Outlook - File - Options - Mail - Empty Auto-Complete List and also Outlook.exe /CleanAutoCompleteCache. The first mail sent internal or external works, but then when you select the recipient from the drop down list the second time we receive the following error "The operation failed. The messaging interface have returned an unknown error. If the problem persist, restart Outlook. Cannot resolve recipient."
If the address is added to the Outlook Address book by - right clicking on the email - add to Outlook outlook contact - then the error message is not displayed at all. Having to add the address to the Address Book is not a solution, but a workaround we are currently using.
Additional info: This issue is only experienced for clients that are on premise, If a client is connected externally using OutlookAnywhere the issue is not present.
Has anyone experienced this before. That can point me in the correct direction.
Continue reading...