Question : Can't Launch SharePoint 3.0 server after machine rename

I installed Sharepoint 3.0 trial on a machine running server 2008.  It installed fine and ran.  I realized the machine name would be misleading, so I renamed it and put it in a domain on our network.  Upon restart, I launched the Sharepoint admin center, and got a message telling me I needed to run the SharePoint confiuuration Wizard.

During the Wizard process, after successfully completing 2 or 3 of 10 steps, I got the following error:

Failed to connect to the configuration database.
An exception of type System.Data.SqlClient.SqlException was thrown.  Additional exception information:
Access to the module dbo.proc_getObjectsByClass is blocked because the signature is not valid.

It then proceeds to give me the path-link where the event log is located. I'm including that as an attachment (text).

Any help to resolve would be greatly appreciated.

Thanks

Attachments:

sharepointlog.txt (687 KB)  (File Type Details) 

sharepoint log

Answer : Can't Launch SharePoint 3.0 server after machine rename

If this is a simple SharePoint installation, it will be easier to run hte configuration wizard and create use the option create a new farm.  This will create a new configuration db.  You can then restore the SharePoint site you have been testing by creating a new web app and attaching the content database from the original web app hosting your sites.

1.  run configuation wizard using create a new farm option
2. Once in central admin, create a new web app with a database called delete_me
3. remove database on new app by looking at web app porperties and content databases option
4. find the name of the old content database you used p[rior to changing server name
5. add the old contentdatabase the the newly created web application using the command stsadm -o addcontentdb

   5a...use stsadm -help addcontentdatabase to see how to use the command

6. after adding the content database to the new app, restart IIS by using iisreset
7. Browse to all urls and check to see if content is ok
8. restart your search services