I thought I should share a problem I came across during my current project were we installed the SP2 for Moss. What we did was that in our SharePoint Server 2007 farm (2 WFEs) we first installed the binaries for both WSS and Moss on all three servers. We then ran the psconfig command psconfig -cmd upgrade -inplace b2b (equal to running the SharePoint Configuration Wizard) to do the updates.
The error message encountered came only on one machine and it came when the command prompt showed the summery of the command. It told us that only 3 out of 4 tasks had completed successfully. When looking in the upgrade log file (found in the 12 hive folder and logs) we found the following error message:
[WebApplicationSequence] [ERROR] [5/19/2009 4:56:08 AM]: Action 12.0.4.0 of Microsoft.SharePoint.Portal.Upgrade.WebApplicationSequence failed.
[WebApplicationSequence] [ERROR] [5/19/2009 4:56:08 AM]: Feature ‘20477d83-8bdb-414e-964b-080637f7d99b’ is not installed in this farm, and can not be added to this scope.
[WebApplicationSequence] [ERROR] [5/19/2009 4:56:08 AM]: at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
We found out that the feature that it refers to is the PublishingTimerJobs so we ran the following stsadm command:
stsadm -o installfeature -name PublishingTimerJobs (you might need to use the -force parameter, we need to do this in another environment)
After the STSADM account we could then re-run the psconfig command with the -force parameter and it worked perfectly.
psconfig -cmd upgrade -inplace b2b -force
Loading ...
[...] quick dig with our old friend google turned up a couple of similar posts from Jukka on Moss and MySharePointofView so I had a look at the 12 hive and to my surprise found that there was no folder for the [...]
Did the above two steps still getting the following error
Failed to upgrade SharePoint Products and Technologies.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
Additional exception information: Upgrade completed with errors. Review the u
pgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
rver Extensions\12\Logs\Upgrade.log. The number of errors and warnings is liste
d at the end of the upgrade log file.
Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of SharePoint Products and Technologies failed. Configuration mus
t be performed before you use SharePoint Products and Technologies. For further
details, see the diagnostic log located at C:\Program Files\Common Files\Micros
oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_8_6_2009_17_35_12_76_173
0697091.log and the application event log.
Do you find anything of use in the upgrade log?
no i have not found anything which could help.
[...] for the SP2 files to install. Thanks to a post from Mattias Karlsson, a colleague of mine, I found this post about how to activate this feature and the details behind the problem. Once the feature was [...]