Monday, June 22, 2009

Installing a Solution ended with status "Error"

Today I had a problem with installing a solution... :-)
It may sound silly because all you have to do is use stsadm -o addsolution -filename "Location Of File" and then deploy it thought the central admin but this time I got an "Error" in the solution status instead of the expected "deployed".
I could not re-deploy / remove becouse there was already a timer job related to the solution deploy.
After deleting the timer job the solution got back to not deployed status (and so on again and again...)

In the ULS logs I found this error - Updating SPPersistedObject SolutionOperationStatus Name=SolutionOperationStatus Parent=SPSolutionLanguagePack Name=0. Version: -1 Ensure: 0, HashCode: 38896601, Id: 87c32e71-13f0-4d85-a215-29f1d180d239, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.SetOperationResult(SPSolutionOperationResult opResult, String msg, SPWebApplication webApp, Int32 updatesPerServer) at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.DeployFilesInstallFeatures(SPWebApplication webApp, Boolean globalInstallWPPackDlls, Boolean installFeatures, Boolean force, Int32 tries) at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.DeployLocalCore(Boolean globalInstallWPPackDlls, Collection`1 webAppl...

After doing some investigation I found that the reason for the error was that the “Windows Share Point Services Administration” was not stated on one of the farm servers. After the service has been started, the deployment worked just fine...

No comments: