Microsoft KB Archive/322689

From BetaArchive Wiki
Knowledge Base


XCCC: Exchange 2000 Conferencing Web Clients Stop Responding When They Gain Access to the List.asp Page

Article ID: 322689

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Exchange 2000 Conferencing Server Service Pack 1
  • Microsoft Exchange 2000 Conferencing Server Service Pack 2



This article was previously published under Q322689


SYMPTOMS

Exchange 2000 Conferencing Server Web pages may stop responding when a Web client tries to gain access to them. The Exchange 2000 Conferencing processes do not show any CPU utilization in Task Manager. If you try to stop the Exchange 2000 Conferencing services, you may not be able to. The following error messages may be logged in the event log:

Event Type: Error
Event Source: MSExchangeCONF
Event Category: (3)
Event ID: 12288
Date: 4/17/2002
Time: 4:47:55 PM
User: N/A
Computer: COMPUTERNAME
Description:
An exception has occurred which was handled internally. Exception Handler: 0 Code: c0000005 Flags: 0 Address: 77e87b1d

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

Event Type: Error
Event Source: MSExchangeCONF
Event Category: (3)
Event ID: 12288
Date: 5/2/2002
Time: 1:23:52 PM
User: N/A
Computer: COMPUTERNAME
Description:
An exception has occurred which was handled internally. Exception Handler: 0 Code: c0000005 Flags: 0 Address: 41e013

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

CAUSE

The default exception handler handled an access violation and permitted the service to continue running. This problem may occur if the thread that caused the access violation is a thread that must run for the Exchange 2000 Conferencing service (Xconfmgr.exe) to run. If this is such a thread, the service does not allow Web clients to connect and use the Exchange 2000 Conferencing Web pages.

An error occurs while Exchange 2000 Conferencing Server tries to process a meeting request with an exception record. If the meeting is not parsed correctly, an internal exception occurs, and the default error handler is called to log the error to Windows Event Viewer.

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


Component: Conferencing

The English version of this fix 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
   -----------------------------------------------------------
   02-JUL-2002   15:15   6.0.5771.22    57,856   Xwebsched.dll
   02-JUL-2002   14:55   6.0.5771.22   487,936   Xconfmgr.exe
                

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

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Conferencing Server. This problem was first corrected in Microsoft Exchange 2000 Conferencing Server Service Pack 3.

MORE INFORMATION

This fix updates the Exchange 2000 Conferencing service to correctly handle this error condition.

Keywords: kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB322689