Microsoft Dynamics CRM 2011 hassles: asynchronous processing service stopped

I installed Microsoft Dynamics CRM 2011 a few days ago – rarely a straightforward task, thanks to Active Directory dependencies and the complexities of Windows security. There also seem to be unfixed bugs in the setup. For example, I always find that the trace directory is incorrectly configured and has to be fixed via PowerShell, even with a new install on a new installation of Windows Server 2008 R2.

Never mind. This time I came across a new problem. After a successful install, users reported errors in scheduled jobs and imports. An attempted import resulted in the message Waiting for Resources.

The problem was that the two CRM Asynchronous Processing Services were not running. Start them manually, and everything works.

The event log reported Event ID 7000 after the last reboot – “the service did not respond to the start or control request in a timely fashion”.

The solution in my case was to set the start action on these services to Automatic (Delayed Start). They now start OK after a reboot.

I suspect this problem may be related to update rollup 12, since the very same problem appeared on another Dynamics CRM 2011 install after applying this.

I also wonder if the fact that SQL Server is on the same VM is related. If CRM starts before SQL Server is fully running, you get this kind of problem.

2 thoughts on “Microsoft Dynamics CRM 2011 hassles: asynchronous processing service stopped”

  1. Hi Tim,
    Interesting points. I am a CRM consultant and work with CRM all the time. I too noticed that the CRM Asynch services are not starting in many of the environments that I work with after Rollup 12 applied. So far my observations are on development type environments where the Asynch services are not used heavily (go to sleep?) AND after reboots where they simply fail to start?

    Be keeping an eye on this and if Rollup 13 makes any difference?

  2. Hi,
    I am not sure if this is the right place to post this query but I’m looking for some expert advise on a similar issue.

    We are currently using CRM Dynamics 2011 and are new.

    We have just implemented CRM campaign distributions We have a strange issue on our production where campaign distribution stops at a particular time every night – exact on the same time. If its a large campaign it’s expected to run through the night but it never achieved to do so as it keeps failing at that time.

    Checked all the below:
    1. Any locks on the tables – none at that time.
    2. Tried to find if there were any restarts of Async services but could find in the Event viewer.
    3. Checked database, application and Async running servers’ event logs but couldn’t find any.

    Although I/O on the database server is very high during that time. We have CRM daily job running at the same time though. But no locks found.

    Is there any default Async service restart set in Dynamics 2011?

    Any advice on this is much helpful.


Comments are closed.