Deleting Managed Solution results in a Sql timeout error
In this post, I will discuss about an issue our team had recently encountered when deleting a managed solution from the Dynamics 365 CRM on-premise system.
While deleting a managed solution, we encountered a 'Sql Timeout error'. The reason it was resulting in this error was because the default time limit in CRM is 2 minutes and deleting the solution with 300 components took longer than that time limit.
We followed the following MS article to increase the Sql Timeout value on the CRM server
https://support.microsoft.com/en-us/help/918609/a-time-out-occurs-when-you-import-large-customization-files-into-microsoft-dynamics-crm
We had added the OLEDB Timeout and ExtendedTimeout values as registry keys under MSCRM folder referring to the article above. However, that still did not solve our problem, and the managed solution was still throwing the timeout error.
Later, we raised a Microsoft support ticket to address this problem.
The following steps were performed by the MS service representative:
1. Increase the OLEDB Timeout and ExtendedTimeout values on all the servers (CRM, Database) associated with that deployment. We had three different servers that were being used for the CRM and maintaining its databases.
2. Do IISRESET
3. Delete the managed solution. The solution took longer than expected and we left it overnight to complete the process.
The solution was finally deleted.
After you finish with the process, make sure to delete the registry keys that were created on all the servers, and do an IISRESET, otherwise it creates performance issues.
This may be helpful for anyone who may come across a similar issue.
I will be happy to answer the questions.
While deleting a managed solution, we encountered a 'Sql Timeout error'. The reason it was resulting in this error was because the default time limit in CRM is 2 minutes and deleting the solution with 300 components took longer than that time limit.
We followed the following MS article to increase the Sql Timeout value on the CRM server
https://support.microsoft.com/en-us/help/918609/a-time-out-occurs-when-you-import-large-customization-files-into-microsoft-dynamics-crm
We had added the OLEDB Timeout and ExtendedTimeout values as registry keys under MSCRM folder referring to the article above. However, that still did not solve our problem, and the managed solution was still throwing the timeout error.
Later, we raised a Microsoft support ticket to address this problem.
The following steps were performed by the MS service representative:
1. Increase the OLEDB Timeout and ExtendedTimeout values on all the servers (CRM, Database) associated with that deployment. We had three different servers that were being used for the CRM and maintaining its databases.
2. Do IISRESET
3. Delete the managed solution. The solution took longer than expected and we left it overnight to complete the process.
The solution was finally deleted.
After you finish with the process, make sure to delete the registry keys that were created on all the servers, and do an IISRESET, otherwise it creates performance issues.
This may be helpful for anyone who may come across a similar issue.
I will be happy to answer the questions.
Comments
Post a Comment