You are visiting the High Monkey blog archive. Posts prior to 2016 may not meet accessibility standards. Please visit our current blog area at https://www.highmonkey.com/blog to view accessibility compliant blog posts published since January 1, 2016.

STSADM is still necessary. Read on...

Written By: High Monkey
Posted: 4/1/2011

(From the mind of Peter Serzo, Previously VP of Consulting Services at High Monkey)

Unfortunately this is not an April fool's joke. Being a true development guy at heart, I thought it was all PowerShell from here on out – smooth sailing.

But then I came across the following error while doing a wsp install with the handy dandy Install-SPSolution:

Admin SVC must be turned on. Simple enough.  I went to Services and ensured it was running:

I started it and ran the Install-SPSolution. Everything should be great, right?

No! I now got the following error…

"A deployment or retraction is already under way for the solution." Here is the Tarantino catch-22 – I received this error because of my previous attempt at doing the install and only one deployment or retraction at a time is supported..

So now I have to kill that job and then reinstall. Ok, easy – break out the handy dandy PowerShell and …

What? There is no Kill-SPSolutionInstall command or anything like it. Ohhhh, the crux of this post(but not the last one!). You must use stsadm in order to kill a running job!

Found the solution at: www.beyondweblogs.com/post/Sharepoint-Solution-Deployment-A-deployment-or-retraction-is-already-under-way-for-the-solution-and-only-one-deployment-or-retraction-at-a-time-is-supported.aspx

Give credit where credit is due. The steps are:

  1. Locate deployment jobId to break the running process using following command:

    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm-o enumdeployments

     2.  Now cancel the deploy typing the following command:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm-o canceldeployment-id "GUID jobId"

     3.   Check that deploy has been canceled by typing the following command:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm-o enumdeployments

Phew! We are done right. No.

When I ran the stsadm command I received a popup error stating: stsadm is not a valid win32 application

After some more research - here is the FIX: Copy the stsadm from another working installation into the /14/bin.

Now run the two stsadm commands above. Success!

Back to the beloved PowerShell and run the Install-SPSolution.

This code M….. (not going to say it) is out. Enjoy.

Chad's Bio Coming Soon!

More About Virgil

Virgil Carroll is the owner and president of High Monkey – based in Minneapolis Minnesota. Virgil also wears the multiple ‘hats’ of Principle Human Solutions Architect and SharePoint Architect.

Virgil is one of those rare individuals who can dive deep into technical topics while speaking clearly to the business owners of a project and never forgetting that the end user experience has the highest priority. He calls it using both sides of his brain. Virgil is passionate about leveraging technologies ‘out of the box’ as much as possible with a focus on the strategic use of content to create websites that deliver the right content to the right audience on the right device at the right time. Virgil brings high energy, an ironic wit, and a sense of grounded perspective whenever he speaks to an audience. Virgil regularly speaks at conferences and user groups throughout the United States and occasionally in Europe.

Posted: 4/1/2011 12:00:00 AM by | with 0 comments
Filed under: