The timeout period elapsed prior to completion of the operation or the server is not responding

There are a number of causes for this error message and their are a range of msdn articles covering these issues including importing customisations through to changing the user’s business unit. The default of 30 seconds is sometimes just not enough. The below instructions are taken from one of the many msdn articles.

Restart IIS after adding the values

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_MACHINE\SOFTWARE\Microsoft\MSCRM
  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.
Advertisements

About Rhett Clinton MVP
Dynamics CRM MVP

2 Responses to The timeout period elapsed prior to completion of the operation or the server is not responding

  1. Chad Rexin says:

    Note that setting this value to a value much higher than 300 or 600 (5 min or 10 min) greatly increases the chance for excessive SQL Blocking to occur, which can result in bigger performance issues than it would by simply letting the Microsoft CRM platform to cancel the long running query. It is better to find the long running queries and tune them than to put in an excessively high value in this registry key.

    • Very true Chad and I wouldn’t recommend these settings to be used as a quick fix for a poorly performing query. I see this setting being used when there is no other means to execute a process such as importing customisations, deleting an entity and/or other such built-in features of CRM. I also recommend changing these values back to their defaults or even removing them from the registry altogether (if not originally present) as soon as the process executes successfully.

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: