SharePoint 2013 is really a good product
w.r.t. functionality and awesome GUI to work with! But today’s article is based
on the error that I faced while updating the solution.
IMP NOTE:
If you find a different solution, please report it as a comment to
this post. Be sure to double-verify it: undo your solution and verify that the
problem comes back, then redo it and verify that the problem goes away.
Here is the error
message:
Cannot uninstall Language Pack 0 because it is not deployed when
attempting to uninstall-spsolution
One
thing we always need to understand is the logic would be same for the
functionality irrespective of which SharePoint version you are working!
I
have written one article in the past for SP2010 based on the same concept: http://sharepointknowledgebase.blogspot.com/2013/11/solution-deployment-stuck-on-deploying.html
and today I am going to elaborate more on the same theory as I have resolved
the above mentioned error message with the same funda.
What’s that funda? – Here we go:
If you are facing this error message then I would suggest checking
the status of your solution in central administration. How to check this? Here are
the details:
o Central
Administration
o System Settings
o Manage Farm
Solutions
o It will open the
solution management
o Here you can check
the status of your solution
If your solution is showing updating, deploying or retracting status
then first and top most check that you need to verify the status of your TIMER
JOB across all WFE’s. How to check this?
– Here are the details:
o
Login
to your web front end (WFE)
o
Start
o
Run
o
Type
“services.msc” and hit enter
o
It
will open the services console
o
Click
on any service and press S
o
It
will directly show you the SharePoint Services
o
Second
service will be SharePoint Timer Service
o
Check
the status across all your servers
Two outcomes will
be there:
1. Timer service will be stopped one of the server:
If this is the case then start the timer
job on that specific server and check the results by executing the commands
that you are using.
2. Timer service is started on all the servers:
If this is the case then restart all the
SharePoint Timer Services across all servers. Once this done then execute the
commands that you are doing and check the results
If
you are looking out command reference then please refer this link in which I
have given the reference of add solution as well as update solution:
Details notes:
Add-SPSolution
Add-SPSolution
-LiteralPath c:\nameofyoursolution.wsp
Install-SPSolution
Install-SPSolution
-Identity nameofyoursolution.wsp –GACDeployment
Uninstall-SPSolution
Uninstall-SPSolution
-Identity nameofyoursolution.wsp
Remove-SPSolution
Remove-SPSolution
-Identity nameofyoursolution.wsp
Update-SPSolution
Update-SPSolution
-Identity nameofyoursolution.wsp -LiteralPath c:\nameofyoursolution.wsp
-GACDeployment
If
you have any queries/questions regarding the above mentioned information then
please let me know. I would be more than happy to help you as well as resolves
your issues, Thank you.
Product Applies To:
o
SharePoint
2013
o
SharePoint
2010
o
SharePoint
2007
