|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 968601 - Last Review: March 31, 2009 - Revision: 1.0 The Microsoft Dynamics CRM Async service crashes when you run Microsoft Dynamics CRM 4.0When you run Microsoft Dynamics CRM 4.0, the Microsoft Dynamics CRM Async service crashes. When this problem occurs, the following error message is logged in the application event log on the Microsoft Dynamics CRM 4.0 server that has the Async Service role installed: Event Type: Error
Event Source: MSCRMAsyncService
Event Category: None
Event ID: 17411
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description:
The description for Event ID ( 17411 ) in Source ( MSCRMAsyncService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: CRMSERVER1, System.ArgumentOutOfRangeException: Value to add was out of range.
Parameter name: value
at System.DateTime.Add(Double value, Int32 scale)
at System.DateTime.AddSeconds(Double value)
at Microsoft.Crm.Asynchronous.QueueManager.GetNextRetryTime(Int32 currentRetryCount) in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\QueueManager.cs:line 860
at Microsoft.Crm.Asynchronous.QueueDataAccess.UpdateStateAndStatusInternal(Guid eventId, Int32 newState, Int32 newStatus, DateTime nextOccurrence, Boolean retryOperation, Int32 currentRetryCount, Int32 errorCode, String errorMessage, Boolean clearData, Boolean removeEvent) in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\QueueDataAccess.cs:line 382
at Microsoft.Crm.Asynchronous.QueueDataAccess.UpdateStateAndStatusCommand.InternalExecute() in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\QueueDataAccess.cs:line 679
at Microsoft.Crm.Asynchronous.QueuedDatabaseCommand.Execute(QueueManager queueManager) in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\QueueManager.cs:line 110
at Microsoft.Crm.Asynchronous.QueueManager.ExecuteAllOutstandingDatabaseOperations() in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\QueueManager.cs:line 613
at Microsoft.Crm.Asynchronous.QueueManager.OnDatabaseOperationTimerEvent(Object sender, ElapsedEventArgs e) in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\QueueManager.cs:line 597
at Microsoft.Crm.Asynchronous.Timer.InvokeElapsed() in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\Timer.cs:line 85
at Microsoft.Crm.Asynchronous.Timer.TimerProcessor.ExecuteTimers(Object data) in f:\CRMv4RTM\src\ObjectModel\Async\AsyncService\Timer.cs:line 192
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj).
Additionally, if you have enabled the Platform tracing functionality, you also receive an error message in the trace log file that resembles the following: [DateTime] Process:CrmAsyncService |Organization:00000000-0000-0000-0000-000000000000 |Thread:16(MSCRM:-TimerProcessor.ExecuteTimers) |Category: Platform.Async |User: 00000000-0000-0000-0000-000000000000 |Level: Error |
at AsyncService.OnUnhandledException(Object sender, UnhandledExceptionEventArgs e)
at DateTime.Add(Double value, Int32 scale)
at QueueManager.GetNextRetryTime(Int32 currentRetryCount)
at QueueDataAccess.UpdateStateAndStatusInternal(Guid eventId, Int32 newState, Int32 newStatus, DateTime nextOccurrence, Boolean retryOperation, Int32 currentRetryCount, Int32 errorCode, String errorMessage)
at UpdateStateAndStatusCommand.InternalExecute()
at QueuedDatabaseCommand.Execute(QueueManager queueManager)
at QueueManager.ExecuteAllOutstandingDatabaseOperations()
at QueueManager.OnDatabaseOperationTimerEvent(Object sender, ElapsedEventArgs e)
at Timer.InvokeElapsed()
at TimerProcessor.ExecuteTimers(Object data)
at ThreadHelper.ThreadStart_Context(Object state)
at ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at ThreadHelper.ThreadStart(Object obj)
>Exception while executing async service: MSCRMAsyncService - System.ArgumentOutOfRangeException: Value to add was out of range.
Parameter name: value
at System.DateTime.Add(Double value, Int32 scale)
at Microsoft.Crm.Asynchronous.QueueManager.GetNextRetryTime(Int32 currentRetryCount)
at Microsoft.Crm.Asynchronous.QueueDataAccess.UpdateStateAndStatusInternal(Guid eventId, Int32 newState, Int32 newStatus, DateTime nextOccurrence, Boolean retryOperation, Int32 currentRetryCount, Int32 errorCode, String errorMessage)
at Microsoft.Crm.Asynchronous.QueueDataAccess.UpdateStateAndStatusCommand.InternalExecute()
at Microsoft.Crm.Asynchronous.QueuedDatabaseCommand.Execute(QueueManager queueManager)
at Microsoft.Crm.Asynchronous.QueueManager.ExecuteAllOutstandingDatabaseOperations()
at Microsoft.Crm.Asynchronous.QueueManager.OnDatabaseOperationTimerEvent(Object sender, ElapsedEventArgs e)
at Microsoft.Crm.Asynchronous.Timer.InvokeElapsed()
at Microsoft.Crm.Asynchronous.Timer.TimerProcessor.ExecuteTimers(Object data)
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
This problem occurs because the existing workflow records contain a large retry count number. To resolve this problem, follow these steps: - Run the following script against the Microsoft Dynamics CRM database:
USE <OrganizationName>_MSCRM
GO;
UPDATE AsyncOperationBase
SET RetryCount = 3
WHERE RetryCount >=7
- If the problem still occurs after you performed step 1, run the following script against the Microsoft Dynamics CRM database:
USE <OrganizationName>_MSCRM
GO;
UPDATE AsyncOperationBase
SET RetryCount = 3
WHERE RetryCount >=7
USE MSCRM_CONFIG
GO;
UPDATE DeploymentProperties
SET FloatColumn = 1.0
WHERE ColumnName = 'AsyncRetryBackOffRate'
- The <OrganizationName> placeholder represents the actual organization name.
- This step is required only if step 1 does not resolve this problem.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
957871Â
(http://kbalertz.com/Feedback.aspx?kbNumber=957871/
)
The Workflow Expansion Task records cause the AsyncOperationBase table in the MSCRM database to grow too large in Microsoft Dynamics CRM 4.0
968520Â
(http://kbalertz.com/Feedback.aspx?kbNumber=968520/
)
Performance is slow if the AsyncOperationBase table becomes too large in Microsoft Dynamics CRM 4.0
959248Â
(http://kbalertz.com/Feedback.aspx?kbNumber=959248/
)
Microsoft Dynamics CRM 4.0 slows to unacceptable levels when you process e-mail messages by using the Microsoft Dynamics CRM E-mail Router
APPLIES TO- Microsoft Dynamics CRM 4.0
| kbmbsworkflow kberrmsg kbsurveynew kbtshoot kbmbsmigrate kbprb kbexpertiseinter KB968601 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
|
 |
|
 |
|
|
|
| |