Pingback from  28 Links Today (2007-08-06)

Great post!

That's what I've been searching for.

Pingback from  Links (8/7/2007) « Steve Pietrek’s SharePoint Stuff

Goede post Mirjam.. dit had ik nodig! :)

Can this be used for WSS 3.0??

It certainly seems like it, these appear to be standard SharePoint Stsadm commands.

Please amend your blog entry to include WSS 3.0 servers.

Thank you, tom

Indeed Tom, the same goes for Windows SharePoint Services 3.

Anwender revoltieren, wenn man ihnen ihr SharePoint wegnehmen will - nachzulesen bei RTodd . Tiffany

Thank you so much - your help on this saved so much time!

WSS 2.0 Best Practices: Using Disposable Windows SharePoint Services Objects Creating a link-enabled

thanks I was stuck using a servername that really was less than desirable, thanks for the post

What about SQL 2005?  Do I need to change it.  We are using one single machine to host both Sharepoint 2007 and MSSQL 2005.

*** MSSQL 2005 is the DB engine for Sharepoint 2007.

Thanks, Mirjam.

Just to confirm, I will need to change anything for the MSSQL 2005 server.

Thank you very much!

Thanks!

Didn't believe it - but it worked :-)

Thanks

Wish i had found this solution before...

Awesome! This worked like a charm!!!!

YOU ROCK, thanks!!!

=)

Mirjam van Olst van Macaw heeft een interessante post over renaming: Renaming a MOSS server is meticulous...

Pingback from  SharePoint 2007 link love 09-22-2007 at  Virtual Generations

regarding the last point:

"If you already have a search index drop this, and rebuild it"

Is this necessary only for the indexes of content stored on the MOSS server itself (which contain the old name in the URL)?  Or do external content sources need to be recrawled as well?  I am asking because I have a complicated set of external sources, some of which need to have crawls kicked off manually with Crawl Rules changed between crawls and this takes several days.  If I can get away with just recrawling the MOSS server it would be great, but I want to be prepared in case I need to drop the entire index.

Thank you - let me clarify the question.  

Is it necessary to actually drop the index?  Or would it be sufficient for me to do a full crawl of the MOSS content, which should overwrite those URLs pointing to pages on the MOSS server?

I didn't know if there was information other than the individual rows of the index table containing pointers to the MOSS server which needs to be reinitialized.

Thank you in advance :)

Ben

Thank you - this is good to know in advance :)  I'll plan time in for rebuilding all my external content source indices.

Thanks again for your great writeup!

- Ben

One of the things that I didn't notice in the list - changing the URLs of the SharePoint sites in the Content Sources.  Do I need to change from http://oldMOSSServerName/ to http://newMOSSServerName/ in the "start addressed" box?  Or does it still recognize http://newMOSSServerName/ due to how the content sources are registered?

Also, there is an sps3://newMOSSServerName/ starting address in there - what is that for?

Thanks all for the help,

Ben

Good thing I ran into this when I did.. I got a little too trigger happy and decided to just rename the server.. In case any one renamed the server before doing the steps above, just rename it back and then follow the steps; it'll work.

Thanks for putting this together!

DM

Hi

What would you do if you have to move the server into a DMZ and rename it. There is no domain credentials carried over.

Cheers

Thanks for your post,....

Note: if you have an MSSQL 2005 server running on the same machine aswell, execute the following query on your SQLServer:

<code>

sp_dropserver 'OldServerName\Instance'

go

sp_addserver 'NewServerName\Instance'', 'local'

</code>

Thanks for the post. It helped a lot.

I followed the steps. Everything works except the 'MySite' on the portal. It is still pointing to the old server name. Anyway to chaneg this?

Hi,

I renamed my WSS 3 server using your instructions (using MSSQL DB on same box) and everything worked except for a recurring error 1000 in the Event Log (in the event description there is another error code #50070). A search of this error number seems to indicate that the Sharepoint Timer Service is still trying to access the ConfigDatabase using the original server name. The rest of the installation works fine (config, site collections, etc). I tried to run a backup but it never started because I think the Timer Service is not working correctly. The account the Timer Service service uses is correct. Any ideas?

Thanks in advance.

I figured out my problem with the Timer Service generating errors. Turns out there was a DSN in the registry that still referenced the old SQL servername. I changed this entry to the correct SQL server name and the errors went away and the Timer Service started working correctly. The registry entry that needed to be changed was [HKEY_LOCAL_MACHINE}/Software/Microsoft/Shared Tools/Web Server Extensions/12.0/Secure/ConfigDB/dsn

Cheers,

Tom

what exactly do you mean by ' Check all application pool identities in IIS, update where the old machine name is still there. ' i checked and did not see any server names here. I carried out the whol einstruction and cannot see my sites, except for configuration console.

this is my second attempt in posting due to error and lost a looong text of post so will keep it short and right to the point.

Please help!

-my installation runs the default SQL server like DB on same machine.  

-I had to rename the server from hostname1 to hostname2.domain.com in order for users not part of our network to be able to access.

-followed the instruction above, everything went smooth, then lastly did the machine name change and reboot.

-now can not access Sharepoint sites or the Central Administration.

-error on Event log, this seemed to be the main error.

Event_ID: 3355

Cannot connect to SQL Server. hostname2.domain.com\MICROSOFT##SSEE not found. Additional error information from SQL Server is included below.

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

on the bottom right of my window, it shows that the database is running on HOSTNAME2.  is this discrepancy in causing the problem?  This is a production intranet that went live last week, any help anyone can provide me would be greatly appreciated!!

Tony

I followed the instruction,

Hi Vijay,

did you solve the problem with "My Site"? Same trouble here, no solution yet.

Regards,

Matthias

Hi Mirjam, hi Vijay,

> did you solve the problem with "My Site"? Same

> trouble here, no solution yet.

having said that I stumbled across something called 'SharedServices1' comming from central administration. There we were able to configure MySite. Everything fine now.

Thanks for this blog!

Matthias

Oops, last post didn't make it. Once again, thanks and: the answer to the 'MySite'  trouble is to use the 'SharedServices' from central administration. There you can configure the 'MySite's.

Matthias

Hi,  

Please disregard my post.  I ended up reinstalling the OS and recovering the site.  For my purpose, using the alternative access mapping only seemed to work.

If you are using the internal database that comes default with Sharepoint Service on a single tier installation, I strongly recommend not changint the machine name.

Cheers.

Tony

Hi Mirjam:

Thank you  so much for this great post...it came as ready made solution to my situation in which I had changed the name of the machine after installing MOSS 2007, and web application stopped connecting to the database with the message "Cannot connect to the configuration database". I just followed the steps you mentioned and it started working again.

Thank you so much again.

-Pankaj

Hi,

Very Nice post. Thanks a lot.

Great post!

I am working with like a Pro

How do you go about dropping the index?

Hi All,

I'm new to Sharepoint and have been setting up and playing with Sharepoint 2007. I am required to change the machine name that has Sharepoint 2007 and SQL 2005 installed on it. Is the above procedure for renaming Sharepoint 2007 server etc....

Secondly, dumb question time, "MOSS" can this refer to "Microsoft Office Sharepoint Server" & "Microsoft Office Search Server"? Sorry in advance for the novice questions!

Kind regards.

Pingback from  SharePoint 2007 How To List &laquo; SharePoint Sherpa

Hi,

We have recently moved our sharepoint server, after moving came across the Cannot connect to the configuration database error when trying to goto both the admin site and normal site/s. I have followed these steps, but when I run the command updatefarmcredentials I get the following error:

Error updating the administration application pool credentials.

Help??

Hi everyone,

I have recently renamed an existing domain. Everything is working fine in new domain. After rename my SQL sever 2005 does not work. I found the sql server mangement studio was missing.I have zero knowledge in SQL. Please help me,

Thankyou

clementrosario@gmail.com

Hi,

I changed the machine name (in fact domain name as well as machine name) before changing the server name. So i m gettiing the error: "Can not connect to Configuration Database".

I tried the method above...but to no avail.

Is there a way ...i can get my sites  working now. As Central Administration is also not working now...i can not create new sites even.

Thanks

Useful blogs / articles..

Hi Mirjam,

         Thanks for such informative blog. I have some alike issues In my case the system is having MOSS7 and MSSql 2005 we have got system when client had already changed the machine name and IP address so we were not able to reconfigure the MOSS7 and then we rename the server to rectify the issue with the MSSql 2005 and executed the sp_dropserver and sp_addserver respecively but still not able to configure the MOSS7 back on the box. Please give your valueable comments to resolve this issue as now we want the old sites to be restored and make the system back into action. Currently the site that was hosted on MOSS7 is down and we are not even able to access the central admin of MOSS7 but able to log in the database. When we run the configuration wizard it throughs error while connecting to data base in step 2 the installation of our is stand alone. Please respond asap.

I used this method to rename my server, but I found alot of little things that had to be retouched. All my Logo URL's had to be pointed to the new server name. Any custom pages with url's had to be modified.

My deployment is not very large right now, but I could see this being a major headache depending on what content you've got. I guess the answer is to be careful to use relative url's whenever possible.  

How do I access my site on MOSS 2007 site after changing my System IP address? Before changing the IP address I was able to access my site and work with it. Now its not working after changing the IP address.

Appreciate if anybody gives a solution for this problem ?? Thanks.