Sharepoint 2003 died.. New system up... need to connect to existing DB

Sp server acting funny…
I’ve created a new server to replace the disgruntled sp server matching versions… the SQL DB is on another server.
What’s the easiest way to connect the NEW Sp server to the existing database?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

zephyr_hex (Megan)DeveloperCommented:
i can't remember if sharepoint 2003 has the Sharepoint Product & Technologies Config Wizard.  if it does, then run it and join the server to the farm.  if that works, then you'll need to transfer Central Admin to this server, which can be done even though the old server is gone.

if you aren't able to join this server to the existing farm, then try these steps (starting at step 28):
5thcavAuthor Commented:
There is no farm... and the old server is still up and running.. I just cant get the search index working... I was hoping i could just name the new server as the old and reconnect the the db... its a 200gig pig expanded accross 4 drives..
zephyr_hex (Megan)DeveloperCommented:
is this a standalone install?  (it's possible to install sharepoint as a farm, and only have one server).  if the SQL database is on a different server than the original sharepoint install, then it's a farm install.

if i'm reading your original question correctly, SQL is installed on a separate server.  if that's the case, then join the new server to the farm and transfer Central Administration to the new server.  you can then unjoin the old server from the farm, and send it off into retirement.

to add the new server to the farm:
To add a server by using the user interface
On the new server, click Start, point to All Programs and then click Microsoft SharePoint 2010 Products Configuration Wizard.

On the Welcome to SharePoint Products page, click Next.

On the Connect to a server farm page, click Connect to an existing server farm.

Click Next.

On the Specify Configuration Database settings page, type the name of the instance of SQL Server in the Database server box, and then click Retrieve Database Names.

Select the name of the configuration database in the Database name list, and then click Next.

On the Specify Farm Security Settings page, type the name of the farm passphrase in the Passphrase box, and then click Next.

On the Completing the SharePoint Products Configuration Wizard page, click Next.

On the server that hosts Central Administration, click Manage servers in this farm to verify that the new server is part of the farm.

You can also verify a successful server addition, or troubleshoot a failed addition by examining the log files. These files are located on the drive on which SharePoint Server 2010 is installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\LOGS folder.
On the Servers in Farm page, click the name of the new server. Use the list of available services on the Services on Server page to start the services that you want to run on the new server.

Configure SharePoint Server 2010 so the new server can accommodate the role it was intended for. For more information, see Configure the new server.
(from here:

here is how you transfer Central Admin:
zephyr_hex (Megan)DeveloperCommented:
sorry, that was for sharepoint 2010.  here are the 2003 instructions:

i believe the steps for transferring Central Admin are the same as the link i posted above.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
If your issue is only with the Search Index, then this can be fixed, often by creating a new SSP, assign it to a "blank" new Search DB, and then repoint all your other Content Databases to the new SP.

You can then remove the original SP which would not have anything assigned to it and then re-create it and "re-map" everything back...

Now if you have a new SP Environment and you just want to recover the old content database(s) on the new environment, then you can re-attach the Content database(s) to the new environment using the stsadm command.

Hope this helps.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.