Select the product you need help with

Error message when you upgrade workflow rules from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0: "System.OutOfMemoryException"

Article ID: 950490 - View products that this article applies to.

SYMPTOMS

You upgrade Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0. When you upgrade workflow rules from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0, you receive a "System.OutOfMemoryException" error message.

In the Microsoft CRM Upgrade log file, you receive the following error message:

Time| Info| Upgrading instance workflow: Name:Sales Process Example ProcessInstanceId:{f26bc78d-94c2-dc11-856b-0019bbe6c5ce}
Time |Warning| Exception while upgrading instance workflow: Name:Sales Process Example ProcessInstanceId:{f26bc78d-94c2-dc11-856b-0019bbe6c5ce}| Microsoft.Crm.CrmException: SdkCommand Update ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.String.CtorCharArrayStartLength(Char[] value, Int32 startIndex, Int32 length)
at System.Data.SqlClient.TdsParser.ReadSqlStringValue(SqlBuffer value, Byte type, Int32 length, Encoding encoding, Boolean isPlp, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.ReadSqlValue(SqlBuffer value, SqlMetaDataPriv md, Int32 length, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ReadColumnData() at System.Data.SqlClient.SqlDataReader.ReadColumn(Int32 i, Boolean setTimeout)
at System.Data.SqlClient.SqlDataReader.GetValueInternal(Int32 i) at System.Data.SqlClient.SqlDataReader.GetValue(Int32 i)
at Microsoft.Crm.BusinessEntities.BusinessProcessObject.FillEntityFromDataReader(BusinessEntity entity, IDataReader reader, EntityExpression entityExpression)
at Microsoft.Crm.BusinessEntities.BusinessProcessObject.DoRetrieve(BusinessEntity entity, EntityExpression entityExpression, ExecutionContext context, Int32 languageCode)
at Microsoft.Crm.BusinessEntities.BusinessProcessObject.Retrieve(BusinessEntityMoniker moniker, EntityExpression entityExpression, ExecutionContext context, Int32[] deletionCodes, Int32 languageCode)
at Microsoft.Crm.BusinessEntities.BusinessProcessObject.Retrieve(BusinessEntityMoniker moniker, EntityExpression entityExpression, ExecutionContext context)
at Microsoft.Crm.Workflow.Upgrade.SdkCommand.Retrieve(String entityName, Guid entityId, String[] columns)
--- End of inner exception stack trace ---
at Microsoft.Crm.Workflow.Upgrade.SdkCommand.Retrieve(String entityName, Guid entityId, String[] columns)
at Microsoft.Crm.Workflow.Upgrade.SdkCommand.Retrieve(String entityName, Guid entityId)
at Microsoft.Crm.Workflow.Upgrade.WorkflowUpgradeOrchestration.CreateAsyncOperation(WFProcessInstanceRow processInstanceRow, Guid activationId, String primaryEntityName, IUpgradeContext upgradeContext, String messageName, Int32 errorCode)
at Microsoft.Crm.Workflow.Upgrade.WorkflowUpgradeOrchestration.CreateAsyncOperation(WFProcessInstanceRow processInstanceRow, Guid activationId, String primaryEntityName, IUpgradeContext upgradeContext, String messageName)
at Microsoft.Crm.Workflow.Upgrade.WorkflowUpgradeOrchestration.UpgradeInstances(IUpgradeContext upgradeContext, IDataProvider`1 dataProvider)

Back to the top | Give Feedback

CAUSE

This problem occurs if many workflow rules are published in Microsoft Dynamics CRM 3.0 before the upgrade.

Back to the top | Give Feedback

RESOLUTION

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949256

(http://support.microsoft.com/kb/949256/ )

Microsoft Dynamics CRM 4.0 updates and hotfixes

Back to the top | Give Feedback