{"id":578,"date":"2009-10-10T15:44:00","date_gmt":"2009-10-10T15:44:00","guid":{"rendered":"https:\/\/brainlitter.itgroove.net\/2009\/10\/10\/resolution-to-strange-sharepoint-sql-database-restore-problem\/"},"modified":"2009-10-10T15:44:00","modified_gmt":"2009-10-10T15:44:00","slug":"resolution-to-strange-sharepoint-sql-database-restore-problem","status":"publish","type":"post","link":"https:\/\/regroove.ca\/brainlitter\/2009\/10\/10\/resolution-to-strange-sharepoint-sql-database-restore-problem\/","title":{"rendered":"Resolution to strange SharePoint SQL Database Restore Problem"},"content":{"rendered":"
\n

The Requirement <\/h2>\n

A customer had quite the mess of a SharePoint farm. Efforts are being made to clean it up \u2026 but in the meantime, they required a backup of a SharePoint Content Database (from 5 days ago) to be restored into a new (temporary) Web Application to retrieve some old data. Typically, this would be a simple request. <\/p>\n

\u00a0<\/p>\n

The Issues <\/h2>\n

The problem was, when it came time to restore, we experienced the following problems (differing, depending on minor changes to the approach): <\/p>\n

    \n
  1. Content Database would not attach at all (using this syntax: stsadm.exe -o addcontentdb -url http:\/\/servername:port<\/span> -databasename content_database_name<\/span> -databaseserver SQL_Server_Name<\/span><\/strong>). This would return the following Error\u2026 The specified SPContentDatabase Name=content_database_name Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.\n

    <\/span>Or\u2026<\/strong><\/span>
    <\/span><\/em><\/li>\n

  2. The Content Database would attach (using above syntax) but Central Administration would indicate that the Content Database contained “0” (zero) sites and if you attempted to go to the Web Application, you would get a 404 <\/li>\n<\/ol>\n

    \u00a0<\/p>\n

    What We Tried First (Validation) <\/h2>\n
      \n
    1. \n
      First, as it seemed pretty clear there were version issues, I verified that the Farm was at the expected build number (MOSS\/WSS SP1 by the way) \u2013 and it was (6219). <\/div>\n
        \n
      1. How: In Central Admin, Operations, Servers in Farm <\/li>\n<\/ol>\n<\/li>\n
      2. \n
        Second, I verified each WFE’s version <\/div>\n
          \n
        1. Find\/compare Owssvr.dll<\/strong> (in 12 hive isapi directory) <\/span><\/li>\n
        2. In the Registry – “HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions12.0”, verify versions are the same <\/span><\/li>\n<\/ol>\n<\/li>\n
        3. \n
          Third, I verified that the restored Content Database was at the same version (well, or so it reported\u2026) <\/div>\n
            \n
          1. \n
            How: In SQL, perform the following Query against the database <\/div>\n

            SELECT [VersionId]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[Version]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[Id]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[UserName]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[TimeStamp]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[FinalizeTimeStamp]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[Mode]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[ModeStack]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[Updates]
            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0,[Notes]
            \u00a0\u00a0FROM [WSS_Content].[dbo].[Versions] <\/span><\/p>\n

            Or\u2026 <\/strong><\/span><\/p>\n

            select * from versions order by timestamp desc <\/span><\/p>\n<\/li>\n<\/ol>\n<\/li>\n

          2. Groupboard Workspace was once installed in the environment as well (and the Farm had recently been rebuilt in haste), so we attempted to put that back temporarily to see if that had any effect <\/li>\n<\/ol>\n

            \u00a0<\/p>\n

            The Solution <\/h2>\n

            So, it was pretty clear WSS\/MOSS SP1 was applied everywhere (but the *history* behind the Farm and some knee jerk reactions does leave some question as to the overall stability and consistency of the environment). Thus, we took the following steps (remember, the requirement was to get some data from an old site backup \u2013 next steps of course will be to bring the farm to SP2 to be more recent\/compliant and supportable for the long haul). <\/p>\n

            \u00a0<\/p>\n

              \n
            1. Built a ‘beater farm’ (a playpen, separate from Dev and Production, that we were comfortable with manipulating\/patching as necessary) with SP1 installed and GroupBoard Workspace (though unclear still whether that mattered in the end \u2026 but I don’t care on a Saturday when I should be getting ready to watch the Leafs vs. Penguins game) <\/li>\n
            2. Restored the SQL Database from backup one more time <\/li>\n
            3. Created a new web application <\/li>\n
            4. Removed the DB created by the new web application <\/li>\n
            5. \n
              Attached the SQL Database to the new web application (again, see syntax above) <\/div>\n
                \n
              1. Still “0” sites if restored into a web application with no Site Collection pre-created previously in new Web Application <\/li>\n
              2. Still get “The specified SPContentDatabase Name=FLAGCONTENTDB1 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.” If we restored into it, without pre-creating a site collection in the placeholder web application <\/li>\n<\/ol>\n<\/li>\n
              3. Applied SP2 to the Beater Farm \u2026 and we have success<\/span>\u2026 We can mount the site collections and retrieve the necessary, archived data \u2013 the customer’s requirement is met <\/li>\n<\/ol>\n

                \u00a0<\/p>\n

                \u00a0<\/p>\n

                Yep, after all that, despite the Database indicating it was created with SP1, it would not restore into an SP1 environment. An upgrade to SP2 however was sufficient to bring the content back online so the data could be retrieved. <\/p>\n

                \u00a0<\/p>\n

                \u00a0<\/p>\n

                Hope this helps someone, somewhere. <\/em><\/p>\n

                \u00a0<\/p>\n

                \u00a0<\/p>\n

                References <\/h2>\n