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/ -forceOperation completed successfully.C:\Workflows>stsadm -o uninstallfeature -name IL.SharePoint.Workflows -forceOperation completed successfully.C:\Workflows>stsadm -o retractsolution -name IL.SharePoint.Workflows.wsp -localDeploymentSucceeded : server : The solution was successfully deployed.il.sharepoint.workflows.wsp: Operation completed with errors.C:\Workflows>stsadm -o deletesolution -name IL.SharePoint.Workflows.wspOperation completed successfully.C:\Workflows>stsadm -o addsolution -filename IL.SharePoint.Workflows.wspAn 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.txtAs 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! :)

We are having the exact same error. Anyone having found a solution to this? Best regards,Thomas N. Srensen

Any Luck We are having exact same problem? Thanks Celerity12Thanks

we can deploy any components using solution package (WSP). The below steps ensures that Config refresh timer service occurs. 1. Stop the Windows SharePoint Timer Service 2. Open C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\<<GUID>> folder 3. Take backup of Cache.ini file 4. Delete all the XML files in the GUID folder 5. Open the Cache.ini file in edit mode and delete the contents of it. 6. Type 1.Save and close the file. 7. Start the Windows SharePoint Timer Service.Thanks

I have followed the steps above, and it eliminated the problem that I had, which was identical to the problem that started the thread.Once I followed these steps, I could again add solutions to the store.

celerity12: Please do not propose your own posts. At the time you proposed this there was no response from anyone to indicate that your post helped (you proposed it as an answer simultaneously with posting it). Instead wait for someone else to propose it. If you want to help the forum and its moderators, propose the good answers of *other people* but not your own. (Moderator) Now if someone else will propose the celerity12 post, I can mark it as an answer.FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.

celerity12: I tried a similar set of steps you listed above, but unfortunately ended up with the <<GUID>> folder completely removed. There are no folders in C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\ on my server. Any suggestions as to how to re-gen it?ben

I support an application that deploys a SharePoint solution via an MSI installation package. We recently encountered this error in one of our environments that had been used many times successfully in the past. In conjunction to the error mentioned at the top there was this error in the event viewer on the web server: The INSERT statement conflicted with the FOREIGN KEY SAME TABLE constraint "FK_Objects_Objects". The conflict occurred in database "xxxx_SharePoint_Config", table "dbo.Objects", column 'Id'. Through a series of repeated installation attempts while tracing the activity in the farm's configuration database (using SQL Profiler) I came to the conclusion that the insert statement being generated for the solution was indeed specifying an invalid guid for the objects.parentid field, and of course failing because of the foreign key on that column. I followed the steps above on both web front-end servers in my farm and was then able to run the program (which deployed the solution properly). I did note that after starting the timer service the XML files were immediately regenerated and a new (different than before) value in the cache.ini was added. We were using MOSS 2007 SP2 (64-bit) on Windows 2003 R2 SP2 x64. Thanks again.

This solution worked perfectly........HOWEVER.....if yo'ure in server 2008, the path "C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\<<GUID>> folder " doesn't exist. Use "Drive:\ProgramData\Microsoft\SharePoint\Config\GUID" instead. (some of those folders are hidden by default...may want to adjust that in folder options if you plan on navigating there via mouse.) Hope that saves someone some time.

This Does Work - Saved My Day Did the Guid Cache file edit thing (above) and this worked perfectly. Directories different on different versions of Server 2008 vs 2003. Solved My Problem with... An object in the SharePoint administrative framework, "SPSolutionLanguagePack Name=0 Parent=SPSolution Name= mySolution depends on other objects which do not exist. Ensure that all of the objects dependencies are createdand retry this operation. This was the error and now it is fixed. I had been doing some restores and rebuilds so I asusme that screwed everything up.

This worked perfectly when get-spsolution from powershel did not list my wsp in the list of installed solutions. Thanks CelerityWe the willing, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, with so little, for so long, we are now qualified to do anything, with nothing." ~ Mother Teresa ~

I must add... this worked perfectly in SharePoint 2010We the willing, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, with so little, for so long, we are now qualified to do anything, with nothing." ~ Mother Teresa ~

You could also try creating a new project, copying your source files and deploying from there. But you may leave some unused files in the VS folders if you do this. Jonathan M Beck