Microsoft KB Archive/896557

= The Live Communications Server service does not start, and events are logged in the application event log after you activate a Live Communications Server 2005 computer =

Article ID: 896557

Article Last Modified on 5/21/2007

-

APPLIES TO


 * Microsoft Office Live Communications Server 2005 Enterprise Edition
 * Microsoft Office Live Communications Server 2005 Standard Edition

-







SYMPTOMS
When you run the Activate Enterprise Edition Server Wizard to assign your Microsoft Office Live Communications Server 2005 computer to an Enterprise Pool, the Activate Enterprise Edition Server Wizard finishes successfully. However, the Live Communications Server service does not start on the newly activated server. Additionally, all the following events are logged in the application event log:

Event ID: 14401 Event Source: Live Communications Server

Event Category (1001)

Event ID: 14401

Date:

Time:

Type: Error

User: N/A

Computer:

Description: The current machine is not in the list of internal servers. This may cause the server to have interoperability issues.

Resolution:

Please check the AD consistency or reinstall the server.

Event ID: 14352 Event Source: Live Communications Server

Event Category (1001)

Event ID: 14352

Date:

Time:

Type: Error

User: N/A

Computer:

Description: Unable to start the stack

Error: 0xC3E92047 (No Message Text Found).

Event ID: 16422

Event Source: Live Communications Server

Event Category (1000)

Event ID: 16422

Date:

Time:

Type: Error

User: N/A

Computer:

Description: Failed starting the protocol stack. The service has to stop

Error code is: 0xc3e92047 (No error message text found).

Cause: Check the previous entries in the event log for the failure reason.

Resolution:

Try restarting the server after resolving the failures listed in the previous event log entries.

Event ID: 12299 Event Source: Live Communications Server

Event Category (1000)

Event ID: 12299

Date:

Time:

Type: Error

User: N/A

Computer:

Description: The service is shutting down due to an internal error.

Error Code: 0xC3E92047.

Resolution:

Check the previous event log entries and resolve them. Restart the server. If the problem persists contact product support.



CAUSE
This problem may occur if the domain part of the fully qualified domain name (FQDN) for the computer that is running Live Communications Server 2005 does not match the primary DNS suffix of that computer. For example, this problem may occur if the following conditions are true:
 * The primary DNS suffix of the computer is domain1.example.com.
 * The domain part of fully qualified domain name of the computer is corp.domain1.example.com.

When the Activate Enterprise Edition Server Wizard activates your Live Communications server, the activation process uses the computer's FQDN to create a &quot;trusted server object&quot; for Live Communications Server 2005. However, if the primary DNS suffix for the computer that is running Live Communications Server 2005 is different from the domain part of the FQDN, Live Communications Server 2005 cannot locate that &quot;trusted server object&quot; entry in the Global Setting container in the Active Directory directory service.



RESOLUTION
To resolve this problem, configure the network interface DNS suffix to be the same as the domain part of the computer's FQDN. To do this, follow these steps:  Deactivate the Live Communications server. To do this, follow these steps:  Start the Microsoft Office Live Communications Server 2005 tool. Expand Forest - . In this step, the placeholder  is the name of your domain. Expand Domains, expand '''. , expand Live Communications servers and pools, expand your Enterprise Pool, right-click the server that you want to deactivate, and then click Deactivate'''. Follow the steps in the Live Communications Server 2005 - Deactivate Wizard to deactivate your Live Communications server.</ol> </li> Click Start, point to Control Panel, and then click System.</li> Click the Computer Name tab, click Change, and then click More.</li> Use one of the following methods: <ul> Type the DNS suffix that your domain uses in the Primary DNS suffix of this computer box. For example, if you use Group Policy to assign a DNS suffix of &quot;example.com&quot; to computers that are in your domain, type example.com in the Primary DNS suffix of this computer box.

Note To see the primary DNS suffix that is assigned by using Group Policy, follow these steps: <ol style="list-style-type: lower-alpha;"> On a domain controller, start the Active Directory Users and Computers tool.</li> Right-click the container where you have configured the policy to assign a DNS suffix. For example, right-click the domain container or the organizational unit container where your Live Communications Server 2005 computer is located.</li> Click Properties.</li> Click the Group Policy tab, click the Group Policy object that you used to assign a DNS suffix, and then click Edit.</li> Under Computer Configuration, expand Administrative Templates, expand Network, and then click DNS Client.

Note In Microsoft Windows 2000, under Computer Configuration, expand Administrative Templates, expand System, and then click DNS Client.</li> In the right pane, double-click Primary DNS Suffix, and then view the value that is displayed in the Enter a primary DNS suffix box.</li></ol> </li> Click to select the Change primary DNS suffix when domain membership changes check box.</li></ul> </li> Click OK two times.</li> Click OK when you receive the following message:

You must restart this computer for the changes to take effect.

</li> In the System Properties dialog box, click OK, and then click Yes when you are prompted to restart the computer.</li> Activate the Live Communications server.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

258503 DNS registration errors 5788 and 5789 when DNS domain and Active Directory domain name differ

Additional query words: LCS 2005, suffix, DNS, RTC, chat

Keywords: kbdeployment kbeventlog kbtshoot kbpending kbbug kbprb KB896557

-

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

© Microsoft Corporation. All rights reserved.