Archive for the ‘Email Router’ Category
Email Router – CRM Field Guide Chapter 5
December 17th, 2012This chapter is designated Field Guide Triple XXX. It is week 5 in the review of the CRM Field Guide chapters from the book – The CRM Field Guide – How to CRM like an MVP with Microsoft Dynamics CRM. This week it is the 42 page Email Router chapter.
As I mentioned at the start of the blog this chapter is rated Triple XXX. What is a Triple XXX CRM Field Guide book rating? This is a chapter than you will end up using 3 times as follows:
- First read to get an understanding into the subject matter: what the component does, is it right or necessary for your environment and the general requirements to make it work.
- During the installation and configuration process
- Troubleshooting implementations that were working but then just stopped.
Let’s get a glimpse (just some teasers, we want you to buy the book) into what the chapter offers up in each of the three categories.
1. Understanding – At some point in every implementation the subject of Do I need the Email router comes up between the client and the CRM partner. As much as we would like give a succinct – Yes you do, no you don’t response, it usually can’t be responded to so simply. When CRM was first released (~2003, V 1.2) the email router was positioned primarly as the way call center users could send out email, tag it in CRM, but not have to use the Outlook Client. Call center personell usually didn’t have Outlook at their disposal. Over the years that seems to have moved from being the typical justification to just another possible example scenario. The author has a very nice introduction into why and why not use the router and where and when it fits and where and when it doesn’t fit. Part of the explanation is summed up in the following graphic from the chapter.
CRM 2011 Email Router – Do I need it?
2. Installation and Configuration – the email router reminds me of the old dial up modem configuration days, you either had the settings right or you didn’t and it isn’t like horseshoes, close doesn’t count. The functioning of the email router is generally a binary process – it either works or it doesn’t work. Besides walking you through step by step with screen shots and the fill in the blank responses for the configuration settings there is some great guidance on how many profiles you should set up and when to use or not use the Mail Forwarding approach in the Rule Deployment Wizard.
CRM 2011 Email Router Configuration
3. Troubleshooting – If you follow the step-by-step directions in the chapter you will see that the configuration of the router can be a fairly simple process. However, since the router is an application that is designed to fit between CRM and a variety of email systems, there are several areas where complications can occur. Rather than just a collection of troubleshooting tips, this chapter provides them in a methodology that can be used to determine the root cause and resolve it. Did you know that there was an router logging function that can be enabled and where those log files are written? You will have you get the book and read this chapter.
CRM 2011 Email Router Enable Logging
We had successfully setup the email router for CRM 2011 in an IFD-ADFS environment for a client and then some weeks later it stopped working. No workflow generated emails were leaving the system.
Their event log looked as follows with MSCRMEmail errors appearing every few minutes.
On inspection of the error details we viewed the following:
#26234 – The E-mail Router service could not process a provider work item using assembly: Microsoft.Crm.Tools.EmailProviders.dll and class: Microsoft.Crm.Tools.Email.Providers.SmtpPollingSendEmailProvider. System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. —> System.ServiceModel.FaultException: ID3242: The security token could not be authenticated or authorized. — End of inner exception stack trace —
Server stack trace: at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]: at Microsoft.Crm.ServiceProxyCache`1.BuildServiceProxy(Uri serviceUrl, Credential credentials, Uri homeRealmUrl, String passportEnvironment, String onlineServiceEnvironment, IServiceConfiguration`1 serviceConfiguration) at Microsoft.Crm.ServiceProxyCache`1.GetNewServiceProxy(Uri serviceUrl, Credential credentials, Uri homeRealmUrl, String passportEnvironment, String onlineServiceEnvironment) at Microsoft.Crm.Tools.Email.Providers.Utility.GetOrganizationUrl(Uri discoveryServiceUrl, Credential credentials, String organizationName) at Microsoft.Crm.Tools.Email.Providers.Utility.GetCrmService(Uri discoveryUri, String authMode, String userName, String password) at Microsoft.Crm.Tools.Email.Providers.CrmPollingSendEmailProvider.Run() at Microsoft.Crm.Tools.Email.Agent.ServiceCore.ExecuteProviderWork(Object providerQueueRequestObject
When you Bing the following: crm 2011email router id3242: The security token could not be authenticated or authorized you get 10 results:
The second listing looked the most promising so we went to this page: http://social.microsoft.com/Forums/en/crmdeployment/thread/6465166b-8ef4-4240-9601-0cf08178b209
However, we know from experience that changing the AFDS\Service\Endpoints Username to enabled is not the action to take as it has proven to break the Outlook integration. So we then read a posting later down the page by XAirrick suggesting that the username & password on the Deployment tab of the Email Router be verified.
We then were hit with a stroke of brilliance – let’s update the password for the User. Guess what – that fixed it.
Solution – set the password never to expire in Active Directory for the Access Credential account being used to authenticate to CRM.
