Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
getting a 'Pending Send' email to send - debugging CRM Email Router RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    New installation of CRM 2011 RU4 on Windows Server 2008 R2.   CRM, E-Mail Router, SQLServer each on its own Windows server.

    We've deployed some code into CRM OnPremise 2011 RU4.    In advanced find I see one Pending Send email.

    I have tried everything to configure the email router to get it to send.  I still see (from Advanced Find) the one Pending Send email, and though I've enabled tracing, no trace information is appearing in Event Viewer.

    I see in CRMEmail hosts's event viewer, about every second:

    MSCRMEmail Event ID: 31826 - Refreshing configuration settings

    I have the "Log On As' for the Microsoft CRM Email Router Windows OS service set to a service account.  The service account is a member of PrivUserGroup.  It is a System Administrator role in CRM, and its 'E-mail access configuration' is set to 'E-mail Router' for Incoming and Outgoing.

    When I deployed the MS CRM Email Router config manager setting, I specified Exchange 2007 and 'Windows Authentication' for the Authentication method for both incoming and outgoing profiles.

    A big concern is that seeing no tracing information.  I have given the account full control permissions for HKLM\system\currentcontrolset\services\eventlog and I've set to 3 the HKLM\SYSTEM\CurrentControlSet\Services\MSCRMEmail LogLevel value, and the Microsoft.Crm.Tools.EmailAgent.xml's file's LogLevel to 3.  But when I restart the Microsoft CRM Email Service I still see no MSCRMEmailLog Windows Log - still just 'Application', 'Security', 'Setup', 'System', and 'Forwarded Events'

    What can I try next ?


    Wednesday, October 5, 2011 5:52 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    It sounds dumb, but whenever I run into this problem, I use a domain admin (if you have one set up as a CRM user) in both profiles and in the deployment. If that works, you know it's a permissions issue, and can troubleshoot that more specifically.

    That's assuming that you've confirmed the inbound functionality, so you know the email router is doing something (is active).

    HTH,

    Andy

    Blog: http://andrewbschultz.com @andrewbschultz
    Tuesday, October 11, 2011 2:22 PM