Microsoft KB Archive/889530

= The Exchange Conference Manager Service does not start when you restart the Exchange 2000 Conferencing Server computer after you upgrade a domain controller to Windows Server 2003 =

Article ID: 889530

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Conferencing Server

-



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



SYMPTOMS
In an organization that is running Microsoft Exchange 2000 Conferencing Server, you upgrade a Microsoft Windows 2000-based domain controller to Windows Server 2003. After you upgrade, you experience both the following symptoms:   After the Conferencing Server computer is restarted, the Exchange Conference Manager Service does not start. When this problem occurs, the following event is logged in the System log: Event Type: Error

Event Source: MSExchangeCONF

Event Category: Startup/Shutdown

Event ID: 8202

Date:

Time:

User:  N/A

Computer:

Description: The Exchange Conference Management Service did not start because a failure occurred during initialization. Error code: 8007006e; Message: The system cannot open the device or file specified.  After a period of time that is between about 30 minutes and 4 hours, the Exchange Conference Manager Service starts successfully.

Therefore, users in your organization cannot use the functionality that is provided by Exchange 2000 Conferencing Server for up to 4 hours after you restart the Conferencing Server computer.



CAUSE
When the Exchange Conference Manager Service starts, it performs an unnecessary LDAP referral chase operation. If an error occurs in this LDAP referral chase operation, the Conferencing Server cannot look up the conference mailbox in the Active Directory directory service. Therefore, the Exchange Conference Manager Service quits.

For additional information about LDAP referral chasing, see the &quot;Active Directory Searches Processes and Interactions&quot; section of the How Active Directory Searches Work document. To view this document, visit the following Microsoft Web site:

http://technet2.microsoft.com/windowsserver/en/library/8196D68E-776A-4BBC-99A6-D8C19F36DED41033.mspx



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to obtain the latest Exchange 2000 Server service pack

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name --  10-Jan-2005  01:43  6.0.6617.36       589,824  Xcmsadm.dll 10-Jan-2005 01:43  6.0.6617.36       524,288  Xconfmgr.exe 13-Jan-2005 16:10  6.0.6617.36     1,314,816  Xconfmsg.dll 10-Jan-2005 01:43  6.0.6617.36       364,544  Xdcsadm.dll 10-Jan-2005 01:43  6.0.6617.36       339,968  Xdcsmgr.dll 10-Jan-2005 01:43  6.0.6617.36       241,664  Xipcadm.dll

Hotfix installation information
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.

After you install this hotfix, the following new registry value is available to control whether the Exchange Conference Manager Service chases LDAP referrals:

Value name: DoNotChaseReferrals

Value type: REG_DWORD

Value data: 00000001

If this registry value does not exist, or if this registry value is set to 0 (zero), the Exchange Conference Manager Service performs the default behavior of chasing LDAP referrals. If you set this registry value to a non-zero value such as 1, the Exchange Conference Manager Service does not chase LDAP referrals.



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Conferencing Server.



MORE INFORMATION
Depending on your network topology and on how Exchange 2000 Conferencing Server is deployed in your organization, you may experience both the following symptoms after you install this hotfix:
 * When you manage the Site Conferencing object in the Conferencing Manager, you are prompted to define the Site Conference Calendar mailbox. You are prompted whenever conferencing management is performed.
 * After you define the Site Conference Calendar mailbox and conferencing resources, they are not displayed in the user interface.

To resolve this problem, configure LDAP queries to start in the local domain after you turn off LDAP referral chasing. For additional information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:

277778 Always prompted to configure the Site Conference Calendar mailbox

Additional query words: XADM

Keywords: kbqfe kbhotfixserver kbfix kbexchange2000presp4fix kbbug KB889530

-

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

© Microsoft Corporation. All rights reserved.