locked
Problem completing MOSS 2007 SP2 upgrade RRS feed

  • Question

  • I've been running into a major issue trying to finalize our MOSS 2007 upgrade to SP2.  The installation itself went fine, but the Configuration Wizard gets stuck on Step 8 of 9.  Here is the excerpt of the error from the Upgrade.log

    [SPManager] [ERROR] [11/16/2010 12:24:44 PM]: CanUpgrade [SPContentDatabase Name=WSS_Content_technology Parent=SPDatabaseServiceInstance] failed.
    [SPManager] [ERROR] [11/16/2010 12:24:44 PM]: Cannot open database "WSS_Content_technology" requested by the login. The login failed.
    Login failed for user 'RKAD01US\username'.

    Now the issue here is not access related.  The Content DB "WSS_Content_technology" is an Offline Content DB which is no longer used (it was restored to a new Content DB with a different name).  Since it is offline, it makes sense that it cannot be accessed but I'm not sure WHY the Configuration Wizard is trying to access it.  I checked IIS on the WFE and neither the old site nor old application pool are listed there so it was definitely removed IIS-wise.

    To complicate matters a bit, we do not have a working Central Admin right now.  Actually, we are applying SP2 as one step in the process of restoring Central Admin ultimately but we are now stuck since the upgrade will not complete.

    I think the root cause of the issue is related to how this old site was removed from the original WFE.  Since there was no Central Admin, I believe the previous engineer did the following:

    • Backed up "WSS_Content_technology"
    • Took "WSS_Content_technology" offline via SSMS
    • Went to IIS on WFE and manually deleted Web Site and Application Pool

    Since this wasn't done through Central Admin or via a command line operation, I believe that there must still be some reference to the old site/old content db somewhere and that is why the Config Wizard is trying to upgrade it and failing.

    Phew - any ideas?

    Tuesday, November 16, 2010 7:00 PM

Answers

  • I was finally able to get the upgrade to complete.  I took an unrelated SharePoint Content DB from another farm and restored it to the DB server under the name "WSS_Content_technology" and retried the configuration wizard and it completed successfully.  Once I can get Central Admin back up, I will be able to remove it properly.  Thanks to all who contributed!
    • Marked as answer by Peng Lei Thursday, November 25, 2010 6:14 AM
    Tuesday, November 23, 2010 2:02 PM

All replies

  • can you try

    psconfig -cmd upgrade -inplace b2b -wait -force



    HTH
    Nagesh S

    Days and years do not mean anything to me. Moments shared are frozen
    in their time frame. Distance or time never fades them for me. I cherish them
    like my life. I have never let them sleep alone. Sachi
    Tuesday, November 16, 2010 9:17 PM
  • Give to 'RKAD01US\username' Database owner on WSS_Content_technology database and run wizard again.


    Oleg
    Tuesday, November 16, 2010 9:39 PM
  • Nagesh - Tried that but same error

    Oleg - As I mentioned, this Content DB is Offline and not used any longer.  The data files that were originally associated with it are now associated with a separate Content DB.  "WSS_Content_technology" is not currently associated with any data files.

    Wednesday, November 17, 2010 2:04 AM
  • Just put that old/unused wss_content_technology db back online for the upgrade and when done, disassociate it from sharepoint via central admin "Application Mgmt/Content Databases".

    /bac
    Wednesday, November 17, 2010 1:16 PM
  • That solution will not work since the data files it was originally associated with are now associated with an active Content DB on the same SQL Server.  I would get an error that the data files are already being used by an existing DB.
    Wednesday, November 17, 2010 1:18 PM
  • This may be a bit of a hack, but can you make copies the data files from that content db and recreate the old?  Otherwise if I were in your situation I might roll back pre upgrade and remove the database from central admin prior to this process.
    /bac
    Wednesday, November 17, 2010 3:17 PM
  • I was finally able to get the upgrade to complete.  I took an unrelated SharePoint Content DB from another farm and restored it to the DB server under the name "WSS_Content_technology" and retried the configuration wizard and it completed successfully.  Once I can get Central Admin back up, I will be able to remove it properly.  Thanks to all who contributed!
    • Marked as answer by Peng Lei Thursday, November 25, 2010 6:14 AM
    Tuesday, November 23, 2010 2:02 PM