After installing WSS hotfix 941422my WSS 3.0does not work any more. I can open Central Admin site but I can not open any other sites. I am very glad if somebody can help me ASAP! Looks like cant uninstall it any more and I dont know what to do now. Should I really restore my whole server? First I installed the hotfix pack and then run the Sharepoint Configuration wizard many times. Every time I get the following errors: Event Type:ErrorEvent Source:Windows SharePoint Services 3Event Category:Topology Event ID:5617Date:27.09.2007Time:10:03:16User:N/AComputer:ORAVDescription:The schema version (3.0.149.0) of the database WSS_Content_root.f24 on ORAV is not consistent with the expected database schema version (3.0.150.0) on ORAV. 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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Failed to upgrade SharePoint Products and Technologies. Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log. An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.Initialize() at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Try running: stsadm -o upgrade -inplace -url http:// {web application URL} Replace'web application URL' with the URL of the site collection(s) causing the problem. Regards, Chris W

Thank you for your answer.I tried this, but no success. First I tried this with my company site and answer was as you can see here and then I tried it with Central admin site and error text was exactly the same. What else I can do?D:\TEMP_D>stsadm -o upgrade -inplace -url http://mysite.comThe specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newerversion of SharePoint. Please upgrade this SharePoint application server beforeattempting to access this object.In Event Viewer I found also this:Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: Database Event ID: 3759Date: 28.09.2007Time: 0:18:09User: N/AComputer: ORAVDescription:Database 'SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553' on SQL Server instance 'ORAV' is not empty and does not match current database schema.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

What was output on the commandline once you ran the command? Did you try running the SharePoint Config Wizard again afterwards? Also, try running "stsadm -o upgrade -inplace" without the URL part and check the upgrade.log again once you have rim the Config Wizard! Regards, Chris

Output on the command line was like I wrote before: D:\TEMP_D>stsadm -o upgrade -inplace -url http://mysite.comThe specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newerversion of SharePoint. Please upgrade this SharePoint application server beforeattempting to access this object. I tried also Wizard after that and it gave me the same text: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newerversion of SharePoint. Please upgrade this SharePoint application server beforeattempting to access this object. I checked also the upgrade.log after "stsadm -o upgrade -inplace" without the URL: [SPManager] [DEBUG] [9/28/2007 1:52:17 AM]: Logging enabled Friday, September 28, 2007 at 1:52:17 AM.[SPManager] [INFO] [9/28/2007 1:52:17 AM]: Upgrade Boot Strap starts. Initialized in Mode: InPlace, as MachineAdmin: True.[SPManager] [DEBUG] [9/28/2007 1:52:17 AM]: Detected v3 configuration database dsn: Data Source=ORAV;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False.[SPManager] [DEBUG] [9/28/2007 1:52:17 AM]: Detected v2 configuration database dsn: Data Source=ORAV\SharePoint;Initial Catalog=STS_Config;Integrated Security=True.[SPManager] [DEBUG] [9/28/2007 1:52:17 AM]: Ensuring local security groups.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Begin registering Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Using assembly manifest Microsoft.SharePoint.UpgradeAssemblyManifest.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 0, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 1, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceSequence] for [Microsoft.SharePoint.Administration.SPService], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceInstanceSequence] for [Microsoft.SharePoint.Administration.SPServiceInstance], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServerSequence] for [Microsoft.SharePoint.Administration.SPWebServiceInstance], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServiceSequence] for [Microsoft.SharePoint.Administration.SPWebService], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebTemplateSequence] for [Microsoft.SharePoint.SPWebTemplate], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence] for [Microsoft.SharePoint.Search.Administration.SPSearchDatabase], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseMigrator] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteCollectionMigrator] for [Microsoft.SharePoint.Administration.SPMigratableSiteCollection], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationMigrator] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServerMigrator] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: End registering Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:52:18 AM]: Reading xml configuration files from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:52:18 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\gbwupgrade.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:52:18 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\MpsUpgrade.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:52:18 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\MpsUpgradeB2B.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:52:18 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\WssUpgrade.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:52:18 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\WssUpgradeB2B.xml.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Begin registering Microsoft.GroupBoard, Version=12.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: No assembly manifest found.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPDatabaseGbwSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 2147483647, Order: 31.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteGbwSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 31.[SPDelegateManager] [DEBUG] [9/28/2007 1:52:18 AM]: End registering Microsoft.GroupBoard, Version=12.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.[SPManager] [DEBUG] [9/28/2007 1:52:18 AM]: CanUpgrade [SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance] returned: True.[SPManager] [DEBUG] [9/28/2007 1:52:18 AM]: NeedsUpgrade [SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance] returned: False.[SPManager] [INFO] [9/28/2007 1:52:18 AM]: Ensure the config cache [C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\3359af48-0cf8-4665-9035-7ac8fc343d0d\] exists.[SPManager] [INFO] [9/28/2007 1:52:18 AM]: Adding NetworkService to the Security registry ACL[SPManager] [INFO] [9/28/2007 1:52:18 AM]: NetworkService successfully added to the Security registry ACL[SPManager] [DEBUG] [9/28/2007 1:52:18 AM]: This local server is joined to a farm.[SPManager] [DEBUG] [9/28/2007 1:52:18 AM]: Using SPFarm Name=SharePoint_Config.[SPManager] [DEBUG] [9/28/2007 1:52:18 AM]: Using cached [SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.[SPManager] [DEBUG] [9/28/2007 1:52:18 AM]: CanUpgrade [SPFarm Name=SharePoint_Config] returned: True.[SPManager] [DEBUG] [9/28/2007 1:52:18 AM]: NeedsUpgrade [SPFarm Name=SharePoint_Config] returned: False.[SPManager] [DEBUG] [9/28/2007 1:52:19 AM]: Attempt to upgrade administration content database SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance[SPDatabaseGbwSequence] [ERROR] [9/28/2007 1:52:19 AM]: Upgrade object too new (build version = 12.0.0.6036, schema version = 3.0.1.0). Current server (build version = 12.0.0.4518, schema version = 3.0.1.0).[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: CanUpgrade [SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance] failed.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: ReflexiveCanUpgrade [SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance] failed.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: SPManager.Initialize failed.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.Initialize()[SPManager] [INFO] [9/28/2007 1:52:19 AM]: Upgrade Boot Strap finishes. 4 errors and 0 warnings encountered.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: Upgrade failed.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [9/28/2007 1:52:19 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.Initialize() at Microsoft.SharePoint.StsAdmin.SPUpgrade.RunUpgrade(StringDictionary keyValues) Then I tried once again Wizard, result in pupgrade.log: [SPManager] [DEBUG] [9/28/2007 1:55:53 AM]: Logging enabled Friday, September 28, 2007 at 1:55:53 AM.[SPManager] [INFO] [9/28/2007 1:55:53 AM]: psconfig: Creating the upgrade manager and setting properties prior to bootstrapping upgrade[SPManager] [INFO] [9/28/2007 1:55:53 AM]: psconfig: Setting the upgrade mode to inplace[SPManager] [INFO] [9/28/2007 1:55:53 AM]: psconfig: Bootstrapping upgrade by calling SPManager.Initialized()[SPManager] [INFO] [9/28/2007 1:55:53 AM]: Upgrade Boot Strap starts. Initialized in Mode: InPlace, as MachineAdmin: True.[SPManager] [DEBUG] [9/28/2007 1:55:53 AM]: Detected v3 configuration database dsn: Data Source=ORAV;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False.[SPManager] [DEBUG] [9/28/2007 1:55:53 AM]: Detected v2 configuration database dsn: Data Source=ORAV\SharePoint;Initial Catalog=STS_Config;Integrated Security=True.[SPManager] [DEBUG] [9/28/2007 1:55:53 AM]: Ensuring local security groups.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Begin registering Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Using assembly manifest Microsoft.SharePoint.UpgradeAssemblyManifest.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 0, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 1, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceSequence] for [Microsoft.SharePoint.Administration.SPService], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceInstanceSequence] for [Microsoft.SharePoint.Administration.SPServiceInstance], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServerSequence] for [Microsoft.SharePoint.Administration.SPWebServiceInstance], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServiceSequence] for [Microsoft.SharePoint.Administration.SPWebService], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebTemplateSequence] for [Microsoft.SharePoint.SPWebTemplate], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence] for [Microsoft.SharePoint.Search.Administration.SPSearchDatabase], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseMigrator] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteCollectionMigrator] for [Microsoft.SharePoint.Administration.SPMigratableSiteCollection], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationMigrator] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Registering [Microsoft.SharePoint.Upgrade.SPServerMigrator] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: End registering Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:55:53 AM]: Reading xml configuration files from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:55:53 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\gbwupgrade.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:55:53 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\MpsUpgrade.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:55:53 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\MpsUpgradeB2B.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:55:53 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\WssUpgrade.xml.[SPXmlConfigurationManager] [DEBUG] [9/28/2007 1:55:53 AM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\Upgrade\WssUpgradeB2B.xml.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: Begin registering Microsoft.GroupBoard, Version=12.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:53 AM]: No assembly manifest found.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:54 AM]: Registering [Microsoft.SharePoint.Upgrade.SPDatabaseGbwSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 2147483647, Order: 31.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:54 AM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteGbwSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 31.[SPDelegateManager] [DEBUG] [9/28/2007 1:55:54 AM]: End registering Microsoft.GroupBoard, Version=12.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: CanUpgrade [SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance] returned: True.[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: NeedsUpgrade [SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance] returned: False.[SPManager] [INFO] [9/28/2007 1:55:54 AM]: Ensure the config cache [C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\3359af48-0cf8-4665-9035-7ac8fc343d0d\] exists.[SPManager] [INFO] [9/28/2007 1:55:54 AM]: Adding NetworkService to the Security registry ACL[SPManager] [INFO] [9/28/2007 1:55:54 AM]: NetworkService successfully added to the Security registry ACL[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: This local server is joined to a farm.[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: Using SPFarm Name=SharePoint_Config.[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: Using cached [SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: CanUpgrade [SPFarm Name=SharePoint_Config] returned: True.[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: NeedsUpgrade [SPFarm Name=SharePoint_Config] returned: False.[SPManager] [DEBUG] [9/28/2007 1:55:54 AM]: Attempt to upgrade administration content database SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance[SPDatabaseGbwSequence] [ERROR] [9/28/2007 1:55:54 AM]: Upgrade object too new (build version = 12.0.0.6036, schema version = 3.0.1.0). Current server (build version = 12.0.0.4518, schema version = 3.0.1.0).[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: CanUpgrade [SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance] failed.[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: ReflexiveCanUpgrade [SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance] failed.[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: SPManager.Initialize failed.[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [9/28/2007 1:55:54 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.Initialize()[SPManager] [INFO] [9/28/2007 1:55:54 AM]: Upgrade Boot Strap finishes. 4 errors and 0 warnings encountered. Actually I dont understand what it is about "upgrade"? I did not tried to upgrade the WSS or something. Only thing I did before problems started was installing the hotfix. Is it also like "upgrade"?

OK, hopefully this should get you fixed (run from the command line): psconfig cmd upgrade inplace b2b wait force Be sure to do a backup first if you haven't already done one recently. The use of the word 'upgrade' is a bit ambiguous. I believe that when you install a hotfix, you essentially 'upgrade' SharePoint. Installing a hotfix will increment the version number of SharePoint and also the database schema version number if changes have been made to it. Regards, Chris

I already hoped, but....C:\Documents and Settings\Administrator>psconfig -cmd upgrade -inplace b2b -wait-forceSharePoint Products and Technologies Configuration Wizard version 12.0.6023.5000Copyright (C) Microsoft Corporation 2005. All rights reserved.Performing configuration task 1 of 4Initializing SharePoint Products and Technologies upgrade...Successfully initialized SharePoint Products and Technologies upgrade.Performing configuration task 2 of 4Initiating the upgrade sequence...Failed to initiate the upgrade sequence.An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.Total number of configuration settings run: 2Total number of successful configuration settings: 1Total number of unsuccessful configuration settings: 2Successfully stopped the configuration of SharePoint Products and Technologies.Configuration of SharePoint Products and Technologies failed. Configuration must be performed before you use SharePoint Products and Technologies. For furtherdetails, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_9_28_2007_3_7_45_740_2068794376.log and the application event log.

OK, is the hotfix showing in add/remove programs and have you tried running the hotfix again? Same result or message saying it is already installed?

Yes it is showing in Add-Remove but it cant be uninstalled. I tried to install it again many times and it says: Hotfix for WS (KB941422) "The update is already installed on this system".

Thank you for your support, but I coudnt find any solution and did server restore to 3 days old state. My mistake that I didnt have a everyday backup. But I connected all my WebApps content databases to new restored WSS and they started to work! I am suprised. That means, I restored 3 days old Central Admin content and databases but all other databases are newer. Yes it works but I am a bit worried, may be I will have some problems in future? Is there some important Information about other WebApps in Central Admin databases?

Chris Whitehead - MSFT wrote: OK, is the hotfix showing in add/remove programs and have you tried running the hotfix again? Same result or message saying it is already installed? OK I've got the same situation as the original post. I know a few hotfixes had been updated on my 2003 Server and I have uninstalled them. I still have the same Newer Version senario. I have tried to do the inplace upgrades but the exact same things are happening as the original post. Any Ideas? I don't have the luxury of a backup at this point and would like to recover the data ( this is a testbed server but I got caught up in one of the templates and added essential data)Thanks!

I began having the same error last night after I (will I never learn) ran the sharepoint "update". I found this forum and tried allsolutions above with the same results. Also I cannot access the WSS cnetral admin site either. Event log: The specified SPContentDatabase Name=SharePoint_AdminContent_c4fe7f9b-537d-4dbd-a862-1eac6ea5bcc9 Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. And this entry along with it: Database 'SharePoint_AdminContent_c4fe7f9b-537d-4dbd-a862-1eac6ea5bcc9' on SQL Server instance 'WIN2K3\Microsoft##SSEE' is not empty and does not match current database schema. I also tried toreturn all rowsfrom the sahrepoint DBs in MS SQL 2005 Express management studio installed lcoally and I get a long SQL message that sums it all up with this: SQL Execution Error...blahblah siteID, ID, title... Error source: .Net SqlClient Data Provider Error Message: Access to table dbo.<any table I choose> is blocked because the signature is not valid. Seriously... why release such a hotfix without enough testing to catch a minor issue like... crashing a mission critical service?

Hi, all.I'm experiencing the same thing with my installation. Fortunately, it's on our test server, but I would very much like to avoid reinstalling the whole thing. Last week I got the updates installed (KB 937832 and KB 934525). At first, they failed, but I managed to install them manually. You can read all about it on my blog: http://frankonmoss.blogspot.com/2007/10/automatic-windows-update-didnt-update.html.However, I've spend all this day trying to find out what has gone wrong with my installation, and finally I found this forum thread.MS, do you have any solution for this? Please advice!!Frank

Not that it finally worked when I got it, but copy and pasting the above results in the quizical "The -cmd command is invalid" It appears that there are hidden characters which cause the above to fail, also psconfig was not in my search path. Running C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>psconfig -cmd upgrade -inplace b2b -wait -force results in: SharePoint Products and Technologies Configuration Wizard version 12.0.6023.5000Copyright (C) Microsoft Corporation 2005. All rights reserved. Performing configuration task 1 of 4Initializing SharePoint Products and Technologies upgrade... Successfully initialized SharePoint Products and Technologies upgrade. Performing configuration task 2 of 4Initiating the upgrade sequence... Failed to initiate the upgrade sequence. An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Action 3.0.1.0 of Microsoft.SharePoint.Upgrade.SPFarmSequence failed. Total number of configuration settings run: 2Total number of successful configuration settings: 1Total number of unsuccessful configuration settings: 2Successfully stopped the configuration of SharePoint Products and Technologies.Configuration of SharePoint Products and Technologies failed. Configuration must be performed before you use SharePoint Products and Technologies. For further details, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_10_15_2007_15_18_7_7_884021493.log and the application event log.

Add one more admin who's having the exact same issues. I'm completely stumped here. Calling support tomorrow afternoon, may be able to shed some light on the issue.

Well, I am close to the same point after running the psconfig line mentioned... Mine failed at configuration task 3 of 4. Performing configuration task 3 of 4Upgrading SharePoint Products and Technologies... 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 upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log. The number of errors and warnings is listed at the end of the upgrade log file. Total number of configuration settings run: 3Total number of successful configuration settings: 2Total number of unsuccessful configuration settings: 1Successfully stopped the configuration of SharePoint Products and Technologies.Configuration of SharePoint Products and Technologies failed. Configuration must be performed before you use SharePoint Products and Technologies. For furtherdetails, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_10_19_2007_11_28_14_132_891936915.log and the application event log. Anybody have any other suggestions or answers yet? Thanks!

In order to resolve the issues you are experiencing, please implement the following steps on each machine that failed the upgrade sequence: On the machine wherepsconfig failed to start the SPAdmin service run: %commonprogramfiles%\Microsoft Shared\Web Server Extensions\12\BIN\psconfig -cmd upgrade -inplace b2b -wait -force Modify the service timeout values in the Registry: HKLM\SYSTEM\CurrentControlSet\Control add/modify DWORD value ServicesPipeTimeout to 60000 (60 seconds) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control add/modify STRING value WaitToKillServiceTimeout to 120000 (120 seconds) Restart the server machine. For additional support and troubleshooting visit http://blogs.technet.com/wbaer/archive/2007/10/15/kb934525-troubleshooting.aspx.

Ladies and gentlemen, after calling MS support and working through the trouble ticket, I have an answer that worked for our team. First off, facts about the issue for our environment that should be fairly close to yours: - You are running a WSSv3 instance with a Microsoft SQL Server Embedded Edition (SSEE)database running on the same server - You applied KB 934525 while IIS was running and users were still hitting the database - SharePoint Web Applications and Central Administration sites were inaccessible post-update or reboot - You've tried to manually update your site via the following methods and failed: -- stsadm -o upgrade -inplace -url http://siteurl -forceupgrade -- psconfig -cmd upgrade -inplace b2b -force -wait -- downloaded KB934525 and ran msiexec.exe /extract to get the .dwp patch, running that manually Based on all these criteria, the issue is that KB934525 updated your configuration database, but not your content database or your application files. This is because the patch does not put your content database in single-user mode during install. What you'll have to do is make a copy of your current content database, completely uninstall WSSv3 and SSEE, then re-install WSSv3, foregoing any patches, and attach your content database to a new Web Application. Please note that I have not tested this on a MOSS 2007 install, nor did we have any extra solutions or features installed, so YMMV. Steps: 1) Open services.msc and stop the "SQL Server 2005 Embedded Edition (MICROSOFT##SSEE)" service. 2) Navigate out to "%SYSTEMROOT%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data" and copy your content database MDF and LDF to a different location. They should look like "WSS_Content.mdf" and "WSS_Content_log.ldf", or "WSS_Content_[long hex value].mdf" and "WSS_Content_[long hex value]_log.ldf". If you are unsure, grab them all. 3) Uninstall Windows SharePoint Services through Add/Remove Programs. If you're unable to do this: 3a) Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-1014-0000-0000-0000000FF1CE}] in the registry 3b) Copy the "UninstallString" value and append " CALLERID=OCSETUP.EXE" to the end of the string 3c) Run what you have in a command prompt 4) Uninstall SSEE. You can't do this through Add/Remove Programs so: 4a) Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB}] in the registry 4b) Copy the "UninstallString" value and append " CALLERID=OCSETUP.EXE" to the end of the string 4c) Run what you have in a command prompt 4d) The uninstaller will not delete the databases in "%SYSTEMROOT%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data", so if you feel comfortable, you can delete everything in the "%SYSTEMROOT%\SYSMSI" folder after you've made copies of your content databases 5) Re-install Windows SharePoint Services and run the SharePoint Configuration Products and Technologies wizard. You should now have a working Central Administration site and empty Web Application. 6) Delete the Web Application that was created for you and create a new Web Application that mirrors your old Web Application's settings (if you had anything special, like port number, secure socket layer enabled, or load balanced URL, make sure you enter those settings). 7) Remove the new Web Application's content database. To do this: 7a) In Central Administration, navigate to "Application Management" > "Content databases". Ensure the Web Application selected is the Web Application you just created (drop-down menu on the right-hand side) 7b) Click "WSS_Content" 7c) The last option on the "Manage Content Database Settings" page is a checkbox next to "Remove content database". Click this checkbox, then "OK". Acknowledge any warnings that may show up 8) This is where things get tricky. For this part, you'll need to install SQL Server Management Studio Express (SSMSE) directly on the server if it isn't already installed. The download URL is: http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en 9) Connect to the SSEE database through SSMSE. SSEE is locked down pretty hard and you can't connect remotely, hence needing to install SSMSE directly on the server. To get the server name: 9a) Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MICROSOFT##SSEE\MSSQLServer\SuperSocketNetLib\Np] in the registry 9b) Copy the "PipeName" value and enter that in the "Server name" field when SSMSE asks you to connect to a server 10) Delete any existing "WSS_Content" databases through SSMSE 10a) Expand the "Databases" folder 10b) Right-click a database starting with "WSS_Content" 10c) Click "Delete", then "OK" in the resulting dialog 11) Move your backed-up "WSS_Content" MDF and LDF files into the "%SYSTEMROOT%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data" folder 12) Attach your backed-up databases. To do this: 12a) Right-click the "Databases" folder in SSMSE, then "Attach..." 12b) Click the "Add..." button.Traverse the file system to "%SYSTEMROOT%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data" and select your content database's MDF, then click "OK" 12c) In the "Databases to attach:" table, there will be a column called "Attach As". Expand this column and write down what's there.This will be the name of your database when you attach it.If you want to change the name, you can do so by single-clicking the field and changing the name as you please. 12d) In the "[database name] database details table, there should be two rows with "Not Found" in the "Message" field of both rows.To fix this, click the "..." button next to the path in the "Current File Path" field and traverse to the correct files. The "Not Found" message may not go away immediately, but click "OK" anyway to attach the database. 13) You can close out SSMSE now if the database attached correctly. Open services.msc and stop the World Wide Web Publishing service. 14) Open a command prompt and traverse to "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN" 15) Moment of truth...issue the following command: stsadm -o addcontentdb -url http://siteurl -databasename [your content database name] 16) Provided you didn't get any error messages, start the WWW Publishing service. Go back out to your Central Administration site, then "Application Management" > "Content databases". There should now be an entry for the content database you just attached. 17) Make any more changes in IIS Manager if you need to (attaching SSL certificates, changing SSL port, etc.), then try visiting your Web Application's URL. If all worked out well, you should be looking at your site. Hopefully this should help with anybody that's pulling their hair out over this issue. BTW, if you want to try installing KB934525 again, you can do so - just MAKE SURE that the WWW Publishing service is stopped before doing so - this will ensure that no one tries to access SharePoint. Many, many thanks to Ajitha Srivastava (ajithas [at] microsoft dot com if you want to drop a thank-you note) for helping me figure this out. Good luck to all the admins out there!

I'm having the same issue as everyone else. My error is: An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_3661411e-8f8a-4403-8308-28ca88083dd8 Parent=SPDatabaseServiceInstance Name=sdbtst04 has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. I've tried the psconfig and stsadm commands already and still get the above error. I haven't found a solution yet and am considering starting over. Luckily this is on my evaluation server and not in production. My configuration: 1 front end server running MOSS 2007 1 back end SQL 2005 server I can't uninstall WSS only since I'm running MOSS. I could uninstall MOSS and reinstall it if that would work, I haven't tried that yet. Any help is appreciated. Thanks, Daniel

How did you restore to 3 days old state? through data , backup whole server? Thanks,

How did you restore to 3 days old state? through restoring data , restoring the whole server backup?

Sara, Our fix action did not involve a restore - we essentially blew away our existing WSS install, but kept the content database files (MDF and LDF). You can attach a valid content database to a new Web Applicationusing[stsadm -o addcontentdb] and the config DB will figure out the rest. As I mentioned, this was a no-frills WSS install...no MOSS, no features, etc. so I'm not sure how one would go about restoring stuff like that.

I did everything you posted and never got an error but I still can't get to any of my pages now. Is there something I'm forgetting? Tom

Couple of things you could check out...I did have issues getting our new Web Application to work with the existing content db (especially with SSL and "require client certificates" turned on...nobody should ever have to manage a site with that kind of security). First, most important thing is to turn off IE's friendly errors so you know exactly what status code you're getting when you try to hit your site. 401s and 403s point to authentication/authorization issues while 500s usually mean some code didn't execute properly. SharePoint also likes to throw 404s (file not found, and also most likely what you're getting). Aside from that, here's the checklist I'd recommend: - SharePoint services installed and up? (at the very least, Administration and Timer) - Central Admin site IIS configuration looks good? (look at the Directory Security tab and check your HTTP/HTTPS ports) - Central Admin site available? - New Web Application created properly? (check port and load-balanced URL) - Web Application site IIS configuration looks good? (again, focus on Directory Security and ports) - New Web Application works with a blank content db? - Blank content db removed? - stsadm -o addcontentdb command worked properly? - Original content db shows up in "Application Management" > "Content databases" after add? - Web Application works with original content db? That's all I have for this round. Hope you have better luck!

I experienced the similar problem, and I was able to get it fixed by running the following command only: stsadm -o upgrade -inplace -url http://{central_admin_web_application_url} Before you apply the above fix, open the Versions table in the related database that is described in the event log, and you would see the previous schema version (3.0.149.0). The above solution would modify it to the expected database schema version (3.0.151.0). FYI, in my case, there is no need to run the above command for each web application, just central admin web application. For more info: http://iweblogs.blogspot.com/2007/11/event-id-5617-after-installing-hotfix_21.html.

OMG I am having the same issues after upgradeing to Service Pack 1!!! WTF, I backed up everything thinking I could restore and I cannot restore my admin or config databases! They actually say this in the fine print. What possible good is there in backing up a databse if you can't restore it! This is a mess. Anyone know of a fix? Can I restore my content databases somehow. Good gawd...what a mess.

Hello,it was long time ago when I started this thread. Last time I juste recovered my server from backup.And guess what? Today I tried to install SP1 to my WSS 3.0 and looks like I got the same error!*************************[SPManager] [DEBUG] [1/15/2008 3:31:51 PM]: Attempt to upgrade administration content database SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance[SPDatabaseGbwSequence] [ERROR] [1/15/2008 3:31:51 PM]: Upgrade object too new (build version = 12.0.0.6219, schema version = 3.0.1.0). Current server (build version = 12.0.0.4518, schema version = 3.0.1.0).[SPManager] [ERROR] [1/15/2008 3:31:51 PM]: CanUpgrade [SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance] failed.[SPManager] [ERROR] [1/15/2008 3:31:51 PM]: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.[SPManager] [ERROR] [1/15/2008 3:31:51 PM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)********************************Should I really stop installing any hotfixes to my server?I tried also the command as Mr.Bill Baer from Microsoft mentioned but result was:********************************C:\Documents and Settings\Administrator>"c:\program files\common files\MicrosoftShared\Web Server Extensions\12\BIN\psconfig" -cmd upgrade -inplace b2b -wait -forceSharePoint Products and Technologies Configuration Wizard version 12.0.6217.1000Copyright (C) Microsoft Corporation 2005. All rights reserved.Performing configuration task 1 of 4Initializing SharePoint Products and Technologies upgrade...Successfully initialized SharePoint Products and Technologies upgrade.Performing configuration task 2 of 4Initiating the upgrade sequence...Failed to initiate the upgrade sequence.An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_823d6056-4414-409e-8149-233cd8606553 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.Total number of configuration settings run: 2Total number of successful configuration settings: 1Total number of unsuccessful configuration settings: 2Successfully stopped the configuration of SharePoint Products and Technologies.Configuration of SharePoint Products and Technologies failed. Configuration must be performed before you use SharePoint Products and Technologies. For furtherdetails, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_1_15_2008_15_46_29_615_212759320.log and the application event log.****************************

Answer to Sara_111.I restored the whole HDD image with Acronis. About 30 minutes and it was restored.My server booted up again after restore and I connected to it by Remote Desktop.

I decided to finish this nightmare.My choice was to try uninstall and reinstall WSS 3.0. I did it and after that I hadnt any problem with installing the SP1.But I didnt uninstall SQL Server 2005 as derelictstatic did.Actually reinstalling WSS wasnt so easy because I have couple Web Applications and some of them have FBA.My steps:1. First of all I did backup of all sites with stsadm.exe. Then full backup of HDD image with Acronis. Backup of all web directory files (I needed old web.config files for my FBA) and backup of SQL database files after taking SQL offline.2. First attempt to uninstall WSS was through Add Remove Application. No success.3. Next try was uninstalling by command line as hint in derelictstatis post. No result, I tried three times but looked like it took off only part of it.4. Then i just deleted all the Web Apps and WSS directory somewhere under Program Files.5. Installed WSS 3.0, all was ok.6. Uninstalled it once again, just for case. Now I could do this from Add Remove Application.7. Installed again WSS 3.0, installed language pack.8. Created Web Apps. 9. Tried to connect webapps to old database files. All connected normally but sites didnt open after that. Any ideas? 10. Deleted again all these messed Web Apps. Created new ones and new empty site collections on them.11. Restored my Site Collections.12. Configured again my FBA.11. Backup of HDD with Acronis. I was pretty sure that installing of SP1 will fail :-).13. Installing SP1 with success! I cant believe this! 14. Installing language packs SP1.Now looks like everything works but I am not very sure, maybe I didnt uninstall my WSS correctly and there are some messed rows in my registry now or what ever. May be somebody can tell me something about that, should I check something?Thank you to derelictstatic for good hints.Tegija<!--[if !supportLineBreakNewLine]--><!--[endif]-->

We were getting the "upgraded to a newer version" error plusthe search, all timer jobs, upgrading templates and incoming e-mail weren't working. What worked for us was: Backup databases Uninstall the GroupBoard from Add Remove Programs on the SharePoint server Restart IIS and Timer services STSADM.EXE" -o upgrade -inplace -forceupgrade -url <webapplication> (Do this for each web application that is on the server including the Central Administration). psconfig -cmd upgrade -inplace b2b -wait -force

We just had this issue today....Some background - we have a deployment server on our internal firewall, which connects to the other side of our firewall to an application server (via Content Deployment). From there, the site is served by two web front-ends. We have caching enabled on the site as well ( I believe between 90 minutes and two hours).Now - the issue was that we needed to install the patch described by KB938536 on our servers. We installed on our deployment server on Friday (1/25/2008) and ran into the issue where Central Admin and the site would not load. After some digging, I found a different forum that had the commands described earlier to fix the issue: stsadm -o upgrade -inplace -url http://<URL> -forceupgrade stsadm -o upgrade -inplace -urlhttp://<URL> -forceupgrade psconfig cmd upgrade inplace b2b wait force...and that fixed the issue.So today - we tried installing the patch on our application server, and then both the site and Central Admin would not load again...so I figured I knew what to do...nope, all 3 commands above failed (also tried to run the commands on one of our WFE's and it failed there too...the event log mentioned the version number being out of sync, so I went into 4 databases and manually changed the version number to '3.0.150.0' in the versions table and it fixed everything...or so I thought.Approximately 90 minutes from the point I 'fixed' everything, the site went down...first on one of the WFE, and then the other one with a database error. When viewing from the public facing URL, the user was returned a weird 404 error from the database. I tried running stsadm and psconfig agani but got the error on Step 2 of 4. Searching the error returned was what brought me to this forum. Un-installing MOSS was a last-ditch effort, and restoring from backup wasn't an option we wanted to take. So I went back into the database and changed the version information back to what it was previously in reverse order. After the 3rd change back I decided to do an iisreset on my WFE (although I don't think the iisreset had anything to do with it)...and the site loaded! Also - my Central Admin is loading from my Application server as well, so everything is fixed to pre-patch state (I believe) with the patch still installed.Anyone with this issue should try this and see if it works. Right now the site has been working for 30 minutes no problem, and I don't think it should fail but I can't guarantee anything at this point, but it looks promising.Good luck to those trying to get thru this issue!Ranjeet

Anonymous - thanks for that you're a life saver. Had tried everything previously mentioned except uninstalling WSS - the forceupgrade switch that you suggested made the difference and we're back up and running. Hope yours stayed fixed! Thought MS stopped publishing hotfixes that broke things in the '90s?

Try removing the content databases from the web applications using STSADM preparetomove and removecontentdb and then running the "SharePoint Products and Technologies Configuration Wizard". If this then runs successfully add the content database back to the web application using STSADM addcontentdb, this should then upgrade the content database to the same as your environment

I have a single WSS 3.0 site that users can get to using the Default alternate access mapping (http://sp1) or an Intranet access mapping (http://lp). After installing that same DST patch (KB941422), search only works on the Default URL, http://sp1. No results are returned for the Intranet URL, http://lp. This worked fine before the patch. I have deleted and let WSS rebuild the search index to no avail. Any ideas?

I tried to add a 2nd content database to our virtual environment and had the similar issues regarding version difference. I even tried to remove the 1st content DB from the web application and upgrade both SharePoint and CA web application and all failed. Until I remove the Great Group Board feature (From MS) from the server, everything went like charm and I had no issues anymore. Since remove this feature also mentioned in this thread, so I post my experience to share with you. Thanks.

JJAnton wrote: Chris Whitehead - MSFT wrote: OK, is the hotfix showing in add/remove programs and have you tried running the hotfix again? Same result or message saying it is already installed? OK I've got the same situation as the original post. I know a few hotfixes had been updated on my 2003 Server and I have uninstalled them. I still have the same Newer Version senario. I have tried to do the inplace upgrades but the exact same things are happening as the original post. Any Ideas? I don't have the luxury of a backup at this point and would like to recover the data ( this is a testbed server but I got caught up in one of the templates and added essential data) Thanks! OK I have found a solution to this issue, I have reinstalled the .net by going through aspnet_regiis.exe on both versions 2.0 and 1.1 This seemed to fix my issues Hope this helps others! Thanks J.J.

Hi I have same Error.I have server A (old server) having WSS 3.0 and SharePoint 2.0 installed side by side . I have two sites in SharePoint 2.0 and two sites in WSS 3.0 total four sites. I have SQL server 2000 for content database.now I want to restore all this four sites to new server "B" it has WSS 3.0 and Default SQL 2k5 Embadded Edition i.e Microsoft##SSEE.First What I did is Take a backup of WSS 3.0 site from Server "A" (older server) and try to restore it on Server "B" with STSADM Retore command. Here It creates Web Application but when it tries to attach content database it throws SQLException Signature is Invalid... so I can't restore site properly.Even when I tries to open dbo.alldocs table from content databse from SQL Manager studio it wont allow me to open table and see its contnet "It throws an SQL Exception that :Access to table dbo.AllDocs is blocked because signature is invaild".Thanks $ Regards,Jayesh Prajapatiwww.SharePointKings.com

I've read that one fix is to remove Groupboard Workspace from Add/Remove Programs, then rerun WSS Products and Technologies Config wizard. I'm in the process of doing that right now so can't say for sure if it works. CW

Uninstalling Groupboard fixed my installation.After applying SP1 and KB953397 simultaneously through Windows Update. My SP sites wouldn't open. In event viewer I had error "schema version (3.0.151.0) of the database XXXXX is not consistent with the expected database schema version (3.1.3.0)". The configuration wizard crashed on step 2, with another error. Running stsadmin -o -update -inplace http://configurationsite aborted with the same error.Then uninstalled Groupboard, which uninstalled successfully despite reporting some errors during uninstall. Then the Configuration Wizard ran successfully.

You install post SP1 hotfixes and you get an error along the lines of The specified SPContentDatabase Name=SharePoint_AdminContent_c3f4a552-4b8c-4753-b8b4-01a39042139f Parent=SPDatabaseServiceInstance Name=OfficeServers has been upgraded to a newer version of SharePoint in the application log. If you look at the upgrade.log file it has the following line in it. Upgrade object too new (build version = 12.0.0.6219, schema version = 2.0.0.0). Current server (build version = 12.0.0.4518, schema version = 3.0.1.0). The resolution is to uninstall the GroupBoard add on that was made available by microsoft.

Careful withGroupboardguys... I bet it won't go cleanly. After you have removed it, try adding an existingsite column to a document library and see if you get an error.If you do, take a peek at this thread:http://forums.technet.microsoft.com/en-US/sharepointadmin/thread/ba825946-b705-41a0-aceb-af6e35a884e8.Hope this helps anyone who experienced the same problems I did.A+, MCP, MCTS WSS 3.0 & MOSS 2007 Configuring

Hi Daniel,I recd a same issue regarding the post servicepack1 for MOSS and WSS 3.0. I got it working for the client.I will post the resolution by this week end. Hope every1 can hold on their patience till Sat atleast.....:)Thanks,Ron

To All, I wonder what was happening as I did the update of: SQL Server 2008 Standard SP1 --> OK WSS 3.0 SP2 --> OK MOSS 2007 SP2 --> FAILED! I'm facing the following problem Event ID: 5617 Error The schema version (3.1.3.0) of the database MySite_ContentDB on MOSSDEV01\MOSSDB is not consistent with the expected database schema version (3.1.8.0) on MOSSDEV01. 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./* Windows Infrastructure Support Engineer */

Hi All, I have been using SharePoint since November 2009 - We use it as a job tracking system, CRM, Stock ordering and an accounts package - Basically we use it for everything. I have been backing up the server infrequently as we have been very busy. On Monday 14th June 2010 - my SBS 2008 standard Ed RC 0 box installed updates - this also coincided with me installing an additional SQL instance to use as a Business Contact Manager 2007 database. Ever since both of these events I have been unable to connect to sharepoint . The error message I was getting originally was "cannot connect to configuration database" when browsing to http://companyweb - Central administration was giving the same error. I was getting event log errors such as the following when anyone tried to access the sharepoint site: ___________________________________________________________________ Log Name: Application Source: SideBySide Date: 15/06/2010 11:22:28 Event ID: 33 Task Category: None Level: Error Keywords: Classic User: N/A Computer: CITSERV.creativeit.local Description: Activation context generation failed for "C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe". Dependent Assembly Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4027" could not be found. Please use sxstrace.exe for detailed diagnosis. ______________________________________________________________________ Log Name: Application Source: MSSQL$MICROSOFT##SSEE Date: 15/06/2010 11:23:39 Event ID: 18456 Task Category: (4) Level: Information Keywords: Classic,Audit Failure User: NETWORK SERVICE Computer: CITSERV.creativeit.local Description: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>] ________________________________________________________________________ Log Name: Application Source: Windows SharePoint Services 3 Date: 15/06/2010 18:59:11 Event ID: 3760 Task Category: Database Level: Error Keywords: Classic User: N/A Computer: CITSERV.creativeit.local Description: SQL Database 'SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. ---------------------------------------------------------------------------------------------------------- I found this thread http://social.technet.microsoft.com/forums/en-US/sharepointadmin/thread/07008528-abfb-4f63-a661-d8c55f3552de/?ppud=4 and decided to use the above method to restore my content database - I have done everything up until 15) Moment of truth...issue the following command: stsadm -o addcontentdb -url http://siteurl -databasename [your content database name] At which point I am getting the following error: The specified SPContentDatabase Name=WSS_Content Parent=SPDatabaseServiceInstanc e Name=Microsoft##SSEE has been upgraded to a newer version of SharePoint. Pleas e upgrade this SharePoint application server before attempting to access this ob ject. I then tried stsadm -o upgrade -inplace -url http://<URL> -forceupgrade stsadm -o upgrade -inplace -url http://<URL> -forceupgrade psconfig –cmd upgrade –inplace b2b –wait –force Which all completed successfully so i tried to add the content database again - the same error appeared. I cannot afford to loose this sharepoint site as it has all of my outstanding invoices/jobs to be done etc.... It has already set me back a week trying to fix it. Any help would be greatly appreciated. I have all of the original databases from the original ##ssee installation. Cheers, Evan

Companyweb and SharePoint Central Admin not accessible after installing KB983444 - The Official SBS Blog - Site Home - TechNet Blogs: http://blogs.technet.com/b/sbs/archive/2010/06/18/companyweb-and-sharepoint-central-admin-not-accessible-after-installing-kb983444.aspx

Make sure that after any hotfix or update installation we need to run Sharepoint products and technologies configuration wizard.Regards, Nagendra

Just goes to show I should read the entire thread before giving up... I had the issue in this thread about six months ago... SP updates had been neglected for a while. Tried many different things to get this to work, but ultimately gave up, VMware allowed me to revert to a snapshot and I just left things unpatched like it was while I worked on other projects. Cut to today, and I started working on this again, decided to read this entire thread this time through, and found your (kef65) post... Uninstalled groupboard and the upgrade went through _without_ an issue. GroupBoard for the LOSS. Thanks for the post! Proposing as answer since this is a definite alternate solution! [edit]Accidentally proposed this one as the answer instead... moderator, feel free to remove it from my own post. Unintended.[/edit] blog TinyInt.Com | work Logicworks.Net

Just goes to show I should read the entire thread before giving up... I had the issue in this thread about six months ago... SP updates had been neglected for a while. Tried many different things to get this to work, but ultimately gave up, VMware allowed me to revert to a snapshot and I just left things unpatched like it was while I worked on other projects. Cut to today, and I started working on this again, decided to read this entire thread this time through, and found your (kef65) post... Uninstalled groupboard and the upgrade went through _without_ an issue. GroupBoard for the LOSS. Thanks for the post! Proposing as answer since this is a definite alternate solution! [edit]Accidentally proposed this one as the answer instead... moderator, feel free to remove it from my own post. Unintended.[/edit] blog TinyInt.Com | work Logicworks.Net