locked
SharePoint 2007 upgrade to SP2 failing RRS feed

  • Question

  • We have been having all kinds of trouble trying to upgrade our MOSS 2007 staff portals to SP2.  We finally got the dev server to upgrade by shutting down LOTS of services (all the SharePoint services, WWW, IIS, etc).  But our production server still will not upgrade.  The post install SharePoint configuration wizard fails on task 8.  We install WSS SP2 first, then MOSS SP2, then run the wizard.  Error message in the Update log indicates the index database is of a pre-release version!  We tried copying over the updated index from the dev server, but then the configuration wizard reports the database is "too new"!!!  (On a side note, why doesn't the configuration wizard just continue on if the database is already updated?  This seems silly!)  I have checked the version of the index database using this query:

    SELECT [VersionId]
          ,[Version]
          ,[Id]
          ,[UserName]
          ,[TimeStamp]
          ,[FinalizeTimeStamp]
          ,[Mode]
          ,[ModeStack]
          ,[Updates]
          ,[Notes]
      FROM [<index database>].[dbo].[Versions]
      WHERE VersionId = '00000000-0000-0000-0000-000000000000'
      ORDER BY Id DESC

    and it returns the proper SP1 version (12.0.0.6219).

    Anyone have any ideas?

    • Edited by Mike Walsh FIN Tuesday, January 25, 2011 1:13 PM speculations on the cause of a problem go in the text not in the Title - ...database version problem? removed from Title. 2010 reference irrelevant here and removed
    Tuesday, January 25, 2011 1:03 PM

Answers

  • Hi If you are able to browse to Central admin then go to Application Management > Content Database > Select SSP web application and detach the content DB

    or

    If central admin is not accessible then take a backup of search content DB and run following command to delete SSP

    stsadm -o deletessp -title <SSP name> -force


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Tuesday, January 25, 2011 4:23 PM
  • Hi,

    Sorry for delay.

    Yes deleting SSP will remove link to SSP crawl DB.

    If this will be done. go ahead and try to upgrade.

    Best of Luck.


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Friday, January 28, 2011 8:39 PM

All replies

  • Hi,

    what is the exact error message you received when PSConfig failed @ step 8 ?


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Tuesday, January 25, 2011 1:51 PM
  • Hello Pratik,

    Unfortunately I don't have the exact message, but it had to do with SharePoint Products and Technologies failing to upgrade.  I have the upgrade.log from when we copied in the upgraded version of the database from dev.  The relevant portion of the log looks like this:

    [SPManager] [INFO] [1/21/2011 11:36:35 PM]: Preparing to upgrade PersistedUpgradableObject: SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT.  This object's current status is Online.
    [SPSearchDatabaseSequence] [DEBUG] [1/21/2011 11:36:35 PM]: SPSearchDatabaseSequence::CanUpgrade IsWYukon False WyukonMode False
    [SPSearchDatabaseSequence] [DEBUG] [1/21/2011 11:36:35 PM]: Generating sqlsession for sequence [Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence] and database [SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT].
    [SPSearchDatabaseSequence] [DEBUG] [1/21/2011 11:36:35 PM]: Calling get SchemaVersion on Database WSS_Search_CWSP1-crawlerFixed, Status = Upgrading.
    [SPSearchDatabaseSequence] [DEBUG] [1/21/2011 11:36:35 PM]: Calling get SchemaVersion on Database WSS_Search_CWSP1-crawlerFixed, Status = Upgrading.
    [SPSearchDatabaseSequence] [ERROR] [1/21/2011 11:36:35 PM]: Upgrade object too new (build version = 12.0.6425.1000, schema version = 2.0.0.0). Current server (build version = 12.0.0.6550, schema version = 12.2.8.0).
    [SPManager] [ERROR] [1/21/2011 11:36:35 PM]: CanUpgrade [SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT] failed.
    [SPManager] [ERROR] [1/21/2011 11:36:35 PM]: The specified SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
    [SPManager] [ERROR] [1/21/2011 11:36:35 PM]:    at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
       at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.get_CanUpgrade()
       at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
    [SPManager] [ERROR] [1/21/2011 11:36:35 PM]: ReflexiveCanUpgrade [SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT] failed.
    [SPManager] [ERROR] [1/21/2011 11:36:35 PM]: The specified SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
    [SPManager] [ERROR] [1/21/2011 11:36:35 PM]:    at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
       at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.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.Upgrade(Object o, Boolean bRecurse)
    [SPManager] [DEBUG] [1/21/2011 11:36:35 PM]: Cannot upgrade [SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT].
    [SPManager] [DEBUG] [1/21/2011 11:36:35 PM]: Skip upgrading [SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT].
    [SPManager] [INFO] [1/21/2011 11:36:35 PM]: Resetting the status of PersistedUpgradableObject: SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT to Online.
    [SPManager] [INFO] [1/21/2011 11:36:35 PM]: Finished upgrading SPSearchDatabase Name=WSS_Search_CWSP1-crawlerFixed Parent=SPDatabaseServiceInstance Name=SQL_SHPNT.

     The message when using the original database that is currently in use was that it was a pre-release version!  Not true, but that is what it was reporting.

    • Edited by jkelch Tuesday, January 25, 2011 3:04 PM
    Tuesday, January 25, 2011 2:23 PM
  • Hi,

    try running following command

    psconfig.exe -cmd upgrade -inplace b2b -force -wait


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Tuesday, January 25, 2011 3:02 PM
  • Yes, we did try that.  Same errors.
    Tuesday, January 25, 2011 3:09 PM
  • In Upgrade log, I found something interesting

    [SPSearchDatabaseSequence] [ERROR] [1/21/2011 11:36:35 PM]: Upgrade object too new (build version = 12.0.6425.1000, schema version = 2.0.0.0). Current server (build version = 12.0.0.6550, schema version = 12.2.8.0).

    Which says current version is 12.0.0.6550 which only possible after Dec 2010 CU install.

    So did you try to install Dec 2010 CU, because its prerequisite is MOSS SP2 and as you have mentioned it is failing in SP2 installation


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Tuesday, January 25, 2011 3:23 PM
  • Sorry for the confusion...the upgrade log text is from the attempt to use a copy of the search index database from our dev server, which has already been upgraded to SP2 and had the Dec 2010 CU installed as well.  Unfortunately (it was late at night, our brains were not functioning at peak efficiency!) we did not save a copy of the upgrade log from using the original seach database during the upgrade.  As I indicated above, we got an error at the same place, but in this instance it was reporting that the search index database was a 'pre-release' version and could not be updated.  We don't understand why the search database would be of a pre-release version while all the other databases were of the proper release (MOSS SP1, 12.0.0.6219)
    Tuesday, January 25, 2011 3:28 PM
  • No problem, in this scenario you can detach search DB from farm first then upgrade server to SP2, create a new SSP in upgraded serer and then attach the old Search DB.

    Basically its not require to carry old search DB to upgraded server but as it contains user mysite data, if its requires you can move it to upgraded once after upgrading server successfully to SP2.

     


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Tuesday, January 25, 2011 3:35 PM
  • I think we tried something like this, but I will check.  I actually reset the search index before doing the SP2 update anyway, that helped in our dev upgrade, so I don't think it has any significant content anyway.
    Tuesday, January 25, 2011 3:39 PM
  • I was just talking to the systems engineering guy I work on this with, and he is not clear (neither am I) on how to detach the database.  It is not a content database, just a search crawler database.  Do we have to detach the entire SSP?  How is that done?
    Tuesday, January 25, 2011 4:06 PM
  • Hi If you are able to browse to Central admin then go to Application Management > Content Database > Select SSP web application and detach the content DB

    or

    If central admin is not accessible then take a backup of search content DB and run following command to delete SSP

    stsadm -o deletessp -title <SSP name> -force


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Tuesday, January 25, 2011 4:23 PM
  • Pratik,

    If we drop the content database for the SSP does that also disassociate the other db's used by the SSP, such as the search crawler db (where we are having our problem)?  All the documentation I have found is rather confusing on this issue.  Our problems occur on processing the search crawler database, not the content database of the SSP, so if we remove the SSP does that automatically remove the link to the search crawler database?

    Wednesday, January 26, 2011 5:24 PM
  • Pratik,

    We are hoping to make another attempt at SP2 very soon, if you have any comment on my question above? Thanks.

    Friday, January 28, 2011 8:28 PM
  • Hi,

    Sorry for delay.

    Yes deleting SSP will remove link to SSP crawl DB.

    If this will be done. go ahead and try to upgrade.

    Best of Luck.


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Friday, January 28, 2011 8:39 PM
  • Patrik... Thanks for all your help on this, the question has been answered. 

    Jkelch if you have further problems please open a ticket with MS Support are being a new thread after all of the above has been tired.  I'm locking this thread at this time.


    Kris Wagner, MVP, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog
    Monday, January 31, 2011 6:52 AM
    Moderator