CRM 4.0 - System Jobs always stuck in "Waiting"

I had just re-isntalled CRM so that I could set it up as an IFD (Internet Facing Deployment) server. Also CRM is set up through an ISA firewall and using SSL. I had to update several fields in the MSCRM_CONFIG database just to get everything to work correctly. I will post another entry with how to get everything workign in IFD mode through ISA correctly.

Now here is what happened.... So one day I was running some test marketing campaign e-mails from CRM and I noticed they were not being sent out. I checkout out the system job page and noticed they were all stuck in the Waiting condition. I tried moving them to Resume but they would just go back into the Waiting condition.

I looked around the web and found out that apparently I had missed a database field update that was not included on the website I found that talked about IFD setup. It's "AsyncSdkRootDomain" and can be found under the DeploymentProperties table.

Here is how to fix it. I have pieced this together from several other people who's pages are linked below.

-Run this SQL command to see your current settings:

Select NVarCharColumn
from DeploymentProperties
where ColumnName='ADSdkRootDomain'
or ColumnName='ADWebApplicationRootDomain'
or ColumnName='AsyncSdkRootDomain';


-You will most like get results that look like this.. where <server> is your server name, and $lt;port> is the port number you are running the CRM website under:

'<server>:<port>'
'<server>:<port>'
''


-Run the follow SQL script to update the value for "AsyncSdkRootDomain". Make sure to replace with your server name and with the port number you are running your CRM website under.

Update DeploymentProperties
Set NVarCharColumn = '<server>:<port>'
Where ColumnName = 'AsyncSdkRootDomain';

-Now restart IIS (open a command prompt and run IISRESET)
-Restart the CRM Async service on the server.

You should be back up and running smoothly.

Here are the articles I read that gave me all the info in this article:
http://www.sadev.co.za/node/155
http://www.themssforum.com/Crm/System-Jobs/

Comments

Post a Comment

Popular posts from this blog

Add User As Local Administrator On Domain Controller

I recently was settting up a new Microsoft SharePoint 2010 machine and had promoted the machine to a domain controller before creating my SharePoint admin accounts.  I needed to add several of my accounts to the local Administrators group.  Unfortunately after you promote a server to a domain controller you can no longer access the GUI for Local Users and Groups.  Instead I had to use the command line to add the users. Open a command promt using the "Run as administrator" function and then run the following command. net localgroup Administrators /add {domain}\{user} Note: do not include the {} brackets.
Read more

Calling Dataverse Web API in PowerShell using Client Credentials

Image
Connecting to Dataverse using PowerShell can be very helpful for data migrations and use within Azure DevOps. Connecting to an instance in a non-interactive way can be tricky though. This article will provide you the links you need for creation and App registration and adding the app user to your environment. You can then utilize the script provided to call Web API requests including ones you define using the new Custom API functionality now available. The script was written so that it is not dependent on any outside libraries such as the Microsoft.Xrm.Tooling connector. This is helpful in situation where involving an outside library will slow down your deployment time by having to be approved in a change control board. If utilizing an outside code library is not a concern you can create a connection to Dataverse utilizing the Microsoft.Xrm.Tooling connector Get-CrmConnection cmdlet. Create App Registration The first thing to do is create an App Registration within Azure AD for
Read more

Windows Server 2008R2 VMs Shut Down After 1 to 2 Hours

Image
When created a lab environment to test ADFS 2.0 I utilized the Windows 2008R2 VM baselines distributed by Microsoft.  After a few days I was told that I had to activate.  The VMs included a 180 day license for use but I didn't feel like adding another network adapter into Hyper-V to connect them to the internet.  I started having issues though where the servers would shut down every hour or so.  I though that maybe there was a memory issue and Hyper-V was shutting them down in order to free up RAM.  Turns out that if Server 2008R2 is not activated it automatically shuts down after a period of time.  After connecting the server to the internet and activating them the problem went away. Finally the madness of the unknown shut downs has ended :)
Read more