The first steps in resolving this would be to ensure that the SharePoint Administration service is running correctly and potentially try to restart it as described in the forum post. Since the solution was successfully deployed the latest version is actually already applied in your environment only the live framework has not been installed.
Since leaving it for a while eventually allowed the solution to deploy we recommend reviewing the deployment again after some time. Apart from this you can try reviewing the SharePoint logs for any SharePoint errors that may suggest why the deployment became stuck. Please note that any solution you try to deploy at this point will become stuck, this will not only affect our latest version. The way we deploy the solution has not changed between versions and the deployment is controlled entirely by SharePoint.
For issues with the solution package being stuck in deployment.
Can you please try following these instructions. Basically, this will cancel the deployment that is stuck in progress allowing you to start again. Unfortunately, this issue is occasionally seen with SharePoint Solution Packages.
First run this command which will show you all in-progress deployments, there will probably be only the one.
stsadm -o enumdeployments
Look for the JobId string corresponding to the Nintex workflow deployment job
and then run:
stsadm -o canceldeployment -id “you job id string here”
This should cancel the deployment, and if you go to the solution management pages in Central Administration the solution should be listed as ‘not deployed’.
From this point you can try again. We have found that it usually just works the second time; if not the SharePoint logs will need to be analysed to try and determine what is causing the failure.
This stsadm command will do a deployment, the same as pressing the deploy button within the Central Administration UI.
stsadm.exe -o deploysolution -n nintexworkflow2007.wsp -allcontenturls -immediate -allowgacdeployment
Hopefully when you run this command (again, all these commands can be run on the one front end server) it will install correctly.
If the solution package is listed as Error.
Can you please ensure the Windows SharePoint Administrative service is running. To do this please open the services management console (start->run then services.msc) and ensure the service is listed as Started.
Once this has been done you will have to execute the stsadm command:
stsadm.exe –o execadmsvcjobs
Please also check the solution information page by clicking on the solution package link in Central Administration -> Operations. There may also be additional information about the cause of your error.
Testing other simple solution packages in your environment.
There are two simple solutions that will help determine the scope of any issues you are experiencing with solution deployment. They can be used to confirm the issue is global to the environment.
The commands to add the solutions to the solution store is:
stsadm.exe -o addsolution -filename
You can use the Central Administration UI to actually deploy them.
WSP 1:
http://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.zip
This solution deploys globally, it does not require a url to be specified.
It will create a file at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE called TestingSolutionGlobal.txt
If Solution 1 does deploy correctly, then please also try WSP 2 as well, which is slightly more advanced.
WSP 2:
http://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.zip
This solution does require a web application to be selected.
It will create a file at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE called TestingSolutionForWebApps.txt, deploy a file called SimpleSolution.dll to the GAC and add an entry to the web.config file for the web application as follows:
Note that the SimpleSolution.dll contains no code that will execute.
Using the 2 solution packages listed above can help determine if the issue is with the nintexsolutionpackage or all solution packages in general. If these solutions also do not deploy we suggest you contact microsoft for addictional support as this indicates an issue with your SharePoint envrionment, which we are not able to troubleshoot.
Possible causes of your deployement issue / log files to investigate.
Please check your SharePoint logs for the time the solution was schedule to be deployed. The logs are found by default at c:\program files\common files\microsoft shared\web server extensions\12\Logs.
A sample error from a log where we have previously seen this issue:
“The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) threw an exception. More information is included below. An update conflict has occurred, and you must re-try this action. The object IndexingScheduleJobDefinition Name=Indexing Schedule Manager on servername Parent=SearchService Name=OSearch is being updated by DOMAIN\username, in the OWSTIMER process, on machine SERVERNAME. View the tracing log for more information about the conflict.”
these errors suggest a critical timer job error relating to internal SharePoint problems persisting object to the database. These errors also mention ‘update conflict’ as experienced when attempting solution deployment. We believe this underlying issue could be preventing solution deployment and must be resolved.
When seeing errors of these kind you should be able to contact Microsoft directly for additional support as we are not equipped to resolve sharepoint deployement issues.
Cannot retract a solution. Solution stuck at retracting
Other symptoms: Cannot uninstall the LanguagePack 0 because it is not deployed
work around would be to cancel retraction and execute the following command:
stsadm.exe -o deletesolution -name testingsolutionforwebapps.wsp -override
Additional Things to Check:
Have you installed SP1 with/without June 2011 CU? Maybe that’s the problem. Try installing December 2011 CU.
Since leaving it for a while eventually allowed the solution to deploy we recommend reviewing the deployment again after some time. Apart from this you can try reviewing the SharePoint logs for any SharePoint errors that may suggest why the deployment became stuck. Please note that any solution you try to deploy at this point will become stuck, this will not only affect our latest version. The way we deploy the solution has not changed between versions and the deployment is controlled entirely by SharePoint.
For issues with the solution package being stuck in deployment.
Can you please try following these instructions. Basically, this will cancel the deployment that is stuck in progress allowing you to start again. Unfortunately, this issue is occasionally seen with SharePoint Solution Packages.
First run this command which will show you all in-progress deployments, there will probably be only the one.
stsadm -o enumdeployments
Look for the JobId string corresponding to the Nintex workflow deployment job
and then run:
stsadm -o canceldeployment -id “you job id string here”
This should cancel the deployment, and if you go to the solution management pages in Central Administration the solution should be listed as ‘not deployed’.
From this point you can try again. We have found that it usually just works the second time; if not the SharePoint logs will need to be analysed to try and determine what is causing the failure.
This stsadm command will do a deployment, the same as pressing the deploy button within the Central Administration UI.
stsadm.exe -o deploysolution -n nintexworkflow2007.wsp -allcontenturls -immediate -allowgacdeployment
Hopefully when you run this command (again, all these commands can be run on the one front end server) it will install correctly.
If the solution package is listed as Error.
Can you please ensure the Windows SharePoint Administrative service is running. To do this please open the services management console (start->run then services.msc) and ensure the service is listed as Started.
Once this has been done you will have to execute the stsadm command:
stsadm.exe –o execadmsvcjobs
Please also check the solution information page by clicking on the solution package link in Central Administration -> Operations. There may also be additional information about the cause of your error.
Testing other simple solution packages in your environment.
There are two simple solutions that will help determine the scope of any issues you are experiencing with solution deployment. They can be used to confirm the issue is global to the environment.
The commands to add the solutions to the solution store is:
stsadm.exe -o addsolution -filename
You can use the Central Administration UI to actually deploy them.
WSP 1:
http://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.zip
This solution deploys globally, it does not require a url to be specified.
It will create a file at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE called TestingSolutionGlobal.txt
If Solution 1 does deploy correctly, then please also try WSP 2 as well, which is slightly more advanced.
WSP 2:
http://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.zip
This solution does require a web application to be selected.
It will create a file at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE called TestingSolutionForWebApps.txt, deploy a file called SimpleSolution.dll to the GAC and add an entry to the web.config file for the web application as follows:
Note that the SimpleSolution.dll contains no code that will execute.
Using the 2 solution packages listed above can help determine if the issue is with the nintexsolutionpackage or all solution packages in general. If these solutions also do not deploy we suggest you contact microsoft for addictional support as this indicates an issue with your SharePoint envrionment, which we are not able to troubleshoot.
Possible causes of your deployement issue / log files to investigate.
Please check your SharePoint logs for the time the solution was schedule to be deployed. The logs are found by default at c:\program files\common files\microsoft shared\web server extensions\12\Logs.
A sample error from a log where we have previously seen this issue:
“The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) threw an exception. More information is included below. An update conflict has occurred, and you must re-try this action. The object IndexingScheduleJobDefinition Name=Indexing Schedule Manager on servername Parent=SearchService Name=OSearch is being updated by DOMAIN\username, in the OWSTIMER process, on machine SERVERNAME. View the tracing log for more information about the conflict.”
these errors suggest a critical timer job error relating to internal SharePoint problems persisting object to the database. These errors also mention ‘update conflict’ as experienced when attempting solution deployment. We believe this underlying issue could be preventing solution deployment and must be resolved.
When seeing errors of these kind you should be able to contact Microsoft directly for additional support as we are not equipped to resolve sharepoint deployement issues.
Cannot retract a solution. Solution stuck at retracting
Other symptoms: Cannot uninstall the LanguagePack 0 because it is not deployed
work around would be to cancel retraction and execute the following command:
stsadm.exe -o deletesolution -name testingsolutionforwebapps.wsp -override
Additional Things to Check:
Have you installed SP1 with/without June 2011 CU? Maybe that’s the problem. Try installing December 2011 CU.
No comments:
Post a Comment