internal error has occurred within the Deployment Service (revisited)

This happened a few times in 9.0.0 IIRC. It seems to have returned.

 

I had this after deploying a solution. I think it happened after I opened a folder in the client immediately after the deployment. I recall an error in the client too. From this point no solution could be deployed. Uninstall and reinstall did not fix it.

 

I created a new database, and all was well again.

 

I manually deleted the last deployed solution version. Did not fix. I deleted all of the deployed versions of this solution from eProcedure, and all related records from eMap, eStage, eAction, eFolder and eAlert.

 

Now it works. Unfortunately I did not see if deleting only the eProcedure records would have made it work, as that could work with no data loss.

Tagged:

Comments

  • Did you ever figure out the exact cause of this or the specific resolution?  I seem to be hitting something eerily similar right now on a customer's environment.  Web client just hung when trying to open up an action form (form worked just fine before), now i can't deploy the solution anymore without the deployment service error.

     

    In the windows Event log, i see a SqlClient Timeout expired error...not sure why...the Designer can connect to the database just fine. 

     

  • I have a feeling it may have been a database issue. I have since learnt that SQL Server Express has a limit of 10 GB, although my database has only 5 GB, so I am not sure. Certainly I do know that after deleting some solutions it worked again for a while, and when it failed I deleted a load more and it was OK again, so it may be that.

     

    Another deployment issue was fixed using your advice to delete files here:

     

    C:\Users\\AppData\Local\IsolatedStorage\

    http://metastorm.processmapping.com.au/post?id=4710637