locked
Problems Restoring a SharePoint WSS 3.0 site RRS feed

  • Question

  •  

    Hello,

     

    I am having problems restoring a backup to a sub site to recovery a document. I have a WSS 3.0 site on Windows 2003 Standard Edition SP2 server. Basically, I started off with following these steps from this article:

     

    http://technet.microsoft.com/en-us/library/cc747463(WS.10).aspx

     

    Step 1 went well, which is:

     

    Click Start, click Command Prompt, and then type "%SystemDrive%\Program files\Common files\Microsoft shared\Web server extensions\60\Bin\Stsadm.exe" -o createsiteinnewdb -url http://companyweb/sites/RestoredSite -ownerlogin DOMAIN\administrator -owneremail administrator@DOMAIN.local -databasename STS_RESTORE, where DOMAIN is your server domain and administrator@DOMAIN.local is your administrator’s e-mail address. Include the quotation marks as part of the path.

     

    The sub-site was created successfully.

     

    Step 2 is this:

     

    Type "%SystemDrive%\Program files\Common files\Microsoft shared\Web server extensions\60\Bin\Stsadm.exe" -o restore -url http://Companyweb/Sites/Restoredsite -filename target path -overwrite, where target path is the location where you chose to save your SharePoint backup.

     

    However, I received this error:

     

    Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '1162887508.196608.17694860.0' or later.

     

    The thing is that I create my backup files (BAK) for the content database with the sqlcmd (the SQL Sever T-SQL command line program), like this:

     

    sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E -Q "BACKUP DATABASE [WSS_Content] TO DISK = 'D:\SQL-Backups\SP2007\WSS_Content.Bak' WITH INIT, NAME = 'WSS_Content Full Backup'"\\\

     

    On the server, I have Microsoft SQL Server Enterprise Edition 2005, 9.00.4035.

     

    The current state of the subsite is that it shows HTTP 400 Bad Request. In the Central Admin, the Site Collection List information for the sub-site shows blank information. There is no Title, URL, database name, email address and other info is blank. I tried this commend but no affect:

     

    stsadm -o addcontentdb –databasename WSS_Content.Bak –ur  http://subsite

     

    The WSS_Content database that I am trying to restore to a subsite has data in it, but SharePoint does not recognize the database and can't show the site. My questions are:

     

    Why can I not restore a SharePoint content database with a BAK file created by sqlcmd?

    Do I have to use the stsadm to create the backups and not use sqlcmd?

     

    Any help is much appreciated.


    Project Manager
    Monday, November 8, 2010 11:28 PM

Answers

  • Hi Doug,

     

    Sorry for misunderstood your meaning and keep you waiting so long.

     

    I think the problem is on your IIS, could you please check this KB article: http://support.microsoft.com/kb/293131/, and try the solution it has mentioned.

     

    Hope this could help you.

     

    Regards.

    • Marked as answer by David HM Monday, November 22, 2010 7:31 AM
    Friday, November 12, 2010 1:36 AM

All replies

  • Do you have the same patch levels of sharepoint in both environments? They need to match exactly.

    When you do stsadm -o addcontentdb, this has to be the name of a SQL Database that is currently ONLINE on your sql instance. Thus you will need to restore the .bak file to your sql instance before running the addcontentdb command.


    Conrad Goodman MCITP SA / MCTS: WSS3.0 + MOSS2007
    Tuesday, November 9, 2010 11:20 AM
  • Hi Dong,

     

    There are several reasons may cause the system send this error message. From your information, I think the problem is most likely caused by your updates. Could you please check this thread: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/9196b33d-60da-4d9d-abc1-8db935a73811.

     

    Also you can read this article to determine whether this causes: http://portalsolutions.net/Blog/Lists/Posts/Post.aspx?List=1fef67f0%2D70ca%2D4263%2Db683%2Df10c1958687a&ID=45&Web=2a4e9897%2D6530%2D44a1%2D80b5%2D4fac295c2c26.

     

    Hope this could help you.

     

    Regards.

    Wednesday, November 10, 2010 1:58 AM
  • I had the database restored in the SQL Server instance before I ran stsadm -o addcontentdb. The database was attached, restored and running when the command was ran.

    Thanks,

    Paul


    Project Manager
    • Marked as answer by Peng Lei Thursday, November 11, 2010 1:59 AM
    • Unmarked as answer by Doug Fir Thursday, November 11, 2010 11:18 PM
    Thursday, November 11, 2010 1:54 AM
  • Peng,

    I am afraid that is likely the problem. The BAK was done about 2 weeks ago. Since then, many MS Security patches have been applied to the SQL Server and SharePoint (as well as the OS) on the server. I hope the articles you posted will provide a solution.

    Thanks,

     

    Paul

     


    Project Manager
    Thursday, November 11, 2010 1:59 AM
  • I meant I had the database restored using the SQL Server, as described in one of the links you provided. However, this did not resolve the issue of the subiste coming up. The author describes just using SQL Management to attach the database, and everything just came up. That did not happen for me.

    So, I am still having the problem.

    What can I do with BAK file or database (once I restore it to a SQL Server instance) to make it compatible with SharePoint? The other article describes modifying the database, but it was confusing about what I should modify. It did not seem to fit my case.

     


    Project Manager
    Thursday, November 11, 2010 11:06 PM
  • Hi Doug,

     

    Sorry for misunderstood your meaning and keep you waiting so long.

     

    I think the problem is on your IIS, could you please check this KB article: http://support.microsoft.com/kb/293131/, and try the solution it has mentioned.

     

    Hope this could help you.

     

    Regards.

    • Marked as answer by David HM Monday, November 22, 2010 7:31 AM
    Friday, November 12, 2010 1:36 AM
  • Hi Peng,

    The KB article you mentioned above essentially says to "contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site." Plus, I have Windows 2003, not 2000.

    Any other suggestions?

    I will keep pursuing to make this work.

    Thanks.

     


    Project Manager
    Monday, November 15, 2010 7:48 PM