Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
System Jobs are in a waiting state / Asnc Service can't connect to CRM Service RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi @ all,

    In our deployment the workflows/asncservice couldn't connect to the crm service. In the systemjobs (AsyncOperationBase) is in the field "message" the following entry:

    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)     at Microsoft.Crm.Asynchronous.QueueManager.PoolHandler.ProcessAsyncEvent(AsyncEvent asyncEvent)

    We have the following configuration:
    2 CRM Application Server (Both full server role) with an F5 Hardware Loadbalancer in front of.

    We have also an IFD Deployment. In the Database we has set the parameters:
    ADSdkRootDomain
    ADWebApplicationRootDomain
    AsyncSdkRootDomain

    all to <loadbalancerIP:5555>

    we have also worked through the following KB http://support.microsoft.com/kb/950416
    but with no success.

    In the forum I have found the following post, with a similar problem but, with no solution

    http://social.microsoft.com/Forums/en-US/crmdeployment/thread/558f9325-f62f-4f20-9284-cf530430bd8b

    Has anybody here further ideas to analyse the problem?

    Thanks with regards

    Matthias

    Monday, October 18, 2010 6:29 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi @all,

    thanks for the answers. The problem was that in this case we used an Hardware Loadbalancer and no Network Loadbalanced System.
    The HLB couldn`t authenticate to the AD Domain. So if you are using an HLB you should configure the AsyncSdkRootDomain to one dedicated server an not to the LB-Adress.

     

    Regards

    Matthias

    • Marked as answer by Matthias Back Sunday, February 6, 2011 1:07 PM
    Sunday, February 6, 2011 1:07 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    Can you please post what the host header properties look like on both of the front-end IIS servers please? Are you using alias/host headers on the IIS server? Are there other websites running on the IIS servers besides CRM?
    H. Sean Shilling, Sr. Sr.Consultant CustomerEffective www.customereffective.com 2009 Microsoft Dynamics CRM Financial Services Partner of the Year
    Tuesday, October 19, 2010 2:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    This is not recommended but try this it has helped me a few times changing the status of jobs in waiting state.

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

    Regards

    TGB

    Microsoft Certified Business Management Solutions Specialist
    Friday, October 22, 2010 9:11 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Check this forum post:

    http://social.microsoft.com/Forums/en-US/crmdeployment/thread/cc5464c6-99a5-4ba8-9374-68291b1282d8/#533d412b-b1ac-4c53-8d59-839247e64532

    Vicky http://howto-mscrm.blogspot.com "Please Mark it as answer if it helps in resolving your query"
    Saturday, October 23, 2010 7:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

     

    Are you using ssl for both internal and external access? if answer is yes, turn the ssl off for internal access.

     

    I hope it helps.

    Amreek singh Senior CRM Consultant CDC Praxa Sydney, Australia http://mscrmshop.blogspot.com
    Thursday, October 28, 2010 3:35 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Matthias,

    Please try out this: Use IFD Config Tool to set it back to onPremise ,apply the changes.

    Run Deployment Config Tool command line tool with the below values for asyncsettings

    addresssettings update -webapprootdomain:<IPADDRESSOFTHECRMWEBSITE>
    addresssettings update -sdkrootdomain:<IPADDRESSOFTHECRMWEBSITE>

    Then execute this on Mscrm_Config with your values

    Update DeploymentProperties SET NVarCharColumn = '<server>:<port>' WHERE ColumnName = 'AsyncSdkRootDomain'

    Your Default Site, intranet, should point with Server IP on IIS, then Reset IIS, Restart Microsoft Async Service. You should be good to go.

    Later apply IFDConfigTool with IFD + On premise to set it back..Cool

    If still the same error, diagnose like this link: http://blogs.msdn.com/b/benlec/archive/2009/02/10/how-to-troubleshoot-system-jobs-failures-using-advanced-find.aspx

    Best of Luck,,,,CRMMate....

    Suresh Kumar VC

    amateur
    Friday, October 29, 2010 10:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Matthias,

    Did any of the suggestions help you or point you in the right direction?  Is this issue resolved?

    Thank you

    Regards, Donna

    Monday, November 15, 2010 5:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi @all,

    thanks for the answers. The problem was that in this case we used an Hardware Loadbalancer and no Network Loadbalanced System.
    The HLB couldn`t authenticate to the AD Domain. So if you are using an HLB you should configure the AsyncSdkRootDomain to one dedicated server an not to the LB-Adress.

     

    Regards

    Matthias

    • Marked as answer by Matthias Back Sunday, February 6, 2011 1:07 PM
    Sunday, February 6, 2011 1:07 PM