Article ID: 318783 - View products that this article applies to.
This article was previously published under Q318783
This article has been archived. It is offered "as is" and will no longer be updated.
When Exchange 2000 Conferencing Server logs event ID 16387 in the Application event log, the event contains a meeting ID, error code, and message parameters that are not formatted correctly. For example:
Event Type: Error
Event Source: MSExchangeCONF
Event Category: CMS Internal
Event ID: 16387
Time: 4:09:03 AM
Multiple conferences found with the meeting id %3. Error code: %1; Message %2
For more information, click http://search.support.microsoft.com/search/?adv=1.
Data: 0000: 00 00 00 00 b6 03 00 00 0008: d9 d6 40 1a
Occasionally, a delay occurs between the "save" function and "send" function when Exchange 2000 books the meeting. Usually, this delay does not occur because the Conference Management Service (CMS) processes the message after the meeting request has been sent. However, if there is heavy stress on the network or network delays, CMS sees the meeting when the "save" function occurs and then again when the "send" function occurs. This causes CMS to process the meeting again and log the error. This event is not really an error but a warning event, and no duplicate meetings are created.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.