locked
All system jobs are waiting RRS feed

  • Question

  • Hi...

    Today, I tried to import some data into crm using Import wizard. 
    After submitting the import, the status reason is showing as Submitted for long time. I double clicked on that and looked at the system jobs and found the status reason of the three jobs as Waiting.
    I checked that Crm Asyn service is running and I restarted it.
    After that I checked all the system jobs and to my surprise all the system jobs have satus reason as waiting for the last 1 week.
    Previously I was able to import data.

    Can anyone have an idea of why am I unable to import the data and why all these system jobs are having status reason WAITING???
    I never faced this kind of issue and your ideas on this is really appreciable!!!


    -Thanks






    Thursday, April 2, 2009 3:45 PM

Answers


  • I fixed the issue with the following change in the DB.


    Database name: MSCRM_CONFIG
    Update DeploymentProperties SET NVarCharColumn = '<server>:<port>' WHERE ColumnName = 'AsyncSdkRootDomain'
    ex: Update DeploymentProperties SET NVarCharColumn = 'MyCrmServer:80' WHERE ColumnName = 'AsyncSdkRootDomain'



    -Thanks
     Dinesh,
     RampIndia.


    • Marked as answer by Perfectionist Friday, April 3, 2009 11:20 AM
    Friday, April 3, 2009 11:09 AM

All replies

  • Hi -

    There is a set of instructions here:
    http://blogs.msdn.com/benlec/archive/2009/02/10/how-to-troubleshoot-system-jobs-failures-using-advanced-find.aspx


    These will help retrieve the 'reason' for the waiting state - Ben also provides some information on other reasons / potential solutions -The failure is possibly that the Asynchronous Service cannot contact the CRM Web Services because of a bad configuration. It could be configuration within the MSCRM_CONFIG database or in the Server MSCRM Registry Hive -  see the configuration details for more information.

    Please have a look at the following articles for more information and for potential solutions:

    950416    System Jobs are in a waiting state and Outlook clients cannot connect after you set the CRM Web site to an assigned IP address
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;950416

    947423    How to update the Microsoft Dynamics CRM Web site port after you install Microsoft Dynamics CRM 4.0
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;947423

    950542    Synchronous plug-ins do not respond to the events that are triggered in Microsoft Dynamics CRM 4.0
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;950542


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    • Marked as answer by Jim Glass Jr Thursday, April 2, 2009 5:12 PM
    • Unmarked as answer by Perfectionist Friday, April 3, 2009 11:20 AM
    • Unmarked as answer by Perfectionist Friday, April 3, 2009 11:20 AM
    Thursday, April 2, 2009 3:54 PM
    Moderator
  • Scott, thank you very much for your quick reply.
    I will take a look at them and ping you if I still have any issues.
    Thursday, April 2, 2009 4:02 PM
  • http://blogs.msdn.com/benlec/archive/2009/02/10/how-to-troubleshoot-system-jobs-failures-using-advanced-find.aspx

    Hey, I followed the above link and checked out by using advanced find and the error messages are different from that mentioned in that link.

    Error message:
    "The operation has timed out at System.Web.Services.Protocols.WebClientProtocol.GetWebresponse(Webrequest request) at System.Web.Services.HttpWebClientProtocol.GetWebresponse(Webrequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsofoft.Crm.SdkTypeProxy.CrmService.Execute(Request Request) at Microsofoft.Crm.Asynchronous.SdkTypeProxyCrmServiceWrapper.Execute(Object reuest) at Microsoft.Crm.Asynchronous."


    Any ideas???
    Thursday, April 2, 2009 4:25 PM
  • That's a fairly generic timeout error - do you have any plugins or workflows on the object(s) you are importing?

    Also are there any SQL issues / timeouts that you've experienced?
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, April 2, 2009 4:30 PM
    Moderator

  • I fixed the issue with the following change in the DB.


    Database name: MSCRM_CONFIG
    Update DeploymentProperties SET NVarCharColumn = '<server>:<port>' WHERE ColumnName = 'AsyncSdkRootDomain'
    ex: Update DeploymentProperties SET NVarCharColumn = 'MyCrmServer:80' WHERE ColumnName = 'AsyncSdkRootDomain'



    -Thanks
     Dinesh,
     RampIndia.


    • Marked as answer by Perfectionist Friday, April 3, 2009 11:20 AM
    Friday, April 3, 2009 11:09 AM
  • I would encourage you to NOT update the config database directly via SQL - rather, The supported method of updating your deployment is to use the Microsoft Dynamics CRM Deployment Configuration tool provided here http://support.microsoft.com/kb/949079/ 

    The Microsoft Dynamics CRM Deployment Configuration tool is a command-line executable program. You can use this tool to update the values in the Microsoft Dynamics CRM configuration (MSCRM_Config) database. Additionally, you can use this tool to send notifications to all the Microsoft Dynamics CRM servers to use the values that you updated.

    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Friday, April 3, 2009 3:20 PM
    Moderator
  • Hi Perfectionist

    I am facing teh same problem

    I updated the DeploymentProperties  but it didnt work for me

    is there something that i am missing do let me know

    Thanks


    Pradnya07

    Monday, May 7, 2012 1:01 PM
  • Hi Pradnya,

    Which version of CRM you are working on? Is it MS CRM 4.0 or 2011?

    Do you have the latest rollup installed? Restart the Microsoft CRM Asynchronous Processing Service once.


    Perfectionist
    wwwdotdinesh.blogspot.com

    Monday, May 7, 2012 1:49 PM
  • Also check the other column names in the Deployment Properties table and do an update if it is null.

    USE MSCRM_CONFIG
    Update DeploymentProperties SET NVarCharColumn = ‘SERVER:PORT‘ WHERE ColumnName = ‘AsyncSdkRootDomain’
    Update DeploymentProperties SET NvarCharColumn = ‘SERVER:PORT‘ WHERE ColumnName = ‘ADSdkRootDomain’
    Update DeploymentProperties SET NvarCharColumn = ‘SERVER:PORT‘ WHERE ColumnName = ‘ADWebApplicationRootDomain’


    Perfectionist
    wwwdotdinesh.blogspot.com

    Monday, May 7, 2012 1:53 PM
  • Hi I am using CRM 4.0 i have updated teh CRM to roll up 21

    Restarted teh Asyn service but no progress


    Pradnya07

    Tuesday, May 8, 2012 8:12 AM
  • Hi Perfectionist;

    This the result of the query

    ADRootDomainScheme HTTP
    ADSdkRootDomain BLUEOWEB1:5555
    ADWebApplicationRootDomain BLUEOWEB1:5555
    AsyncSdkRootDomain BLUEOWEB1:5555
    IfdRootDomainScheme HTTP
    IfdSdkRootDomain theblueorchid.co.uk
    IfdWebApplicationRootDomain theblueorchid.co.uk


    Pradnya07

    Tuesday, May 8, 2012 8:15 AM
  • Hi ;

    I just found that my workflows are actuaaly working but they show status reason as waiting in the system jobs

    Can you please help regarding the same

    Thanks

    P


    Pradnya07

    Tuesday, May 8, 2012 11:42 AM
  • Follow the steps in the below link and check for the Error Message.

    http://wwwdotdinesh.blogspot.in/2012/03/ms-crm-workflows-waiting-and-failed-how.html

    Try restarting SQL services as well.

     


    Perfectionist
    wwwdotdinesh.blogspot.com

    Wednesday, May 9, 2012 9:36 AM