Install-SPSolution error “Admin SVC must be running in order to create deployment timer job”

Last night I was installing a solution on my own farm at home and because I turn my server off sometimes You get the usual errors to get everything up and running. But so far no problems until I wanted to install a solution package from my Web Frontend server. I opened PowerShell and added the SharePoint snapin.

I added the solution file Add-SPSolution “C:\MySharePointSolution.wsp“ and then I installed it Install-SPSolution –Identity MySharePointSolution.wsp –WebApplication http://myspwebapp –GACDeployment -Force.

Only at the installing part I got a nice red PowerHell error, “Admin SVC must be running in order to create deployment timer job”.

After inspecting the error message I was thinking, WTF is the Admin SVC ?, So I turned to our trusty friends of BING (yes in some post I use Google and some BING, please don’t tell anybody but I’m a secret double agent). But Any way, the Admin SVC is actually the SharePoint 2010 Administration service (Windows Service – services.msc).

After starting the service and giving the Install-SPSolution command one more hit everything worked like a dream.

PowerShell Install-SPSolution trouble

Hey People,

A moment ago I deployed a solution with PowerShell and I’ve received a weird error. Atleased not weired but it did not made me happy. This is what I did,

• Add-PSSsnapin Microsoft.SharePoint.PowerShell
• Add-SPSolution “C:\MySharePointSolution.wsp“
• Install-SPSolution –Identity MySharePointSolution.wsp –WebApplication http://myspwebapp –GACDeployment

Then I did, Get-Solution and I saw my newly installed sollution was False. In de Central Admin Console I found an error.

SERVERNAME : Failed to create receiver object from assembly “MySharePointSolution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XXX”, class “SomeNamespace.Features.Lists.ListsEventReceiver” for feature “SomeNamespace_Lists” (ID: {GUID}).: System.ArgumentNullException: Value cannot be null.

First I checked all the SharePoint Windows Timer Services if they where running and yes this was the case.

Then somebody on the web pointed out just to stop and start the timer service of the WFE servers because of a DLL that would be cached and causing trouble. So I stopped and started the Timer service and deployed it again. Only this time I’ve got an other error that there already was a solution. SharePoint suggested to add -Force and that was the trick, it worked like a dream.

So in the end of this story the clue is resetting services can do magic.