In the CRM 2011, sometimes you have to use the user credentials to access to the mail box. When the check box to allow that in the CRM is not editable. Please follow the following article: Microsoft KB
Cause:
In processing e-mail for a user or queue, the E-mail Router requires credentials for the user or queue. Those credentials can be entered in the Microsoft Dynamics CRM Web application in the Set Personal Options dialog box (for users) and in the Queues form (for queues). Microsoft Dynamics CRM stores these credentials in encrypted form in the CRM database. The E-mail Router uses a key stored in the CRM database to decrypt these credentials. The call that the E-mail Router makes to obtain this key enforces HTTPS. In Microsoft Dynamics CRM 2011, the E-mail Router functions this way by default, which means that you need not take any action to retain this behavior.
Resolution:
To resolve the above issue, please follow the below steps to add the registry key “DisableSecureDecryptionKey” on the CRM server.
Launch the registry editor on the CRM server by clicking “Start”, “Run” and type “regedit”
Locate the following path on th CRM server : HKEY_Local_MachineSoftwareMicrosoftMSCRM
Please check the value of the registry key “DisableSecureDecryptionKey”. If this registry key is present, set its value to 1. (If the key is not present or set to 0, calls from the E-mail Router to the Microsoft Dynamics CRM Server 2011 are made using HTTPS.) Setting the value of this key to 1 allows the E-mail Router to obtain information from the CRM database over the HTTP protocol.
If you changed the value of DisableSecureDecryptionKey, do the following on the Microsoft Dynamics CRM Server 2011 to Restart Internet Information Services (IIS). To perform the same click on “Start”, click “Run”, type “cmd, and then click OK.
Type the following in the command prompt window “IISRESET”
(Recommended) Enable IPSec for all communications between the Microsoft Dynamics CRM Server 2011 and the E-mail Router computer. For more information about enabling IPSec, see IPSec
.
Comments