XADM: Error Message: The Exchange Conferencing Service May Not Have a Default Conferencing Mailbox Defined for It (330317)


The information in this article applies to:

  • Microsoft Exchange 2000 Server
  • Microsoft Exchange 2000 Enterprise Server
This article was previously published under Q330317
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

When users try to schedule a conference in Microsoft Outlook or by using the Exchange 2000 Conferencing Web Scheduler, they may receive an error message similar to the following:
The Exchange Conferencing Service may not have a default conferencing mailbox defined for it.
Please try the following:
Contact your system administrator.

Sending the message Error #80010105: Unable to schedule the specified conference.
Microsoft Exchange 2000 Conferencing Server
Additionally, when you view the Application log in the Event Viewer of the Exchange 2000 Conferencing Server, the following event may be displayed: 

Date:     <date>       Source:   MSExchangeCONF
Time:     <time>       Category: Startup/Shutdown
Type:     Error        Event ID: 8212
User:     N/A
Computer: <ServerName>

Description:
The Microsoft Exchange Conference Management service could not log on to
the Microsoft Exchange Information Store - idling until it can. Error code:
81002746; Message: /o=<organization>/ou=First Administrative Group/cn=Recipients/cn=ECSCalendar

For more information, click http://search.support.microsoft.com/search/?adv=1.

CAUSE

This issue may occur if the Exchange Conferencing Server computer cannot create the Conferencing Calendar mailbox. This issue may occur after you install the security update described in the following Microsoft Knowledge Base article:

311401 Windows 2000 Security Rollup Package 1 (SRP1), January 2002

RESOLUTION

To resolve this issue, follow these steps on the global catalog server (or servers).

NOTE: These steps are taken from the following Microsoft Knowledge Base article:

309622 XADM: Clients Cannot Browse the Global Address List After You Apply the Q299687 Windows 2000 Security Hotfix

The following registry change is required only if the global catalog servers are not upgraded to Windows 2000 Service Pack 3 (SP3).

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.
  1. In Control Panel, double-click Add/Remove Programs, and then locate the Windows 2000 Hotfix (Pre-SP3) (Q299687). Alternatively, the Windows 2000 Security Rollup Package (Q311401) may be listed.

    For additional information about this hotfix, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    299687 MS01-036: Function Exposed By Using LDAP over SSL Could Enable Passwords to Be Changed

    311401 Windows 2000 Security Rollup Package 1 (SRP1), January 2002

  2. If either of these packages are listed, start Registry Editor, and then locate and click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

  3. In the right pane of the Registry Editor window, locate the value of the restrictanonymous registry value on the global catalog server. If the value is set to 0x2 and either the Q299687 Windows 2000 security hotfix or the Q311401 Windows 2000 security rollup package are installed, change this value to 0x0.
  4. Quit Registry Editor, and then restart the global catalog server for this change to take effect.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type:MajorLast Reviewed:7/17/2006
Keywords:kberrmsg kbbug kbnofix KB330317
©2004 Microsoft Corporation. All rights reserved.