3

Those are the properties of my wsp :

enter image description here

I use SPSD to deploy my solution, there is no error on SPSD log and SP log .

I Restarted the SharePoint Timer service and the administration services on all my front-end server. The issue is the status of solution deployment stuck on deploying. I check: the features are created on my all front-end server, the bin is on the virtual directory folder. I even restart all the server ? but the issue still the same.

Any ideas ?

7
  • Can you go to Central Administration -> System Settings -> Manage Farm Solutions and check on the status there? I would try canceling the deployment from there and see if you can retry.
    – Ted N.
    Mar 3, 2016 at 13:12
  • when i cancel the deployment teh status change to deployed , but it's not the right way , is that ?
    – Imen Turki
    Mar 3, 2016 at 13:14
  • No, but canceling the deployment should let you try to deploy it again. Managing the solution through Central Admin is sort of a last-ditch fix... Does the solution hang every time you deploy or is this just a fluke?
    – Ted N.
    Mar 3, 2016 at 13:32
  • yes the solution hang every time I deploy, i even restart the timer jobs on all server.I wish i could know what it try to to do ?
    – Imen Turki
    Mar 3, 2016 at 13:38
  • 1
    what method you are using the to deploy the solution? i am sorry but i dont know what is SPSD?
    – Waqas Sarwar MVP
    Mar 3, 2016 at 13:39

2 Answers 2

3

In my case I have followed below steps to deploy the solution:

  1. I have cancel my solution deployment from central admin.
  2. I have restarted SharePoint Timer Service in all my SP instance.
  3. I stopped SharePoint Administration service in all SP instances.
  4. I have deployed my solution from central admin. (keep continue even if it gave an error)
  5. I have executed below command in all SP instance in Command Prompt (administrative)
    stsadm -o execadmsvcjobs
  6. Refresh deployment page. It shows deployment success message
2

So it finally works , it's a SP problem , what I did is:

  1. I restart all my timer job with PShell

stsadm -o execadmsvcjobs

or

[array]$servers= Get-SPServer | ? {$_.Role -eq "Application"}            
$farm = Get-SPFarm            
foreach ($server in $servers)            
{            
    Write-Host "Restarting Timer Job on $server"                                      
    $Service = Get-WmiObject -Computer $server.name Win32_Service -Filter "Name='SPTimerV4'"                        
    if ($Service -ne $null)                         
    {                             
        $Service.InvokeMethod('StopService',$null)            
        Start-Sleep -s 7            
        $service.InvokeMethod('StartService',$null)                             
        Start-Sleep -s 7            
        Write-Host "Timer Job successfully restarted on $server"                        
    }             
    else            
    {            
        write-host -ForegroundColor Yellow "Could not find SharePoint 2010 Timer Service on $server"            
    }            
}
  1. Restart all my front-end server
  2. Readjust my timer out. and I deploy the wsp .

And if the first time did not work just try to redeploy for the second time and it pass normally !!

1
  • still same issue. Any other way? Oct 11, 2017 at 8:10

Your Answer

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

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