Article ID: 918609 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
When you import large customization files into Microsoft Dynamics CRM 3.0 or into Microsoft Dynamics CRM 4.0, a time-out occurs. Additionally, you receive one of the following error messages.
Error message 1
Import timeout error.
Error message 2
Maximum request length exceeded.
Error message 3
The file could not be uploaded or Import failed
Error message 4
If the DevErrors value is set to "On" in the Web.config file, you receive the following error message:
This is not a valid customization file. Please use an .XML file that was generated by exporting customizations.
Additionally, when you upgrade a large Microsoft CRM database from Microsoft Business Solutions - CRM 1.2 to Microsoft Dynamics 3.0 or from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0, you may receive the following error message:
Microsoft CRM Platform Error Report:
Error Description: Timeout expired
Error Details: Details on this error have not been provided by the platform.
Error Number: 0x80040E31
09:54:25| Error| Install exception.System.Exception: Action Microsoft.Crm.Setup.Server.InstallDatabaseAction failed. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.Crm.Setup.DatabaseInstaller.DatabaseUtility.ExecuteSql(InstallDatabase database, String sql, Int32 timeout) at Microsoft.Crm.Setup.DatabaseInstaller.SqlScriptAction.Execute() at Microsoft.Crm.Setup.DatabaseInstaller.DatabaseInstaller.Install(Int32 languageCode, String file, Boolean upgrade) at Microsoft.Crm.Setup.Server.InstallDatabaseAction.Do(IDictionary parameters) at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo) --- End of inner exception stack trace --- at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo) at Microsoft.Crm.Setup.Common.Installer.Install(IDictionary stateSaver) at Microsoft.Crm.Setup.Server.DatabaseInstaller.Install(IDictionary stateSaver) at Microsoft.Crm.Setup.Common.ComposedInstaller.InternalInstall(IDictionary stateSaver) at Microsoft.Crm.Setup.Common.ComposedInstaller.Install(IDictionary stateSaver) at Microsoft.Crm.Setup.Server.ServerSetup.Upgrade(IDictionary data) at Microsoft.Crm.Setup.Server.ServerSetup.Run()
This problem occurs because one of the following conditions is true:
To resolve this problem, use one or more of the following methods.
Method 1: Add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out valuesWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Method 2: Modify the parameters in two different Web.config files
The OLEDBTimeout valueThe unit of the OLEDBTimeout value is seconds. By default, the OLEDBTimeout value is 30 seconds. The OLEDBTimeout value controls the SQL time-out value that is used for a single SQL query. The increased OLEDBTimeout value is useful when the SQL server is overloaded. Additionally, the query takes a longer time to process.
The ExtendedTimeout valueThe unit of the ExtendedTimeout value is milliseconds. By default, the ExtendedTimeout value is 1000000 milliseconds. The ExtendedTimeout value controls the ASP.NET time-out value that is used for import requests. The time-out value must be larger than the time for finishing the whole import process. The increased ExtendedTimeout value is useful when the import process takes a long time.
Note When the performance of the SQL server is slow or when there are many customization files to import, the import process takes a long time.
Contact us for more help
Connect with Answer Desk for expert help.