Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
System Jobs not running RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a clean installation of CRM 4.   It is not an upgrade.  It is, however, migrated from another instance of CRM 4.  IFD has been applied.  I'm on the latest patch release.  The OS is Windows Server 2008 64 bit.

    My system jobs are in a waiting status and will not run.    I've read all of the other posts and have tried the updates to the database on the 3 values.  They are all crm.pccdr.org:80.   That has not worked.    I'm getting this error in the trace file.

    >Exception while trying to execute AsyncOperationId: {F9C286D5-1901-4350-B5C1-C7F90845BFDD} AsyncOperationType: 12 - System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.Crm.SdkTypeProxy.CrmService.Execute(Request Request)
       at Microsoft.Crm.Asynchronous.SdkTypeProxyCrmServiceWrapper.Execute(Object request)
       at Microsoft.Crm.Asynchronous.DuplicateDetectionCacheLoader.LoadCacheData(Guid key, IOrganizationContext context)
       at Microsoft.Crm.Caching.BasicCrmCache`2.CreateEntry(TKey key, IOrganizationContext context)
       at Microsoft.Crm.Caching.BasicCrmCache`2.LookupEntry(TKey key, IOrganizationContext context)
       at Microsoft.Crm.Asynchronous.PersistMatchCodeOperation.InternalExecute(AsyncEvent asyncEvent)
       at Microsoft.Crm.Asynchronous.AsyncOperationCommand.Execute(AsyncEvent asyncEvent)
    [2011-01-05 08:31:00.5] Process:CrmAsyncService |Organization:32ef82e3-750d-e011-bcb9-0022197b567e |Thread:    9 |Category: Platform.Async |User: 00000000-0000-0000-0000-000000000000 |Level: Error | AsyncOperationCommand.Execute
        at AsyncOperationCommand.Execute(AsyncEvent asyncEvent)
        at PoolHandler.ProcessAsyncEvent(AsyncEvent asyncEvent)
        at PoolHandler.InvokeHandlerInPool(Object state)
        at ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
        at _ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
        at _ThreadPoolWaitCallback.PerformWaitCallback(Object state)

     

    I've tried running the service as Network Service and as Administrator.    Nothing is working without this.  Would appreciate all advice.

     

     

    Wednesday, January 5, 2011 4:30 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Can you please explain what steps you took for the installation and migration.  My first thought is that something occurred during this process, "It is, however, migrated from another instance of CRM 4", that caused the application to be unstable.

    I'm assuming your reference to "service" in your last sentence is regarding the Async service and that it is not running.  Is that correct?  Can you ensure that your Organization is enabled in the Deployment manager and all of your Server settings are correct as well.

    Regards, Donna

    Wednesday, January 5, 2011 5:29 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    I've had this problem once, after migrating from one to another server, what solved my problem was changing the account under which sql server agent was running. 
    Wednesday, January 5, 2011 6:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I followed the migration instructions.   The migration itself went pretty well.   By migration, I mean we moved the instance from one server to another.  Installed the software, imported the data, created the new organization following the instructions for that.

     

    Yes, the service I'm referring to is the async service.    The organization is enabled.  Everything else works just fine.   One can hook up with Outlook, use the web interface, etc.   The only thing not working is the async system jobs/workflows.

    Wednesday, January 5, 2011 9:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can you elaborate on how you changed it?    I have a SQL Service user that is the owner of all SQL related things.   The owner of the CRM install is Administrator.   The Async service runs under Network Service.

    Can you tell me what to try changing it to?

     

    Thank you all for your help.  It is appreciated.

    Wednesday, January 5, 2011 9:15 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Since the system jobs are run by SQL server agent service, log on your server and in Services see if this service is running and under which account. Under which account is this service running?
    Wednesday, January 5, 2011 9:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The MS Async Service is being run by "Network Service".   The SQL server services are all run by PCCDR\SQLservice

     

     

    Wednesday, January 5, 2011 10:31 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Here as a link. Here you should find the answer for Sql Server Agent service account.

    http://msdn.microsoft.com/en-us/library/ms143504.aspx#Use_startup_accounts

     

    In my case I changed the sql server agent service account to Local SYstem and the problem was solved.

    Wednesday, January 5, 2011 11:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks.  Does it matter that the SQL Server and the CRM are on the same server?

     

    Wednesday, January 5, 2011 11:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I changed both the SQL Server agent and the MS CRM Async to Local Service.    I'm still getting the same error.

     

    [2011-01-05 17:57:41.4] Process:CrmAsyncService |Organization:32ef82e3-750d-e011-bcb9-0022197b567e |Thread:    3 |Category: Platform.Async |User: 00000000-0000-0000-0000-000000000000 |Level: Error | UpdateContractStatesOperation.InternalExecute
        at UpdateContractStatesOperation.InternalExecute(AsyncEvent asyncEvent)
        at AsyncOperationCommand.Execute(AsyncEvent asyncEvent)
        at PoolHandler.ProcessAsyncEvent(AsyncEvent asyncEvent)
        at PoolHandler.InvokeHandlerInPool(Object state)
        at ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
        at _ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
        at _ThreadPoolWaitCallback.PerformWaitCallback(Object state)
    >AsyncHandler::UpdateContractStatesOperation could not complete because of exception The request failed with HTTP status 401: Unauthorized.
    [2011-01-05 17:57:41.5] Process:CrmAsyncService |Organization:32ef82e3-750d-e011-bcb9-0022197b567e |Thread:    3 |Category: Platform.Async |User: 00000000-0000-0000-0000-000000000000 |Level: Error | AsyncOperationCommand.Execute
        at AsyncOperationCommand.Execute(AsyncEvent asyncEvent)
        at PoolHandler.ProcessAsyncEvent(AsyncEvent asyncEvent)
        at PoolHandler.InvokeHandlerInPool(Object state)
        at ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
        at _ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
        at _ThreadPoolWaitCallback.PerformWaitCallback(Object state)

    Thursday, January 6, 2011 1:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    On further review, the IIS error trace shows this error.  Does this help?

     

    <failedRequest url="http://64.81.172.103:80/MSCrmServices/2007/CrmService.asmx"
                   siteId="1"
                   appPoolId="CRMAppPool"
                   processId="4828"
                   verb="POST"
                   remoteUserName="PCCDR\CRM$"
                   userName="PCCDR\CRM$"
                   tokenUserName="PCCDR\CRM$"
                   authenticationType="Negotiate"
                   activityId="{00000000-0000-0000-B503-0080000000D7}"
                   failureReason="STATUS_CODE"
                   statusCode="401.5"
                   triggerStatusCode="401.5"
                   timeTaken="16"
                   xmlns:freb="http://schemas.microsoft.com/win/2006/06/iis/freb"

     

     

    Thursday, January 6, 2011 3:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Any ideas? 
    Thursday, January 6, 2011 5:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Any hope?  I'm still lost on this one.
    Saturday, January 8, 2011 4:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't think SQL server agent service and asynchronous service should be under the same account. 
    Saturday, January 8, 2011 11:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Brian,

    I am going to go back to my original thought that something didn't go as expected with the Org import.  You can look at the log files and try to track down the issue but ultimately I think you're going to need to either re-import the Org or re-install the server and then re-import the Org.  You can try a repair on the CRM server but not sure that will help.

    If the async service is not starting and the Org in Deployment Manager is enabled and all servers are pointing to their correct location then I suggest you disable the Org and try the import again.  It will be helpful to use the same login identified as your Deployment Administrator in the CRM Deployment Manager of the CRM system that is working.  Also ensure when you come to the part where you map the users during the import, that you map the user correctly.  It is also helpful to do the initial CRM server install with that same user login but that will only be applicable if you decide to uninstall and re-install.

    Other than the above, I'm not confident that we are going to be successful guessing at why your async service is not starting.

    Please ensure you follow this article exactly when you move the CRM server. 

    http://support.microsoft.com/kb/952934

    If you do re-install the CRM server, ensure everything is working as expected before you import the Org.  That should leave you with the ability to roll back to a working install if the import does not go as expected.

    Regards, Donna

    Saturday, January 8, 2011 1:43 PM