I am trying to deploy a WSP solution in SP2010 using a PowerShell script and it's showing the status in CA as "Deploying" for a long time. I have tried:

  1. stsadm -o execadmsvcjobs
  2. stsadm -o enumdeployments
  3. Remove-SPSolution -ID -force (Finally to remove the solution )
  4. Restarted SharePoint 2010 Timer Job in services.msc

But I'm still facing the same problem once I deploy it again. Any Help

  • If you can inlcude a copy of your powershell deployment script, that might be useful too. – lwbecker2 Aug 22 '12 at 18:51
  • I am have the same problem when deploying a wsp in SP2010. Any ideas ? – user10461 Aug 31 '12 at 13:16

Is there anything in the ULS logs? I have seen the deployment hang when the services don't have the correct access to a box, or the services aren't running (ie: setup account must be local admin on all boxes in the farm, and the timer service must be running), but it'll typically come back after a period of attempts and tell you it failed.

Without more information, it's difficult to provide any guidance.

|improve this answer|||||
  • SQL database login for 'SharePoint_Config' on instance 'ServerName' failed. Additional error information from SQL Server is included below. Login failed for user 'domainname\servername'. – shreyas Aug 22 '12 at 20:22
  • If you're getting an access error like that I'm assuming you're running the deployment under your personal credentials, and not the setup account. Log on to the box using the setup/install account (which will have the correct permissions), and retry the deployment. – webdes03 Aug 23 '12 at 13:37

Make sure that the Timer job is running on ALL servers in the farm, not merely the server you are running the commands on. Beyond that, make sure that the account that you are logged in on has sufficient permissions on the farm.

|improve this answer|||||
  • I just have one server running like wfe/app. – shreyas Aug 22 '12 at 19:08
  • In that case, set your Diagnostic logging to Verbose/Verbose, rerun the deployment, giving it about 5 minutes to run, then look at the latest logs in 14/LOGS for any errors or other unexpected results. ULS Viewer (archive.msdn.microsoft.com/ULSViewer) helps considerably with this task! – Dave Wise Aug 22 '12 at 19:17
  • ULS Viewer shows an Error : SQL database login for 'SharePoint_Config' on instance 'ServerName' failed. Additional error information from SQL Server is included below. Login failed for user 'domainname\servername'. – shreyas Aug 22 '12 at 20:35
  • I assume you are running this as your user account so the quickest way to get around it is to run the SharePoint Command Console as the Farm account (Shift-right click on the link and select Run As User) and attempt the deployment under that account. If that works, then you will need to do some troubleshooting to determine exactly where the permissions for your user account are falling short as you really don't want to make it a habit of logging in under the farm account. – Dave Wise Aug 22 '12 at 21:02
  • Thanks Dave, I had fixed this issue in main server (using powershell commands) but still needs to fix it in dev server. – shreyas Aug 27 '12 at 18:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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