A SQL Server Timeout may occur when changing a name field for a Microsoft Dynamics CRM User
This article helps you resolve the problem where administrator is unable to make changes to a user record in Microsoft Dynamics CRM 2011 and receives a generic SQL Server error message.
Applies to: Microsoft Dynamics CRM 2011
Original KB number: 2637855
Symptoms
An administrator is unable to make changes to a user record in Microsoft Dynamics CRM 2011 and receives a generic SQL Server error message.
Cause
This can be caused by the user owning a high number of related records that need to be updated in the ActivityPartyBase table in the Microsoft Dynamics CRM organization database.
Resolution
Increase the HKLM\Software\Microsoft\MSCRM\OLEDBTimeout
to a higher value either on a temporary basis or permanent basis on the Microsoft Dynamics CRM Server.
Create or change the OleDbTimeout value
In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
Double-click the OleDbTimeout value.
Note
If the OleDbTimeout value does not exist, create an OleDbTimeout value. To do this, follow these steps:
- Right-click MSCRM, point to New, and then click DWORD value.
- Type OleDbTimeout.
In the Edit DWORD Value dialog box, click Decimal, type 600 in the Value data field, and then click OK.
Note
The value of 600 represents 600 seconds. By default, the value is 30 seconds. Also note that if required on a temporary basis to allow this operation to complete, you may need to set this to 86400 which is equivalent to a value of 24 hours.
Note
It's recommended to run with the OLDDBTimeout setting set to a value between 30 to 600 decimal as a best practice to help minimize excessive SQL Blocking that a long running or expensive query may cause.