I have an odd problem with a farm where solutions are marked as "Not deployed" yet looking at the last operation it shows "Deployed Successfully" and lists all the servers as being successfully deployed to.

My problem is that without having an accurrate picture of whats deployed I cannot be certain that my changes in the solutions are deployed.

I've tried through both powershell and central admin - no errors are raised in either case.

This question: Solution deploying 'succesfully', yet doesn't.. is similar and I'll try that but I am working in SP2013 not MOSS2007.


SharePoint's solution deployment is a bit of a black box. I would try two things:

1) Use -Force on the Install-SPSolution cmdlet to instruct SharePoint to override files, etc., and hopefully result in "Deployed".

2) If #1 doesn't work, I would retract and remove the solution. Then restart the SPAdminV4 and SPTimerV4 Windows Services. Then re-add the solution and use Install-SPSolution with the -Force parameter.

  • Thanks, I tried all of these but unfortunately it was nothing to do with the services but rather a server misbehaving. Taking it out of the farm allowed solutions to deploy correctly. – Mauro Nov 6 '13 at 9:21

While Johns answer had some good information and extra steps to try - i finally discovered a server was not functioning correctly after it had been replaced/rejoined to the domain - never removed/rejoined from the farm though.

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.