Knowledge Base

Live Communications Server Does Not Start After You Change the Computer Name

Article ID: 830535

Article Last Modified on 11/19/2003

APPLIES TO

Microsoft Office Live Communications Server 2003

SYMPTOMS

After you change the fully qualified domain name (FQDN) of a server that is running Microsoft Office Live Communications Server 2003, you may experience one or more of the following symptoms:

When Microsoft Windows Messenger users try to connect to Live Communications Server, they receive the following message:

The server name servername for the SIP Communications Service cannot be resolved. The server name may be incorrect, or there may be a problem with your network connection. If the problem persists, please contact your network administrator.
Live Communications Server does not start automatically when the computer starts. When you start the Live Communications Server utility, right-click your server, and then click Start, you receive the following error message:

Live Communications Server Snap-in cannot start Live Communications Server. Try again. For more information, see Event Viewer. Open the Application node and look for event log messages for this program.
When you view the application log in Event Viewer, the following events are displayed:

Event Source: Live Communications Ser
Event Category: (1001)
Event ID: 12291
Date: date
Time: time
Type: Error
User: N/A
Computer: servername
Description: The service is registered for a different machine. Please reinstall the product.

Event Source: Live Communications Ser
Event Category: (1000)
Event ID: 16417
Date: date
Time: time
Type: Error
User: N/A
Computer: servername
Description: Unable to initialize the protocol stack, error code is: 0xc0410805 (The machine name has changed since Microsoft Live Communications Server has been installed. Please uninstall and reinstall the product.). The service has to stop.

CAUSE

This issue occurs because Live Communications Server 2003 does not support changing the FQDN of a Live Communications Server computer.

RESOLUTION

To resolve this issue and retain the new server name that you configured, follow these steps.

Note Microsoft recommends that you perform a full back up of your Live Communications Server computer and your SQL Server database before you follow these steps.

Start the MSSQL$RTC service if it is not already started. To do so, follow these steps:
1. Click Start, click Run, type services.msc in the Open box, and then click OK.
2. In the list of services, right-click MSSQL$RTC, and then click Start.
Export the Home Server database by using the Dpimpexp.exe tool. To do so, follow these steps.

Note By default, this tool is located in the following folder:

Program Files\Microsoft LC\Server\Support
1. Click Start, click Run, type cmd, and then click OK.
2. Change to the folder where the Dpimpexp.exe tool is located, type the following command, and then press ENTER:
  
  dbimpexp.exe /hrxmlfile:rtcdata.xml
  
  You receive the following message (where number is the number of resources exported):
  
  Exporting number Homed Resources from database...
  100% complete.
  Export completed successfully.
  
  Note This command may take several minutes to complete.
Remove Live Communications Server 2003 together with the Home Server database. To do so, follow these steps:
1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. Click Microsoft Office Live Communications Server 2003, and then click Change.
3. In the Live Communications Server - Setup Wizard, click Next.
4. Click Remove, and then click Next.
5. Click to clear the Keep the Home Server database check box, and then click Remove.
6. When Live Communications Server 2003 has been removed successfully, click Finish.
Reinstall Live Communications Server 2003.
Import the Home Server database by using the Dpimpexp.exe tool. To do so, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.
2. Change to the folder where the Dpimpexp.exe tool is located, type the following command, and then press ENTER:
  
  dbimpexp.exe /import /hrxmlfile:rtcdata.xml
  
  You receive the following message:
  
  Importing Homed Resources into database...
  number Homed Resources imported.
  Import completed successfully.
  Reindexing all tables and updating statistics.
  
  Note This command may take several minutes to complete.
If the users are not already assigned to the renamed Live Communications Server, use the Live Communications Server Move Users Wizard to move the users to the new Home Server. To do so, follow these steps:
1. Start the Live Communications Server utility.
2. Right-click Orphaned users, and then click Move users.
3. In the Move Users Wizard, click Next.
4. In the Move users to the following home server list, click your server, and then click Next.
5. Follow the remaining steps to move the users to the renamed Live Communications Server.

WORKAROUND

To work around this issue, rename the server to its original name and then restart the computer when you are prompted to do so. When the computer has restarted successfully, clients can again connect to Live Communications Server 2003.

MORE INFORMATION

To rename a computer that is running Live Communications Server, follow these steps:

Remove Live Communications Server 2003 by using the Add or Remove Programs tool in Control Panel. During the program removal, on the Remove the Program screen, make sure that you leave both of the following check boxes selected:

Keep the Active Directory objects in domain controller
Keep the Home Server database
Rename the computer, and then restart the computer when you are prompted to do so.
Reinstall Live Communications Server 2003.
If the users are not already assigned to the Live Communications Server, use the Move Users Wizard to move the users to the newly renamed Live Communications Server.

Additional query words: LCS, RTC

Keywords: kbprb KB830535

Microsoft KB Archive/830535

Contents