I'm having a problem with the deployment of a SharePoint workflow solution - hopefully someone can help me out.
Here is the sequence of STSADM commands and their output from the console:
C:\Workflows>stsadm -o deactivatefeature -name IL.SharePoint.Workflows -url http://localhost/ -force
Operation completed successfully.
C:\Workflows>stsadm -o uninstallfeature -name IL.SharePoint.Workflows -force
Operation completed successfully.
C:\Workflows>stsadm -o retractsolution -name IL.SharePoint.Workflows.wsp -local
DeploymentSucceeded : server : The solution was successfully deployed.
il.sharepoint.workflows.wsp: Operation completed with errors.
C:\Workflows>stsadm -o deletesolution -name IL.SharePoint.Workflows.wsp
Operation completed successfully.
C:\Workflows>stsadm -o addsolution -filename IL.SharePoint.Workflows.wsp
An object in the SharePoint administrative framework, "SPSolutionLanguagePack Name=0 Parent=SPSolution Name=il.sharepoint.workflows.wsp", depends on other objects which do not exist. Ensure that all of the objects dependencies are created and retry this operation.
IL.SharePoint.Workflows.wsp: The Solution installation failed.
Here is the related log info from the SharePoint logs:
error-redacted.txt
As far as I can see, SP is attempting to insert a "SPSolutionLanguagePack" object into the configuration database, with an invalid foreign key reference to the solution. Obviously there is already something fishy going on during solution retraction as well..
The only possible cause I can think of:
The virtual machine(s) on which I'm trying to do this deployment (a test environment) were created from the production environment. Somehow, in the process of creating the virtuals, their OS's regional settings got reset to English/US from their desired setting. I've also got a warning in the event log (event id 2486) of the SP host, that the system locale has changed. Weird thing is that another test environment, created from the same set of virtuals and using the same solution package, is not experiencing this problem. Granted, that environment's regional settings were changed back to the desired values at some point, but I've tried doing the same in the problem environment without success.
Needless to say it's critical for me to be able to test a deployment.. but what's more worrying is that this could occur in the production environment before I've figured out how to solve it.
Any help much appreciated! :)
Here is the sequence of STSADM commands and their output from the console:
C:\Workflows>stsadm -o deactivatefeature -name IL.SharePoint.Workflows -url http://localhost/ -force
Operation completed successfully.
C:\Workflows>stsadm -o uninstallfeature -name IL.SharePoint.Workflows -force
Operation completed successfully.
C:\Workflows>stsadm -o retractsolution -name IL.SharePoint.Workflows.wsp -local
DeploymentSucceeded : server : The solution was successfully deployed.
il.sharepoint.workflows.wsp: Operation completed with errors.
C:\Workflows>stsadm -o deletesolution -name IL.SharePoint.Workflows.wsp
Operation completed successfully.
C:\Workflows>stsadm -o addsolution -filename IL.SharePoint.Workflows.wsp
An object in the SharePoint administrative framework, "SPSolutionLanguagePack Name=0 Parent=SPSolution Name=il.sharepoint.workflows.wsp", depends on other objects which do not exist. Ensure that all of the objects dependencies are created and retry this operation.
IL.SharePoint.Workflows.wsp: The Solution installation failed.
Here is the related log info from the SharePoint logs:
error-redacted.txt
As far as I can see, SP is attempting to insert a "SPSolutionLanguagePack" object into the configuration database, with an invalid foreign key reference to the solution. Obviously there is already something fishy going on during solution retraction as well..
The only possible cause I can think of:
The virtual machine(s) on which I'm trying to do this deployment (a test environment) were created from the production environment. Somehow, in the process of creating the virtuals, their OS's regional settings got reset to English/US from their desired setting. I've also got a warning in the event log (event id 2486) of the SP host, that the system locale has changed. Weird thing is that another test environment, created from the same set of virtuals and using the same solution package, is not experiencing this problem. Granted, that environment's regional settings were changed back to the desired values at some point, but I've tried doing the same in the problem environment without success.
Needless to say it's critical for me to be able to test a deployment.. but what's more worrying is that this could occur in the production environment before I've figured out how to solve it.
Any help much appreciated! :)