Home > CRM 4.0 > Error while changing User’s Business Unit

Error while changing User’s Business Unit

In some cases when we try to change the business unit of one particular user to another business unit, we may encounter an error saying “And error has occurred. Try this action again

90% probability for this error will be a “Time-out Issue“.

And the resolution would be to set the OLEDBTimeOut and ExtendedTimeOut values in the Registry.

Follow these steps:

Add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values
1. Click Start, click Run, type regedit , and then click OK.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRM
3. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
4.  Rename the DWORD value to the following value:
OLEDBTimeout
5. Right-click the DWORD value, and then click Modify.
6. In the Edit DWORD Value dialog box, type 86400 in the Value data box, click Decimal in the Base option, and then click OK.
Note: According to the requirement of the computer that is running SQL server and the number of customization files, the value can be larger than  86400. The value of 86400 is equivalent to 24 hours.
7. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
8. Rename the DWORD value to the following value:
ExtendedTimeout
9. Right-click the DWORD value, and then click Modify.
10. In the Edit DWORD Value dialog box, type 1000000 in the Value data box, and then click OK.

Notes:
” In the Value data box, you can type a value that is larger than 1,000,000. However, do not type a value that is larger than 2,147,483,647. This is hexadecimal 0x7FFFFFFF.
” If this key already exists, notice the current value. After you have completed the import or the upgrade for Microsoft Dynamics CRM, set the value of this key back to the original value or delete the key if it did not previously exist. The default OLEDB timeout value is 30 seconds.

This solution works perfectly.

Caution: As a safety precaution and as a best practice back up your registry before making any changes.

Advertisements
Categories: CRM 4.0
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: