1

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                            {}
Improve this question

1 Answer 1

Reset to default
1

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/

Improve this answer
14
  • Even after reading that a few times, I'm not sure what a Get Command is doing that could remedy this problem, I have edited my answer to include the output. Thank you for showing me Get-SPProduct
    – christopher clark
    Commented Jan 27, 2016 at 20:13
  • Can you run a psconfig? Running this command allows your SharePoint to detect required software that would otherwise be blocking the sync in the farm.
    – Mike
    Commented Jan 27, 2016 at 20:18
  • You are very close to an accepted answer. We ran the powershell command and psconfig wizard on both servers. I decided to start/stop with central admin on the WFE the Excel Calculation Services. And it worked! However on the APP server I was able to STOP excel Calculation services, but now it's stuck on starting.
    – christopher clark
    Commented Jan 27, 2016 at 21:04
  • 1
    Check the timer jobs and delete the one-time jobs, and restart the sptimer service, before you try to deploy again. You may need to reset the sp config cache, read here: blogs.msdn.com/b/jamesway/archive/2011/05/23/…
    – Mike
    Commented Jan 28, 2016 at 18:23
  • 1
    SPTimerv4 is a crucial service that syncs the server with the rest of the farm's servers. It should always be running on every SharePoint server. If One-Time jobs are in the definitions, they aren't running correctly. One-time timer jobs are created by SharePoint and the definitions are deleted after they run successfully.
    – Mike
    Commented Jan 28, 2016 at 18:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.