XCCC: Event ID 8196 and 8197 Messages Are Logged When You Connect to a Video Conference (244635)


The information in this article applies to:

  • Microsoft Exchange 2000 Conferencing Server
This article was previously published under Q244635
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 you connect to an online video conference, the following events may be logged in the Microsoft Windows 2000 Application event log:

Type: Error
Sources: MSExchangeIPConf
Event ID: 8196
Description: The Microsoft Exchange IP Multicast Conferencing service could not find any multicast address allocation (MADCAP) servers configured with multicast scope(s) specified by the Exchange Video Conferencing resource conference resource object. Please correct this problem immediately.

Type: Error
Sources: MSExchangeIPConf
Event ID: 8197
Description: The Microsoft Exchange IP Multicast Conferencing service found an Exchange Video Conference resource conference resource object that has no multicast scopes associated with it. Please correct this problem immediately.

CAUSE

When you create an online video conference in Microsoft Outlook, a multicast address for the conference may be allocated by a Multicast Address Client Allocation Protocol (MADCAP) server. The events that are described in the "Symptoms" section can occur for any of the following reasons:
  • A MADCAP server cannot be contacted.
  • A configured multicast scope is not defined or is incorrect.
  • The MADCAP server is not authorized in Active Directory.

RESOLUTION

To resolve this issue, verify that the following conditions are true:
  • The Dynamic Host Configuration Protocol (DHCP) service is installed and running.
  • A multicast scope is defined and configured correctly.
  • The DHCP/MADCAP server is authorized for use in Active Directory.
For information about how to configure DHCP and multicasting, see Windows 2000 Server Online Help.

MORE 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.

  1. Start Registry Editor (Regedt32.exe).
  2. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

  3. On the Edit menu, click Add Key, and then add the following key:

    Key Name: Conferencing
    Class: Leave blank

  4. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Conferencing

  5. On the Edit menu, click Add Key, and then add the following key:

    Key Name: Parameters
    Class: Leave blank

  6. Click the newly-created Parameters key, click Add Value on the Edit menu, and then add the following values:
    • Value Name: No Random Mcast Address
      Data Type: REG_DWORD
      Data: 0
    • Value Name: Random Mcast Address Count
      Data Type: REG_DWORD
      Data: The amount of addresses that are needed, for example, 400
    • Value Name: Random Mcast Address Start
      Data Type: REG_SZ
      String: start of multicast address scope
  7. Quit Registry Editor.
NOTE: A valid Class D multicast range is defined as 224.0.0.1 - 239.255.255.255
Modification Type:MinorLast Reviewed:4/25/2005
Keywords:kbbug kberrmsg kbfix kbprb KB244635
©2004 Microsoft Corporation. All rights reserved.