Monday, April 02, 2012 3:43 PM
I'm trying to deploy a package to administration web application and is stucked at deploying status.
I've tried already other suggestions like
- executing stsadm -o execadmsvcjobs
- restarting the SPTimerv4 and SPAdminV4 services
-killing the above mentioned service processes and starting them again
-rebooting the servers
-removed the deploying solution and retried deployment.
None of them worked
Any further suggestions?
Monday, April 02, 2012 3:47 PM
stsadm -o enumdeployments
to find out the ID and then cancel it using
stsadm -o canceldeployment -id $id
Then you can deploy fresh.
- Edited by Yogesh Pawar Monday, April 02, 2012 3:48 PM
Tuesday, April 03, 2012 6:48 AMI've already tried that both with STSADM and from central admin and when retried deployment it blocks again at deploying status
Tuesday, April 03, 2012 11:41 AM
Tuesday, April 03, 2012 11:55 AM
If server reboot didn't worked, This could be about time zones.
- Edited by ova c Tuesday, April 03, 2012 11:55 AM
Tuesday, April 03, 2012 3:51 PMSeems this does not solve the issue neither
Thursday, April 05, 2012 11:18 AM
Due to time constraints I've recreated the sharepoint databases and deployment and retraction worked, with a single issue of cryptographicerror inside TimerService, but that's another subject.
Thursday, April 05, 2012 12:01 PM
have you tried chaning Log on Account for SharePoint 2010 Timer service if not then try doing:
Run -> services.msc -> SharePoint 2010 Timer service -> Properties -> In that under Log on Section select Log on as Local service account -> And restart the service -> then try fresh deplyoment of you wsp.
Please let me know if this helps you.
Thanks.... ________________ Baba (MCTS, MCPD)
Thursday, April 05, 2012 1:05 PM
Yes, I've had this too. Given that others have already made some good suggestions, I can only tell you what happened and how we resolved it in our situation.
For us, it stemmed from a database server move; when we changed the database server, we set up Aliases on each server in the farm via the SQL Server Configuration Manager. While all appeared ok, for some reason the alias did not work properly on one of the back-end servers. This was first noticed when I tried to deploy a farm solution and it was stuck at a status of 'deploying'.
To cut a long story short, it turns out that the alias was trying to find the original database server, so the Timer job on the back-end server could not run; and it needs the timer jobs on ALL the servers in the farm to run successfully for a deployment to succeed.
Simple solution once we found the problem - delete the alias that wasn't working and recreate it. Worked fine after that. Though unfortunately we still don't know why the alias we created didn't work in the first place.
Hope that helps. If not you, then someone! :-)
- Edited by SPNick Thursday, April 05, 2012 1:06 PM
Thursday, April 05, 2012 1:36 PM
Repair the content database for your webapplication using STSADM
Restart your application pool from the IIS manager and
Friday, April 06, 2012 11:21 AM
I'm having with the deployment further:
1) SPSolution.LastOperationResult instead of being SPSolutionOperationResult.DeploymentSucceeded it is reported as SPSolutionOperationResult.NoOperationPerformed
2) After solution retraction the feature is still preset if I use get-spfeature command
3) I'm using the Microsoft.Practices.SharePoint.Common asembly from Sharepoint 2010 Guidance, for logging, which I'm deploying it in a separate package in the GAC. From my feature event receiver I'm using this logging assembly, and I'm getting an error that assembly Microsoft.Practices.SharePoint.Common cannot be found, although I checked is in the GAC.
Monday, April 09, 2012 10:02 AM
1) I've overcome this issue for forcing SpDeployment job execution
3) I've repackaged the logging assemblies and another assembly which contains the feature receiver code in a separate solution file and deploy it first. But when the second solution file is deployed feature activation fails saying that assembly from previous package is not found, error reported is :
Failed to load receiver assembly "<assemblyName>, Version=0.1.0.0, Culture=neutral, PublicKeyToken=a07d948f87bd
97e2" for feature "FeatureAdmin" (ID: 972558fc-89fd-44b4-b1c7-bea035e9bd4d).: System.IO.FileNotFoundException: Co
uld not load file or assembly '<assemblyName>, Version=0.1.0.0, Culture=neutral, PublicKeyToken=a07d948f87bd97e2' or one of it
s dependencies. The system cannot find the file specified.
File name: '<assemblyName>, Version=0.1.0.0, Culture=neutral, PublicKeyToken=a07d948f87bd97e2'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly loca..
If I deploy only the first solution it works fine, and I checked the GAC the feature receiver assembly is there. I choose also to restart web server after deployment and same error.
I'm really blocked now, any ideas?
- Edited by unciprian Monday, April 09, 2012 10:08 AM