I have full and differential backups from wss 3.0 . I used stsadm to backup. Server was gone. I created new site. When I was trying to restore , I am getting this error: stsadm -o restore -url http://site1 -filename "c:\backup\spbr0066\0000000A.bak" -overwrite "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 berestored to a server with version '1162887508.196608.17694860.0' or later." New portal is wss 3.0 . and I setuped SP1 too. If you have any idea, It will help me. Thanks

Was the backup made from a server running SP1? John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

Also, make sure you the server you are doing the restore on is up to date with Windows Updates. If your original server had all of its updates and this new server doesn't, that could also cause issues. John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

Hi, Were you able to fix the issue. I'm facing the same issue. Would appreciate if you could reply Thanks Ramesh

Ramesh- Did you ensure that the Windows Updates on your new server were up to date before restoring? That can definitely cause the issue. John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

John, I did have all the latest updates on both windows server(SP2) and MOSS (SP1) with all updates. Still I'm getting the same error like 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 berestored to a server with version '3701403.0.1196032409.29915337' or later. We did the backup in the production server and one of the user deleted the site() and we're trying to get the site backup. I saw few post on this error. http://blogs.technet.com/wbaer/archive/2007/05/22/understanding-and-handling-microsoft-it-site-delete-capture-1-0-archives.aspx - I did install the MSITDelete Site capture on my local machine. Not sure that is the problem. If only have installed this the production, that would have saved almost two days and still no postive results http://serverdays.com/2007/08/10/problems-using-stsadm-to-backup-windows-sharepoint-services-30/ Any help will be greatly appreciated. Thanks for the mail Ramesh

The error you are getting is most of the time a result of theupdates for Windows Server not being current. If you are certain they are to date, then it is possible that your backup could be corrupt. Were you also doing SQL backups that you could restore from? John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

I managed to work my way around this error. My case was fairly simple - i had a farm backup off an old machine that I had long since taken out of service. Iwanted to restore a single web application and was running into the version error on the stsadm -o restore command. Part of the problem was that my production server is now sharepoint sp1 and the backup was retail. Luckily, i have a test virtual machine that doesn't have sp1 on it yet, but both before and after updating that test environment with the latest security patches, i still had the version issue trying to do the restore. Here are the steps I followed (Note: this involves modifying sharepoint tables directly in the database, very taboo in the eyes of MS - your mileage may vary ): 1. On a test box (do not try this in production!) create a new web application (central admin >> Application Management >> create or extend web application >> Create a new web application. Go ahead and create a new iis site and web pool. Give your content database a nice name like 'wss_content_restore_fix' 2. Create the site collection - basic team site with a name of 'test' or something simple that you will remember. 3. Figure out which bak file from your sharepoint backup corresponds to the site you're trying to restore. In my case, i was able to look at the backup log file and determine by backup file was named '00000015.bak'. 4. Restore this database via sql server management studio. Be sure to give it a name you can remember and one that is different than any other content database (i.e. don't overwrite anything). Something like 'wss_content_restore_from_backup'. 5.Use sql server activity monitor to see if the content database is being accessed (it will be). Stop services and processes until you see no more activity on the database you created with you new site ('wss_content_restore_fix' if you named it as suggested in step 1). iisreset, stop sharepoint search, timer, reporting services services, stop the app pool in iis, etc. I even had to stop and restart sql management studio to get all the activity stopped. 6. Once there's no more activity, rename the db to something along the lines of 'wss_content_restore_fix_spcreated_with_test_site'. Be sure to remember the old name! In fact, copy it into the clipboard because you'll need it in the next step. 7. Rename your recently restored database to the name of the content database you renamed in the previous step (i.e. rename 'wss_content_restore_from_backup' to 'wss_content_restore_fix') 8. Double check the security of the new database - in my case i had to remove a bunch of logins from the old machine that were no longer applicable in the new environment and reset the dbo (right click the database, properties, files, set the owner to match what is on 'wss_content_restore_fix_spcreated_with_test_site'). 9. Here's the magic that makes all this work - query the sitemap table in the sharepoint_config database (select * from sitemap). One of the id's corresponds to the site you created back in step 1. We need to change this guid to be the one from the restored site. On each content database, query the webs table to determine the appropriate site ids. From the spcreated content database, the siteid column in the webs table will be found in the id column in the sharepoint_config.dbo.sitemap table. update that id with the webs.siteid from the site you are trying to bring back from the restored content database. Be very careful on this step, since you are directly modifying a sharepoint table. In my case, this was the fix: update sitemap set id = 'D98D0B21-6FF1-4547-870E-23AA82CC4A10' where id = '3CA366D5-464D-402C-A097-558DB5406A11' where 'D98D0B21-6FF1-4547-870E-23AA82CC4A10' was the webs.siteid from my restored content database and '3CA366D5-464D-402C-A097-558DB5406A11' was the id from the sharepoint created site. 10. Restart all the services, do an iisreset, say a little prayer, cross your fingers, hold your breath, and try to bring up the site. Hopefully i didn't miss anything, but this worked for me and I haven't seen it documented anywhere, so here it is. My next step is to upgrade this test environment to sp1 and restore it to my production site using the standard backup and restore procedures. Good luck!

Thank you for getting me this info. I don't have to do this on a test server....per this morning (13.5 hours ago) I smashedour MOSS Portal into the wall with a great smile ....did I say smile? The backup and restore function through STSADM (The admintool from ***, from today forth) made sure that I killed it single handedly....(on my test server, VPC, everything went fine, although I received the same message: The site I wanted to create already existed, so use overwrite). With a single sitecollection and 30GB of data....imagine.....so I am going to try this last resort....If you don't hear from me it worked....or not....

was the problem solved ?I am having the exact problem ... I only have the backup files, no database backups and the old server is not accessible... I dont even know the old server setup (updates , service pack...etc.). and the new serverhas fresh installation of WSS (along with its config database, new content database for anewly created empty team site). however, teh users are defined as in the old server, theweb application name, server name and site collection name are defined as in the old server...was the problem resolved? and how? before I tryandy solution (as this will require preparing a virtual machine as well :) ) Thanks all,

Moving to Admin (Backup issue)WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx

Hi there. Just a quick note to let you know I found your post invaluable, it got me out of a real bind. Thanks for your efforts! :-)

was solved? I have a SP 2010 and have: '1178817357.0.384944.0' or later (i just have wps file :( )Regards