The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Stefan Goßner — Thu, 26 Feb 2009 10:26:12 GMT

Hi John,

changing the init.js on your own is not supported.

Cheers,

Stefan

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

John — Thu, 26 Feb 2009 00:13:11 GMT

Hi Stefan,

In RTM version of MOSS we had to change the init.js file(and maybe some other things) so multiple postback would work in a page. After applying december CU we seem to have some problems with that. The init.js look's fine but could there be another problem caused by the CU ?

Thanks

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Frank — Mon, 19 Jan 2009 12:57:30 GMT

Hi Björn,

On the Hotfix Request page, above the software selection table, click on the link titled "Show hotfixes for all platforms and languages (2)".

This will trigger the table to show downloads for all platforms, including 64-bit.

Regards,

Frank

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Stefan Goßner — Wed, 14 Jan 2009 17:07:19 GMT

Hi Björn,

just checked. 64-bit is available as well.

Cheers,

Stefan

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Björn — Tue, 13 Jan 2009 16:17:28 GMT

Hi,

Is the cumulative update for december available for 64bit, coz I cant find it?! I can only find a downloadable file for 32bit...

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Bob M — Sat, 20 Dec 2008 22:22:55 GMT

Stefan,

Thanks -- Looks like I have some reading to do :)

Bob M.

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Stefan Goßner — Sat, 20 Dec 2008 21:09:52 GMT

Hi Bob,

the following documentation has the info. It mainly recommends for large farms to speed up things - but it is also best practice to do this to failure with PSCONFIG runs.

http://technet.microsoft.com/en-us/library/cc263467.aspx

Cheers,

Stefan

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Bob M — Sat, 20 Dec 2008 20:15:53 GMT

Stefan,

What documentation are you referring to in your response to Chris? While your answer resolved our problem with the upgrade we would like to know what document we should have read first.

Thanks

Bob M.

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Stefan Goßner — Fri, 19 Dec 2008 11:46:12 GMT

Hi Chris,

regarding the first error:

Our documentation on upgrade recommend detaching the databases before running the hotfix installation and attaching again afterwards to avoid such problems.

Seems you haven't done this.

To recover from this problem, please detach the affected databases now through

STSADM -o preparetomove ...

STSADM -o deletecontentdb ...

Then run PSCONFIG again and afterwards attach the database again using

STSADM -o addcontentdb ...

Regading the problem with the SearchDB: Turn off WSS Search in Central Admin before running PSCONFIG turn it back on after the upgrade has finished.

Cheers,

Stefan

re: The December cumulative update for WSS V3 and MOSS 2007 has been released yesterday

Chris — Fri, 19 Dec 2008 00:39:00 GMT

My installation of these updates are succeed. But the psconfig was failed. Does anyone know can I roll back this update or how to fix it as my moss sites except the CA site are all down now.

Error message from event viewer when browsing the site as below:

The schema version (3.1.5.0) of the database WSS_Content_91_ZZZ_DEV on COMPUTER_NAME1 is not consistent with the expected database schema version (3.1.6.0) on COMPUTER_NAME1. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.

Error message from 12/logs/upgrade.log as below

[SPManager] [ERROR] [12/19/2008 10:09:02 AM]: Upgrade [SPSearchDatabase Name=WSS_Search_XXX_DEV Parent=SPDatabaseServiceInstance] failed.

[SPManager] [ERROR] [12/19/2008 10:09:02 AM]: Object reference not set to an instance of an object.

[SPManager] [ERROR] [12/19/2008 10:09:02 AM]: at Microsoft.SharePoint.Upgrade.SPSearchDatabaseAction.GetSearchContextSearchSqlStringValue(String stringName)

at Microsoft.SharePoint.Upgrade.SearchQFE23318DatabaseAction.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()