Microsoft KB Archive/824290

= Error Message: The videoconference was not started because none of the available multicast address allocation (MADCAP) servers can issue a multicast address =

Article ID: 824290

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange 2000 Conferencing Server

-





SYMPTOMS
When you try to join a video conference that has been scheduled on Microsoft Exchange 2000 Conferencing Server, you receive the following error message:

The videoconference was not started because none of the available multicast address allocation (MADCAP) servers can issue a multicast address. Contact your system administrator for assistance.



CAUSE
This problem may occur when Exchange 2000 Conferencing Server obtains an IP address from a Multicast Address Dynamic Client Allocation Protocol (MADCAP) server. When Exchange 2000 Server obtains an IP address from the MADCAP server, the Exchange 2000 Conferencing Server computer makes sure that the IP address is not already in use by any existing conferences. If the first address that the MADCAP server provides is already in use by Exchange 2000 Conferencing Server, Exchange 2000 Conferencing Server requests another IP address. When a unique IP address is found, Exchange 2000 Conferencing Server runs a cleanup routine to release the unwanted IP addresses. During the cleanup routine, Exchange 2000 Conferencing Server also releases the good IP address.

If the first IP address that Exchange 2000 Conferencing Server obtains is not in use by any conferences, the problem does not occur.



RESOLUTION
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 2000 Server 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.

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 -- 08-Oct-2003 03:37  6.0.6518.0        217,088  Xipconf.dll Note Because of file dependencies, this update requires 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



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

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB824290

-

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

© Microsoft Corporation. All rights reserved.