次の方法で共有

PSconfiguration wizard fails to complete after installing new Patches

  • [アーティクル]

SYMPTOMS:

*****************

while trying to run the SharePoint Products and Technologies Configuration Wizard, get the following error

ERROR MESSAGE (If applicable):

****************************************

The specified SharedDatabase Name=Sharepoint_SSP1_AdminDB Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object."

ENVIRONMENT:

*********************

Windows 2003 SP2t, SQL 2005 SP2 and MOSS 2007 SP1

CAUSE:

*********

Cause not sure

RESOLUTION:

******************

Go to Registry editor

Browse HKLM\Software\Microsoft\Office Server\12.0\BuildVersion

Check the build number

If its 12.0.4518.1016

Manually edit the value 12.0.6219.1000

Close the registry editor

Run the PSconfiguration wizard and it will be Successful

ADDITIONAL INFORMATION: TO - RESOLVE

*******************************************************

The Error says " The databases are been upgraded to a newer version. Please upgrade this SharePoint application server before attempting to access this object"

where the Binary is on a lower build then the database

When we checked on the central administration window, it shows 12.0.6332

when we checked the above registry key found even after installing the SP1 on the MOSS Server the build was 12.0.4518.1016, as it should be 12.0.6219.1000

When installing the Cumulative, it will check the build version in the registry, where it was 12.0.4518.1016

Comments

  • Anonymous
    February 21, 2009
    PingBack from http://www.anith.com/?p=12502

  • Anonymous
    March 02, 2009
    many thanks for your guidance. Awesome!

  • Anonymous
    May 31, 2010
    We upgraded MOSS to SP2 and April 09 CU, but the registry key still shows version 12.0.6219.1000. In the add/remove programs>windows updates it shows SP2 as one of the updates, and the central admin shows 12.0.0.6504 as the version on the servers. Why is the registry not updated? Is it a known issue, and how can we fix it? Thanks.