locked
All system jobs are in waiting state RRS feed

  • Question

  • Hi All,

    All my system jobs are in waiting state, error message is as below. What might be causing the error, can any one guide me please. The async service is running fine.

    System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it ::1:80  at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)  at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)  --- End of inner exception stack trace ---  at System.Net.HttpWebRequest.GetRequestStream()  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.BulkDetectDuplicatesOperation.GetQueryExpressionFromFetchXml(String fetchXml)  at Microsoft.Crm.Asynchronous.BulkDetectDuplicatesOperation.DoBulkDuplicateDetection()  at Microsoft.Crm.Asynchronous.BulkDetectDuplicatesOperation.InternalExecute(AsyncEvent asyncEvent)  at Microsoft.Crm.Asynchronous.AsyncOperationCommand.Execute(AsyncEvent asyncEvent)  at Microsoft.Crm.Asynchronous.QueueManager.PoolHandler.ProcessAsyncEvent(AsyncEvent asyncEvent)

    Thursday, September 16, 2010 10:18 AM

Answers

  • Thursday, September 16, 2010 10:57 AM
    Answerer
  • Since MayankP's suggestion is from a post where the solution worked, you can try that first.  However, please make a backup of your database in the event that something doesn't go as expected.  Additionally, it seldom hurts to ensure you are on the latest update as updates often have fixes that correct issues like this.

    Was this working at some point in time and then stopped working?  One additional comment, in looking at the error message, it could be a permission issue:

    "No connection could be made because the target machine actively refused"

    Since you are leveraging load balancing, there could be some permissions issue.  I'm not sure of your environment details but you can have a look at this article to ensure you've setup the environment in a way that the machines can leverage services that are installed on other machines.


    Regards, Donna

    Monday, September 20, 2010 3:23 PM

All replies

  • Thursday, September 16, 2010 10:57 AM
    Answerer
  • This article asks me to perform the following operation

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

     

    What this does? With this update the jobs were working fine, now why this update needs to be done?

    Thursday, September 16, 2010 12:07 PM
  • Hi,

    Did you tried updating CRM with the latest Rollup?

    Regards

    TGB


    Microsoft Certified Business Management Solutions Specialist
    Thursday, September 16, 2010 12:14 PM
  • These properties are used by Async service to get crm sdk details..

     


    MayankP My Blog My twitter
    Thursday, September 16, 2010 12:25 PM
    Answerer
  • Which is best, to update the db using deployment config tool or applying the latest roll up.

    Basically I have two servers on NLB, but only one server has this issue.

    Thursday, September 16, 2010 1:24 PM
  • Since MayankP's suggestion is from a post where the solution worked, you can try that first.  However, please make a backup of your database in the event that something doesn't go as expected.  Additionally, it seldom hurts to ensure you are on the latest update as updates often have fixes that correct issues like this.

    Was this working at some point in time and then stopped working?  One additional comment, in looking at the error message, it could be a permission issue:

    "No connection could be made because the target machine actively refused"

    Since you are leveraging load balancing, there could be some permissions issue.  I'm not sure of your environment details but you can have a look at this article to ensure you've setup the environment in a way that the machines can leverage services that are installed on other machines.


    Regards, Donna

    Monday, September 20, 2010 3:23 PM
  • Hi Donna, Thanks for all your replies. Luckily I have resolved this issue by restarting the Asynch Service, IIS and the server itself. Yes, it was working well previously, but stopped in the middle. Regards
    Tuesday, September 21, 2010 6:13 AM