Changing WSS Server to a new machine

[macleod1021]

OK...here's the scenerio. I just got in a brand new server to run our Sharepoint on. My current set up is WSS running on an old server and the databases running on a seperate SQL Server. I got it loaded with 2003 standard, updated it with latest SP's. Checked connectivity and everything looks good. Now the fun began. I'm trying to get the new box to a point where I can just make the DNS change for my companyweb CName and everyone will point to the new box and never know there was a change.

Attempt #1.
Installed WSS and used the same database information as the original server. Result: Error attempting to create database.

Attempt #2.
Reinstalled WSS and let it install a local copy of databases and then attached to the existing databases. Result: Error stating that the virtual site was not in the config database.

Attempt #3.
(progress) Reinstalled WSS and connected to SQL Server...but created new databases. A blank WSS site came up locally. Then, I went into Administration and changed the config database to the existing. When I refreshed the website I got "the virtual server that is referenced here is not in the config database.".

This is where I'm at now. If anyone has some suggestions, please let me know. I'm still working on finding the answer, but a general direction to go in would be nice

Thanks in advance.

 

[macleod1021]

OK...I figured it out...kinda

The problem is that in the Docs database within the original Content database the Site ID was changed to the Site ID that related to the blank content database. Once I changed the SiteID field in the Configuration Database to match the SiteID in the content database, everything came up as expected.

 

[MonkeyNut]

Hi

Could you explain your second post a bit more please, as I have a WSS site and sub sites set up which are working great on a test server. I now want to migrate/move it over to another server as you've done. A bit more details would be great or if you have time a run through of the steps that you took would be ideal.

Thanks

 

[macleod1021]

The reason I had so many problems was because I was attempting to have no down time. If you can, schedule a time when you can take everything offline and use the instructions at this link

http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf17.mspx?mfr=true

(Migrating the content databases to a server farm).

Even if you're using the server farm method now this should work. I didn't find this until after I started my migration. I think I caused my own problems by not bringing the configuration database over when I moved the content.

If you have troubles, post again. I've been through it a lot