The server has the below event log every hour. --------------------------------------------------------------------- Event Type: Error Event Source: Windows SharePoint Services 2.0 Event Category: None Event ID: 1000 Date: 10/10/2011 Time: 4:40:57 PM User: N/A Computer: WWEB1 Description: #50070: Unable to connect to the database STS_WWEB2_1 on WWEB2\SharePoint. Check the database connection information and make sure that the database server is running. --------------------------------------------------------------------- This server name originally was "WWEB2" but it was renamed to "WWEB1" later. Now the "WWEB2" does not exist. I ever try to remove it as the following procedures. 1. Windows SharePoint Services Central Administration 2. Manage Web Server List > remove server name "WWEB2" But it still appears again after remove. How should I remove the name WWEB2 or records? Thanks.

Ideally, you should have used these steps to rename the server: http://www.smallworkarounds.net/2009/07/renaming-moss-2007-or-sharepoint-server.html Thanks & Regards, Kamlesh | Blog | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.

Ideally, you should have used these steps to rename the server: http://www.smallworkarounds.net/2009/07/renaming-moss-2007-or-sharepoint-server.html Thanks & Regards, Kamlesh | Blog | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.

Hi, How did you rename your server name? You should rename your server in a proper way. And here are some KB articles related to this error: http://support.microsoft.com/kb/900498 http://support.microsoft.com/kb/840685 Hope this helps. Thanks, Pengyu Zhao

Hi, How did you rename your server name? You should rename your server in a proper way. And here are some KB articles related to this error: http://support.microsoft.com/kb/900498 http://support.microsoft.com/kb/840685 Hope this helps. Thanks, Pengyu Zhao

Hi, How did you rename your server name? You should rename your server in a proper way. And here are some KB articles related to this error: http://support.microsoft.com/kb/900498 http://support.microsoft.com/kb/840685 Hope this helps. Thanks, Pengyu Zhao