Microsoft KB Archive/830525

= Live Communications Server Service Does Not Start When You Restart the Computer =

Article ID: 830525

Article Last Modified on 1/29/2004

-

APPLIES TO


 * Microsoft Office Live Communications Server 2003

-





SYMPTOMS
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

When you restart your Microsoft Office Live Communications Server 2003 computer, you may intermittently experience all the following symptoms:  When you start the Live Communications Server utility, and then expand the Servers node, you receive the following error message:

The computer is not part of a domain, network connection is lost or you do not have sufficient privileges to administer the User Services and Global Settings. Make sure network connectivity is available. For more information about network troubleshooting, see Windows Help. If the computer is part of a domain, please log on with the proper credentials.

You receive this message even though your computer is a member of the domain, and you have logged on with the correct credentials. When you start the Services Control Panel tool, you notice that the Live Communications Server service is not started even though the startup type is set to Automatic.  The following events appear in the application log in Event Viewer: Event Source: Live Communications Ser

Event Category: (1000)

Event ID: 16415

Date:

Time:

Type: Error

User: N/A

Computer:

Description: Unable to initialize the registration component, error code is:0xc0700007 (Initialize failure. Failed to initialize the WMI configuration.). The service has to stop. -and- Event Source: Live Communications Us

Event Category: (1006)

Event ID: 7

Date:

Time:

Type: Error

User: N/A

Computer:

Description: Initialize failure. Failed to initialize the WMI configuration. -and- Event Source: Live Communications Us

Event Category: (1006)

Event ID: 20482

Date:

Time:

Type: Error

User: N/A

Computer:

Description: Server could not register for notifications for configuration changes for the class MSFT_SIPESGlobalRegistrarSetting from WMI Provider.   The following event appears in the system log in Event Viewer: Event Source: DHCP

Event Category: None

Event ID: 1002

Date:

Time:

Type: Error

User: N/A

Computer:

Description: The IP address lease  for the Network Card with network address   has been denied by the DHCP server   (The DHCP Server sent a DHCPNACK message).  If you try to manually start the Live Communications Server service, you receive the following error message:

Windows could not start the Live Communications Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -1066401785.





CAUSE
This issue may occur if all the following conditions are true:
 * The Live Communications Server is configured to obtain its IP address information from a Dynamic Host Configuration Protocol (DHCP) server.
 * The Live Communications Server and the DHCP server are on a 100 Mbps network that supports Full-Duplex.
 * The network adapter configuration on the Live Communications Server computer, the DHCP server, or both, have a media type set to Auto Detect.

Note This option may also appear as Auto select and other phrases, depending on your network adapter device.

In this scenario, when you restart the Live Communications Server computer, it may not be able to obtain an IP address from the DHCP server. Because of this, the Live Communications Server service cannot obtain its configuration information from the Active Directory directory service. In some instances, the network stack has not completely loaded and network dependent services, such as Live Communications Server, may not start. You will be able to start the service manually after the computer restarts. To confirm that this is the case, use method 3 in the &quot;Workaround&quot; section of this article to create a batch file to start the Live Communications Server service.



WORKAROUND
To work around this issue, use one of the following methods:

Method 1: Configure the Network Media Type
Modify the network adapter properties on the Live Communications Server computer to match those on the DHCP server. Specifically, set the media type to 100 Mbps Full-Duplex on both the Live Communications Server computer and the DHCP server computer. To do this, follow these steps:
 * 1) Click Start, point to Control Panel, point to Network Connections, right-click Local Area Connection, and then click Properties.
 * 2) Click Configure, and then click the Advanced tab.
 * 3) In the Property box, click Media Type (or click the similar option that corresponds to your network adapter).
 * 4) In the Value list, click 100 Mbps Full-Duplex, and then click OK.
 * 5) Restart the Live Communications Server computer.

Method 2: Assign a Static IP Address
Configure the Live Communications Server with a static IP address, clear the DNS resolver cache, and then start the Live Communications Server service. To do this, follow these steps: <ol> Click Start, point to Control Panel, point to Network Connections, right-click Local Area Connection, and then click Properties.</li> Specify the IP address information for the following items, and then click OK two times.

IP address

Subnet mask

Default gateway

Preferred DNS server

Alternate DNS server

</li> Create a reservation for this IP address on your DHCP server so that it does not assign this IP address to another computer on the network.</li> Clear the DNS resolver cache on the Live Communications Server computer. To do this: <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type cmd, and then click OK.</li> At the command prompt, type ipconfig /flushdns, and then press ENTER.</li> Type ipconfig /registerdns, and then press ENTER.</li></ol> </li> Start Live Communications Server. To do this, type net start rtcsrv, and then press ENTER.</li></ol>

Method 3: Create a Batch File that Delays the Start of the Live Communication Server Services
Use the Sleep.exe utility that is part of the Windows 2000 and Windows Server 2003 Resource Kits to create this batch file. The file waits 60 seconds (or more) and then starts the RTCSRV service and the RTClog service (IM archiving agent) if these services are installed. You can run the batch file from the RUN key in the registry. To create this batch file, follow these steps: <ol> Put the Sleep.exe utility in the %systemroot%\sytem32 directory.</li> Create a batch file. Name it LCSstart.bat. Put the file in the C:\ directory, and then put the following statements in the file: sleep 60 net start rtcsrv net start RTClog .</li> Start Registry Editor, and then locate the following registry subkey:

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.</li> Create a new sting value. Name the string LCS Start and give it the value c:\LCSstart.bat .</li> Restart the server, and then confirm that the Live Communications Server service has started.</li></ol>

Additional query words: RTC chat

Keywords: kbeventlog kbprb KB830525

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.