Question

This is a very bizarre issue. Let me tell you our environment. SharePoint 2013 Enterprise, three server farm. Database, App, and WFE. A migration from 2010 happened about 6 months ago.

In order to Start/Stop Services Provision/Unprovision services or Deploy/Retract solutions. We have to follow these steps.

  1. Use Central Admin to either start/stop/deploy/retract.
  2. Stop the SPAdminv4 service
  3. Run stsadm -o execadmsvcjobs
  4. Start the SPAdminv4 service

If we don't do this, Central admin and Powershell will be stuck on starting/stopping/deploying/retracting. We have confirmed that other TimerJobs will complete. We have tested starting/stopping etc with using powershell, and we had the same issue.

What could be causing this? It's weird that we must run some deprecated powershell command to complete a simple task.

EDIT: ran Get-SPProduct -Local The Output for both servers was

ProductName                    Required   Missing              Servers             
-----------                    --------   -------              -------             
Microsoft SharePoint Server... True                            {}   
Was it helpful?

Solution

I've had this problem before. You probably need to run the PowerShell command

Get-SPProduct -Local

Also I would try to run the PSConfig on all servers.

More here: http://thesharepointfarm.com/2013/12/the-magic-of-get-spproduct-local/

Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top