Sign in
 
HomeSharePoint Server 2010SharePoint Foundation 2010SharePoint OnlineLibraryForums
SharePoint Products > SharePoint Products and Technologies Forums > SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010) > MOSS is down after installing SharePoint Services 3.0 Service Pack 1

Unanswered MOSS is down after installing SharePoint Services 3.0 Service Pack 1

    •  
      Wednesday, January 23, 2008 11:30 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote


      Event Type: Error
      Event Source: Windows SharePoint Services 3
      Event Category: Topology
      Event ID: 5617
      Date:  24/01/2008
      Time:  12:00:41 AM
      User:  N/A
      Computer: DTSPSTS-HO01
      Description:
      The schema version (3.0.151.0) of the database WSS_MySite_Content on dtsqlts-ho02 is not consistent with the expected database schema version (3.1.3.0) on DTSPSTS-HO01.  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.

       

    All Replies

    • Thursday, January 24, 2008 7:46 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      HI,

      Try to use the upgrade operation of the stsadm.exe tool: STSADM.EXE -o upgrade

       

      I hope this helps,

      Mart

       

       
    • Monday, January 28, 2008 4:00 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi all,

       

      I met the same error !

       

      In fact, I launched the SHAREPOINT and CONFIGURATION WIZARD.

      After that, the Web site works fine.

       

      Best regards,

      I hope it will work for you too !!

       

      Stéphane

       

       
    • Monday, January 28, 2008 4:42 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Doesnt the configuration wizard launch automatically after the SP1 update?  did you run it an additional time after this? 

       

      I'm only wondering because we are seeing some strange issues after SP1 and I am wondering if we should just run the config wizard a 2nd time. 

       

       

       
    • Monday, January 28, 2008 10:43 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Thanks Stéphane, I tried SharePoint Products and Technologies Configuration Vizard & It worked!
       
    • Thursday, January 31, 2008 1:49 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      open the content database for your site, find the versions table and change the value back to 3.1.3.0. I had a similar issue and it resolved my problem.
       
    • Friday, November 21, 2008 9:21 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi Mart,

      I tried upgrading operation using stsadm.exe tool. But still unable to fix the issue.

      This is message I am getting after running stsadm.exe

      Upgrade completed with error. Review the upgrade.log file located in C:\Program File\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log

      I also looked into LOG file and figured out there were repeated lines which are highlighted in black. But I am sure what does it mean and where to start from to fix it. 

      Any help would be really appreciated. It's very very very urgent...Please help me..

       --- End of inner exception stack trace ---
         at System.ServiceProcess.ServiceController.Start(String[] args)
         at System.ServiceProcess.ServiceController.Start()
         at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
         at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
         at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]: Upgrade [SPSearchDatabase Name=WSS_Search_PSSSites_8301b11e117840b093cdf73fea8842cb Parent=SPDatabaseServiceInstance] failed.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:       The service did not start due to a logon failure
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:       Cannot start service SPSearch on computer '.'.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:    at System.ServiceProcess.ServiceController.Start(String[] args)
         at System.ServiceProcess.ServiceController.Start()
         at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
         at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
         at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
         at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
         at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
      [SPManager] [DEBUG] [11/21/2008 12:56:53 AM]: Elapsed time upgrading [SPSearchDatabase Name=WSS_Search_PSSSites_8301b11e117840b093cdf73fea8842cb Parent=SPDatabaseServiceInstance]: 00:00:04.
      [SPManager] [INFO] [11/21/2008 12:56:53 AM]: Resetting the status of PersistedUpgradableObject: SPSearchDatabase Name=WSS_Search_PSSSites_8301b11e117840b093cdf73fea8842cb Parent=SPDatabaseServiceInstance to Online.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]: ReflexiveUpgrade [SPSearchDatabase Name=WSS_Search_PSSSites_8301b11e117840b093cdf73fea8842cb Parent=SPDatabaseServiceInstance] failed.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:       The service did not start due to a logon failure
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:       Cannot start service SPSearch on computer '.'.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:    at System.ServiceProcess.ServiceController.Start(String[] args)
         at System.ServiceProcess.ServiceController.Start()
         at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
         at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
         at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
         at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
         at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
         at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
         at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
      [SPManager] [INFO] [11/21/2008 12:56:53 AM]: Resetting the status of PersistedUpgradableObject: SPServer Name=PSSSites Parent=SPFarm Name=SharePoint_PSSSites to Online.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]: ReflexiveUpgrade [SPServer Name=PSSSites Parent=SPFarm Name=SharePoint_PSSSites] failed.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:       The service did not start due to a logon failure
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:       Cannot start service SPSearch on computer '.'.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:    at System.ServiceProcess.ServiceController.Start(String[] args)
         at System.ServiceProcess.ServiceController.Start()
         at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
         at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
         at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
         at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
         at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
         at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
         at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
         at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
         at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
         at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
         at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
      [SPManager] [INFO] [11/21/2008 12:56:53 AM]: Resetting the status of PersistedUpgradableObject: SPFarm Name=SharePoint_PSSSites to Online.
      [SPManager] [INFO] [11/21/2008 12:56:53 AM]: Inplace Upgrade session finishes. root object = SPFarm Name=SharePoint_PSSSites, recursive = True. 3 errors and 0 warnings encountered.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]: Upgrade failed.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]: 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.
      [SPManager] [ERROR] [11/21/2008 12:56:53 AM]:    at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSession(IUpgradable root, Boolean bRecursive)
         at Microsoft.SharePoint.StsAdmin.SPUpgrade.RunUpgrade(StringDictionary keyValues)


       
    • Friday, November 21, 2008 9:34 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      I am struggling a lot to fix this issue. Could you please let me know the navigation steps to find version table in content database to make the suggested changes.


      I would really appreciate if you could help me . It very very urgent

      Please help me



      Thanks in advance

      Jaya


      Note: Sorry for the duplicate post , I trying my best to get a sloution to fix the issue.

      • Edited by Jaya78 Friday, November 21, 2008 9:38 AM Note
      •  
       
    • Tuesday, November 25, 2008 8:21 PM
       
       
      Sign In to Vote
      1
      Sign In to Vote
      Hi All,

      I resolved the issue by myself, here are the steps I have done.

      1. From central administration \ operations \ services on server

      2. Selected the windows SharePoint help search service (SPSEARCH)

      3. And then added the password for the user account again.

      4. Aand saved that.

      5. Then ran the following command:

       

      STSADM –o spsearch –farmseviceaccount domain\username –farmservicepassword password

       

      6. Then ran the Psconfig wizard again.

      7. And it got completed successfully.


      Thanks for all for providing help steps for this issue..


      Regards

      Jaya

       
    • Monday, July 13, 2009 7:01 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Thanks Jaya.. it solved the problem instantly.
       
    • Friday, June 11, 2010 9:21 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Tank you Jaya! You saved my day!
       
    • Friday, January 28, 2011 3:37 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Awesome!  Fixed my error immediately upgrading from SP1 to SP2 of WSS.

      Now to do the next one...