W
01/26/2011 14:37:15 : #6188 - The E-mail Router service cannot connect to the Microsoft Dynamics CRM server or the Microsoft Dynamics CRM Live server to access user and queue information. Verify that the account that is used to run the E-mail Router service
has sufficient permission to access the Microsoft Dynamics CRM server and that there are no connectivity problems. System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable
to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)
--- End of inner exception stack trace ---
at Microsoft.Crm.Tools.Email.Management.Deployment.LoadUsers(BackgroundWorker backgroundWorker, List`1 newRecipients, Dictionary`2 recipientsWithOverride, Dictionary`2 recipientsDisabled)
at Microsoft.Crm.Tools.Email.Management.Deployment.Load(BackgroundWorker backgroundWorker)
at Microsoft.Crm.Tools.Email.Management.Configuration.UpdateAll(Boolean refreshDeployments, String configurationSettingsFilePath, String configurationFilePath)e have just deployed update rollup 15 in an environment and this has resulted in the
CRM email router not fetching info from the server.
We have tried un-install and re-install and working up through the updates and nothing works. We then put the CRM email router on another machine and this;
worked without update rollups
worked with update rollup 7
Broke with update rollup 15
Removing, striping from the registry and file system and re-installing does not resolve the issue.
Nothing in the server application log even though we have debugging on the router set to level 3
Any ideas?
