Issues with CRM 4.0 Client for Microsoft Outlook on Terminal Server: CRM Add-in Disabled
Posted Monday, January 26th, 2009
Symptoms: The CRM 4.0 Client for Microsoft Outlook works when first configured for a user on a terminal server, but when the user logs off and logs back on, the CRM add-in for Outlook is disabled. The user then receive the following message:
WarningDiagnosticCheckException: You recently used a different Outlook profile than the one the Microsoft Dynamics CRM add-in has been configured for. The Microsoft Dynamics CRM add-in will be enabled only for the profile it was configured for. at Microsoft.Crm.Outlook.Diagnostics.
Background: The CRM 4.0 Client for Microsoft Outlook gets successfully installed to the terminal server by an administrator. An end user then logs in and successfully configures the client, and the CRM 4.0 Client for Microsoft Outlook performs as expected. Once the user logs off and logs back on, the CRM add-in for Outlook is disabled.
Cause: The server was configured with Login scripts that are clearing the outlook profile without checking a condition it is already there. Another login script is then running to configure Outlook for the user without any user input. The CRM 4.0 Client for Microsoft Outlook realizes this upon initialization and disables the CRM add-in for Outlook.
Solution: Be sure that your terminal server login scripts, or files, called by those login scripts are checking to see if the Outlook profile for the user that is logging in exists and does not remove and recreate a profile if one already exists.
Tags: AddIn Disabled, Outlook Client Issue, Terminal Server
Posted in Dynamics CRM, Outlook Client, Script and Code
Need Expert Help With Microsoft CRM?
Get the support you need to effectively manage your business.
Learn more about our Microsoft CRM support options
Please give the detail solution.
Thanks