SharePoint 2010 Troubleshooting: Solution deployment stuck on deploying
Solution deployment is the task that we do on daily basis. This is the task in which SharePoint developer and administrator works in proper co-ordination.
Problem description
While deploying the solution in our production environment we faced some strange issues. When adding a solution using PowerShell command its says operation completed successful.
Add-SPSolution –LiteralPath "<file_path>\name of the wsp” is stored"
So the next stage is install solution and we executed the following command:
Install-SPSolution -Identity "name of the solution.wsp" -WebApplication http://mossnwss.com/ –GACDeployment
Checked the statuses of the solution in central administration->system settings->manage farm solutions and the status never changes from deploying.
By means of this article, we will try to share the resolution that worked for us and possible recommendations you can try to resolve this issue completely.
Resolution that worked
It turned out that one of the servers stopped the timer service + World Wide Web publishing service due to patches incompatibility and it was waiting on this server to complete. If you have more than one server in your farm ensure that the SharePoint TIMER services are running on all.
How you can check the above:
1. On any server->start->run->services.msc->enter->this will open the services console.
2. Now type s-> this will give you all the services that start with S->look for SharePoint timer service and make sure it’s in started mode.
3. This service should be started on all the front ends as well as application server.
Possible Resolutions
1. Make sure SharePoint timer service should be started on all the servers (web front ends as well as app server)
2. Try restarting the SharePoint Administration service on all the servers.
3. Restart all the SharePoint servers
4. Make sure that all the servers in farm are on the same time zone.
5. Execute stsadm -o execadmsvcjobs on all the servers of the farm
6. Cancel the deployment job by means of central administration, remove the solution and try to add the solution again & check the results.
7. Check the status of the jobs by means of CA-timer job status or use the following command - stsadm -o enumdeployments This will give you the list of all the pending & active deployments.
8. After patching, make sure SPTimerServiceInstance object which represents the SPTimerV4 Windows service is online in all SharePoint servers.
To bring it online , run the following power shell and then restart the timer windows service manually:
$farm = Get-SPFarm $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"} if ($disabledTimers -ne $null) { foreach ($timer in $disabledTimers) { $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online $timer.Update() } }
After trying all the steps and nothing works then please checks the logs and find out the root cause.
In case of any problems with respect to logs then please share here so that we can help you out!
Hope the above information will be helpful to deploy the solution successfully. Thank you.
Product applies to
- SharePoint Server 2010
- SharePoint Foundation 2010
- SharePoint Server 2013
- SharePoint Foundation 2013