We were having a problem importing or creating new entities.
Enabling trace revealed the following error being logged
Exception when executing non-query: exec p_RecreateIndexes Exception: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Happily I then found a post here which describes how to change the time out value
http://mscrmuk.blogspot.com/2008/09/sql-timeouts-in-crm-generic-sql-error.html
the content of that post (in case it is ever moved is) quoted below...
Increase the Timeout
The SQL timeout is controlled by a registry value on each CRM server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\OLEDBTimeout
This value does not exist by default, and if it does not exist then the default value will be 30 seconds. To change it, add the registry value (of type DWORD), and put in the value you want (measured in seconds). Then you have to recycle the CrmAppPool application pool for the change to take effect (this is a step most Microsoft documentation omits to mention); do this we IISReset, or less drastically via iisapp.vbs
This has now resolved the issue...
No comments:
Post a Comment