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.