locked
"SPConfigurationDatabase is too old to be upgraded by this version of SharePoint" - SPS2003 (SP3) RRS feed

  • Question

  • I am performing an in-place upgrade from SPS2003(SP3) to MOSS2007
    During the SCW process, it fails on step 2, Initialising Upgrade Sequence, with the error:
    "The specified SPConfigurationDatabase is too old to be upgraded by this version of SharePoint. Please perform the needed intermediate upgrades before attempting this one"

    My question is:
    Since the SPS version I have is 11.0.8168.0, and WSS is 11.0.8173.0, what other upgrades are necessary for MOS2007 SCW to be happy and continue to step 3?

    Thanks

    • Edited by Stunz Saturday, December 18, 2010 2:39 AM modified heading to better reflect content
    • Edited by Mike Walsh FIN Saturday, December 18, 2010 8:56 AM Quotes put around error text
    Saturday, December 18, 2010 2:25 AM

Answers

  • I got in touch with Microsoft in the end but we couldn't resolve the outdated config database issue.

    I ended up using the addcontentdb method and creating a new config database. This upgraded the 2003 portal system to 2007 Sharepoint successfully.

    A few days of reconfiguring some settings, cleaning up some errors and I am all good again!

    • Marked as answer by Stunz Wednesday, January 12, 2011 4:24 AM
    • Edited by Mike Walsh FIN Wednesday, January 12, 2011 7:26 AM reference to SP 2010 removed
    Wednesday, January 12, 2011 4:23 AM

All replies

  • Hi Stunz,

    Perhaps the reason is the database is not upgraded. Please check the version number in the DBO.Systemversions.

    If so, please run stsadm.exe –o upgrade -forceupgrade -url <url>on the SPS 2003 machine and do a upgrade again. And check the version number.

    Here are some references about perform a gradual upgrade, hope it could help.

    http://technet.microsoft.com/en-us/library/cc303405(office.12).aspx

    http://technet.microsoft.com/en-us/office/sharepointserver/bb421259.aspx


    Best regards. Emir
    • Edited by Emir Liu Wednesday, December 22, 2010 1:14 PM
    • Marked as answer by Lily Wu Monday, December 27, 2010 8:20 AM
    • Unmarked as answer by Stunz Wednesday, January 12, 2011 4:23 AM
    Monday, December 20, 2010 5:50 AM
  • Thank you Emir.

    I did in fact find out that my version is out by a few clicks after looking in the dbo.global table.

    I'll do as you suggest and run a -forceupgrade. Does this procedure automatically download and install the required patches to get it up to the latest level?

    Regards

    Stu

    Tuesday, December 21, 2010 6:54 PM
  • Hi Stu,

    Thanks for your reply.

    forceupgrade is used to force an ungrade of the content database and configuration database to the next level.


    Best regards. Emir
    Wednesday, December 22, 2010 1:20 PM
  • Thanks for your response Emir.

    I have tried the -forceupgrade, but it fails with error:
    "Object reference is not set to an instance of an object"
    The exact syntax was: stsadm-o upgrade -forceugrade -inplace -url http://portalsite

    What I am confused about however, is:

    • My Virtual Server is version 6.0.2.8165 (SPS2003 + SP3)
    • The sites in the site collection however, are displaying version 6.0.2.5530 which is (as I understand it), the first release version of WSS. The configuration database is also showing this value, but...
    • I am running WSS2.0 SP3 on the server which by my calculations should make WSS at least version 6.0.2.6568 (and ready for an upgrade to WSS3.0 and MOSS2007)

    Additionally, the Portal_SITES db is 6.0.2.8165, so how can a site in the site collection be at 6.0.2.5530?

    So I am at a loss. How can I make sure the config database is up to date?

    Thanks for looking

    Wednesday, December 29, 2010 12:49 AM
  • I got in touch with Microsoft in the end but we couldn't resolve the outdated config database issue.

    I ended up using the addcontentdb method and creating a new config database. This upgraded the 2003 portal system to 2007 Sharepoint successfully.

    A few days of reconfiguring some settings, cleaning up some errors and I am all good again!

    • Marked as answer by Stunz Wednesday, January 12, 2011 4:24 AM
    • Edited by Mike Walsh FIN Wednesday, January 12, 2011 7:26 AM reference to SP 2010 removed
    Wednesday, January 12, 2011 4:23 AM