Microsoft KB Archive/318783

= XCCC: Event ID 16387 Error Message Does Not Format Parameters Correctly =

Article ID: 318783

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Conferencing Server

-



This article was previously published under Q318783



SYMPTOMS
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

Date: 2/18/2002

Time: 4:09:03 AM

User: N/A

Computer: XCH-NWCMS-01

Description:

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



CAUSE
Occasionally, a delay occurs between the &quot;save&quot; function and &quot;send&quot; 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 &quot;save&quot; function occurs and then again when the &quot;send&quot; 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.



RESOLUTION
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:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

The English version of this fix should have the following file attributes or later:

Component: CMS

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.



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

Keywords: kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB318783

-

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

© Microsoft Corporation. All rights reserved.