One of my users is experiencing issues when tracking emails.
When they try to select a contact in the set regarding field they get the following error report.
Microsoft Dynamics CRM Error Report Contents
<Message>Could not complete the operation due to error 800a139e.</Message>
<BrowserUserAgent>Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; Microsoft Outlook 14.0.6131)</BrowserUserAgent>
<ClientName>Outlook Laptop - Online</ClientName>
The event viewer also logs this sometimes
An error occurred retrieving data from the Microsoft CRM server for processing Microsoft CRM-related e-mail messages. Not all CRM-related e-mail messages may be marked appropriately. Verify that the current user has appropriate permissions and server connectivity and try the action again. HR=0x80131501. Context=. Function=CEmailTagger::Run. Line=410.
They have the same permissions as others in the organization but the other users do not encounter the errors.
What happens when the email is tracked with the track button instead of Set Regarding?
If they just click track it seems to work alright. Although sometimes the little tracking icon doesn't show up in outlook. However, if you go into the customer record, it was indeed tracked.
Try setting the Privacy preference to Automatically Send error reports to Microsoft.
Navigate to Settings --> Administration --> Privacy Preferences to do this.
Thank you for using Microsoft Dynamics Online Communities,
I was wondering if you were able to find a solution to this issue?
Even one of my users is facing this issue and happens to be the only one. Other users having the same role has no issues tracking emails.
This is the message in the event viewer:
An error occured retrieving data from the microsoft crm server for processing microsoft crm-related e-mail messages.Not all crm-related email messages may be marked appropriately.Verify that the current user has appropraite permissions and server connectivity and try the action again.
Did you find a resolution to this problem?
I have the same error.