We had an annoying error, we tried to import a solution with a new field on the case table. The case table already had 300 plus fields on it so it was a bit a mammoth table.
Whilst trying to find the problem we split the various enhancements into separate solutions in an attempt to make each separate solution smaller and increase the chances of smaller solutions importing rather than one big one.
The reason we split up the solution was because we thought the problem was a timeout issue.
Interestingly the solutions with workflows and plugins imported. The solutions with other entities included also imported and we were left with a solution with just the case entity in which was still refusing to import.
The changes in the solution were minimal, we were basically adding one new field to the case entity but I guess this is adding a new field and value to all the case records which already exist in CRM database.
I remembered I previously had problems importing a large solution, so I searched my blog and found this
CRM 2011 – A time-out occurs when you import a solution in Microsoft Dynamics CRM 2011
In the blog I also refer to this KB article about a timeout when importing solutions
We were pretty sure the import was timing out because it was taking too long to import, so we increased the OLEDBTimeout and the ExtendedTimeout and this allowed the import process more time to import the solution and finally it worked.
A good reason to write blogs is you might run into the problem again later and if you have blogged about it you can easily find the solution to your problem even when you have forgotten the solution yourself.
I imagine this solution and the two registry keys would probably still be used in CRM 2013 although I haven’t tried this out yet.
The registry keys are used in MSCRM 2013 , yesterday I used this keys for too long importing solution operation in CRM 2013
Thanking for you commenting and adding that useful confirmation.