Today I was configuring the Email Router with Incoming profile – Access Credentials as “User Specified“.
After setting up the new Deployment, I fetched out the views of the Users and their respective mailboxes. But For a single user when I selected the “Test Access” button, it showed the following Error:
Incoming Status: Failure – The E-mail Router service configuration parameter “EmailUser” is missing. This parameter is required.
I even checked the log in Event: It stated the following error details
#26090 - An error occurred while opening mailbox email@example.com.
System.Configuration.ConfigurationErrorsException: The E-mail Router service configuration parameter "EmailUser" is missing. This parameter is required.
at Microsoft.Crm.Tools.Email.Providers.ConfigNodeReader.GetCheckedStringValue(String elementName, String defaultValue, Boolean throwIfMissing, Boolean hide)
at Microsoft.Crm.Tools.Email.Providers.ConfigNodeReader.GetCheckedStringValue(String elementName, String defaultValue, Boolean throwIfMissing)
After some reading I found the reason for this Error. It was because CRM was not configured to use the credentials to send and receive email messages. Therefore, Email Router does not have the user name and the password to retrieve the mail.
To resolve this issue we need to enable CRM to send and receive e-mail on your behalf, Follow these steps:
1> Start the Dynamics CRM Web Client.
2> On the front Page Click File -> Tools -> Options
3> On the Email tab, click to select the check box “Allow Email router to use my credentials to send and receive email on my behalf”
4> Type the User Name and Password correctly
User Name : Domain\UserName
Password: <Domain Login Password>
5> Click Ok.
The option of “Allow Email router to use my credentials to send and receive email on my behalf” is only available when you have selected the Email Access Type-Incoming as ‘Email Router’ (Settings -> Administration -> Users)
In case you find this option grayed out, Kindly follow my Next Post.
After clicking on ‘OK’ the Page will refresh and Now while testing the access in Email router, no such error will show up again.