System Jobs all ways going to waiting status

System Jobs that are triggered in Microsoft Dynamics CRM are not processed and remain in a waiting state.

This problem occurs because of the following cause:

Cause :

The Async service cannot connect to the server. By default, the AsyncSDKRootDomain field in the DeploymentProperties table is left blank. This means, when the Async service tries to connect to the server, it uses the loopback address of 127.0.0.1. However, the CRM Web site is now using an assigned IP address, the Async service cannot connect to the server.

To resolve this problem, follow these steps:

  1. Make sure that a HOST (A) record has been created in DNS and point to the IP address assigned to the CRM Web site.
  2. Download the Deployment Configuration tool.

    For more information, click the following article number to view the article in the Microsoft Knowledge Base:

      (http://support.microsoft.com/kb/949079/ ) How to use the Microsoft Dynamics CRM Deployment Configuration tool for Microsoft Dynamics CRM 4.0

  3. Extract the Deployment Configuration tool, and put it in the location on the CRM server.
  4. Back up the MSCRM_Config and OrgName_MSCRM databases.
  5. At command prompt, path out to the directory that contains the microsoft.crm.deploymentconfigtool.exe file, and then run the following commands to correct this setting:

microsoft.crm.deploymentconfigtool asyncsettings update -sdkrootdomain:<IPADDRESSOFTHECRMWEBSITE>

microsoft.crm.deploymentconfigtool addresssettings update -webapprootdomain:<IPADDRESSOFTHECRMWEBSITE>

microsoft.crm.deploymentconfigtool addresssettings update -sdkrootdomain:<IPADDRESSOFTHECRMWEBSITE>

Note <IPADDRESSOFTHECRMWEBSITE> is a placeholder for the actual IP address that is assigned to the CRM Web site.

To confirm the IP address, follow these steps:

  1. Open IIS Manager and locate the CRM Web site.
  2. Right-click the CRM Web site, and then click Properties.
  3. On the Web Site tab, notice the IP Address that is set in the IP Address field.

    So, the command should resemble the following:

    microsoft.crm.deploymentconfigtool asyncsettings update -sdkrootdomain: 192.167.0.0

    microsoft.crm.deploymentconfigtool addresssettings update -webapprootdomain: 192.167.0.0

    microsoft.crm.deploymentconfigtool addresssettings update -sdkrootdomain: 192.167.0.0

    1. Reset IIS. To do this, click Start, click Run, type iisreset, and then click OK.
    2. Existing Microsoft CRM Outlook clients may not reconnect to the server. To correct this problem, follow these steps:
  4. Close Outlook on the Microsoft Dynamics CRM client computer.
  5. Click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Configuration Wizard.
  6. Follow the configuration wizard and make sure that the new name of the HOST record mentioned in step 1 is defined.
    1. Make sure that Kerberos is passing correctly.
    2. Make sure that you add the IP address and the new HOST name in the Local intranet zone of the Internet Explorer options. To do this, follow these steps:
  7. Open Internet Explorer.
  8. On the Tools menu, click Internet Options.
  9. On the Security tab, click Local Intranet, and then click Sites.
  10. Click Advanced.
  11. In the Add this Web site to the zone field, enter the CRM IP address, HOST name, and FQDN of the HOST name. For example, http://crmwebsiteipaddress.
  12. Click Add.
  13. Close the Local intranet window.

Comments

Popular posts from this blog

MS CRM 4.0 Relationship Mappings Error

Open Data Protocol

Using Read-only versus const