Last week I tried to update one of our solutions. the upgrade worked perfectly fine in the dev and test environment, but when I tried it on the release server, it stuck on deploying.
I did hours of search and tried almost every suggested solution such as
I did hours of search and tried almost every suggested solution such as
- Check the SharePoint 2010 timer services on all servers
- Restart all the SharePoint services on all servers
- Check the SharePoint Web Services application pool in all servers
- Restart the IIS application pool for SharePoint web services
- IISReset
- Check the timer jobs
- Cancel deployment and try Disable-SPFeature, Uninstall-SPSolution, Remove-SPSolution then Add-SPSolution, Install-SPSolution, Enable-SPSolution (couldn't do further than uninstall because it stuck on retracting)
- Retract and Remove solution through UI (Central Admin) and try to redeploy again
- I even tried Stsadm -o deploysolution -local
every one of these approaches fixed other people problem in different circumstances, but noting helped me. when I tried the Stsadm command to deploy locally, I realised that I can deploy on two servers out of three.
the third server in the farm is the indexing server and when I tried to open powershell, it was giving a message about not having SharePoint.
Oh, what an idiot I am... looking at the logs more carefully, there is being lots of logs about this server not being accessible.
Finally, everything been solved just by restarting the problematic server and redeploy the solution, ofcourse I had to redeploy instead of update because in my many attempts to find the problem I disabled and removed the actual feature.
well the lesson learned is to check ALL the servers in the farm when you are having a similar issue and make sure they are all healthy and working as expected.
No comments:
Post a Comment