There have been many discussions about this error that occurs when running stsadm -o deploysolution to deploy a solution:
The Execute method of job definition "SPSolutionDeploymentJobDefinition" (id "65274d73-2174-417e-b0fa-a63130953ee3") threw an exception. Failed to create feature receiver object from assembly "MyFeaturePack, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9f4da00116c38ec5", type "MyFeaturePack.FeatureReceiverApplyRootUI" for feature 0f9127e3-a930-41a3-8cda-21ded77d996d: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
Common causes of the problem include that (1) the assembly not being deployed to GAC, thereby having code access issue; (2) the signing key is somehow wrong; (3) the class name is not what's defined in feature.xml.
However, this error occurred for a different reason. Actually I still don't know the reason but managed to figure out a solution. Somehow adding the "-force" parameter on stsadm -o deploysolution made it to work for me:
stsadm -o deploysolution -url http://mossdev/ -name MyUI.wsp -immediate -allowgacdeployment -force
Maybe -force wipes out some caching somewhere. Oh well.
Subscribe to:
Post Comments (Atom)
4 comments:
Any idea why you have to use -force? I'm having this same issue in SharePoint 2010.
i m having the same issue, when i removed -force parameter it gives me error
"The Execute method of job definition "SPSolutionDeploymentJobDefinition" (id "fb9b9423-d972-4f8c-a5d1-2d9caa11fb54") threw an exception. One or more error occurred while writing messages into the log."
but with force parameter it works as a charm. any idea y?
Post a Comment