Wednesday, April 08, 2009

Microsoft SharePoint 2007 - Fixing a failed WSS v3 and/or MOSS 2007 SP1/Infrastructure Patch Upgrade

The Upgrade Process
I was upgrading an environment (MOSS version in the following manner:
  1. Check all Timer jobs have run to completion in the existing environment
  2. Check no errors with WSP
  3. Install WSS v3 SP1 Patch (Skip Configuration wizard)
  4. Install MOSS 2007 SP1 Patch (Skip Configuration wizard)
  5. Install WSS v3 infrastructure Patch (Skip Configuration wizard)
  6. Install MOSS 2007 infrastructure Patch
  7. Following the prompts for the Configuration Wizard (PSconfigUI).

Okay, so far so good.

The Problems
In the middle of the configuration wizard, it seemed to have stayed on Step 5 for hours. Looking at the Event Viewer, errors with messages:

Content index on Search could not be initialized. Error The content index is corrupt. 0xc0041800.Component: bd72df39-396a-472f-8a1a-db6c3241e922

Checking Upgrade.log (in 12\Logs\), unveiled some Exception errors.

The Solution
So then I cancelled out of the setup (which took a while to cancel – actually it didn’t cancel until I ran the following command), and ran the following command to force the upgrade of the SharePoint environment:

psconfig -cmd upgrade -force

Checked the version numbers and the existing sites I had - That seemed to have fixed my issues

Alternatively, the stsadm utility can be used (though I didn't have to use it):

stsadm -o upgrade -forceupgrade

For more details on this command:
Upgrade: Stsadm operation (Windows SharePoint Services)

Upgrade: Stsadm operation (Office SharePoint Server)

Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Office SharePoint Server)

Install Windows SharePoint Services 3.0 by using the command line

Thursday, April 02, 2009

Microsoft SharePoint - Version numbers

It's been the Nth time I've had to checkup the version of SharePoint that is installed on a Farm - and I am now finally keeping this here for my own notes.

All these times I've been hitting back on a very nice post by Penny Coventry that contains a list of SharePoint Patches and respective version numbers:

The easiest ways I use to check version numbers are:
1. In Central Admin, Site Actions > Site settings:


2. In IIS, right click on the web application and select properties > 'HTTP Headers' tab, under Custom HTTP Headers section: