Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sharepoint Services Original Release

Status
Not open for further replies.

adamsonk100

IS-IT--Management
Sep 12, 2005
2
US
Hello,

I currently went through a disaster recovery for our company server which was running the released to production Windows Sharepoint services (WSS) 6.0.2.5530. I have reinstalled WSS now after the recovery, however, it is a newer version (SP1) and when I try to reconnect to the older database WSS specifies the database is of an old schema and needs to be updated. Well the only way I have found to update a database is if it is already attached to Sharepoint of which I can not complete because it will not let me. So therefore my only solution is to plead with anyone out there to send me the original release version of WSS 6.0.2.5530 (send to (kadamson@rvrdg.com) since microsoft no longer has it available for download. This way I can reload it, connect the database, then apply SP1. If you know any other work around i'm open for suggestions.
 
Thomas,

Thank You for the link! Although it was not a direct process I did get my sites up and running. This is indeed version 6.02.5530, however, it appears I had 6.0.2.6411 *shakes head* so therefore I got the same error. However with this version I was able to trick it per say. To get my old site to work I did the following:

1. loaded version 6.02.5530 and extended sharepoint to my webs creating databases with the exact names of my backups.
2. I then dropped the content databases from the webs
3. Next go to an administrative package for SQL server and restore your backups.
4. Using a table editor for SQL server go into the table SystemVersion and change the version number to 6.02.5530.
5. go back to Sharepoint administrator and reattach the content databases
6. Using a table editor for SQL server go back into the table and change the version number back to its original (In my case 6.02.6411).
7. Now go to the command line and type in the following:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN>stsadm -o upgrade -forceupgrade

This will upgrade your databases to the current version.
8. Your webs should now be functioning properly

What a pain in the &%^$. They really need to make an upgrade routine for Sharepoint when you add a content database.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top