locked
Error while processing organization Async Service RRS feed

  • Question

  • Hi.
    My Crm 4.0 Async service has starting to throw error messages like this:

    Host <dnsname>: error while processing organization 0989bd38-5e10-4fb4-8564-be79db561d47. Exception: System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

       at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

       at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)

       at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()

       at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()

       at System.Data.SqlClient.TdsParserStateObject.ReadByte()

       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

       at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()

       at System.Data.SqlClient.SqlDataReader.get_MetaData()

       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

       at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

       at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)

       at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()

       at Microsoft.Crm.CrmDbConnection.InternalExecuteReader(IDbCommand command)

       at Microsoft.Crm.CrmDbConnection.ExecuteReader(IDbCommand command, Boolean impersonate)

       at Microsoft.Crm.Asynchronous.DataAccessBase.ExecuteSqlCommandAndProcessRecords(IDbCommand command, RecordProcessor recordProcessor)

       at Microsoft.Crm.Workflow.WaitSubscriptionDataAccess.Notify(IDbCommand selectCommand, WaitNotificationService waitNotificationService)

       at Microsoft.Crm.Workflow.WaitSubscriptionDataAccess.Notify(String hostId, WaitNotificationService waitNotificationService, Int32 maxRetries)

       at Microsoft.Crm.Workflow.WorkflowHost.OnNotificationTimerEvent(Object sender, ElapsedEventArgs e)

    I have read this: http://social.microsoft.com/Forums/en-US/crm/thread/401855e6-47d9-47fb-9ca7-1854d8eb470f but my problem is nor cpu-preformance, rather that the async-service is loosing db-connection ore something.

    Antbody got an idea?

    Tuesday, January 5, 2010 10:31 AM

Answers

  • I ended some Workflows that where in a whait-mode. This seems to have fixed it. No more errors in the event-log. Must be some sql gone really bad... Thank you all for the input.

    /Kris

    • Marked as answer by KristofferS Thursday, January 14, 2010 9:06 AM
    Thursday, January 14, 2010 9:06 AM

All replies