Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XCCC: MAPI Thread That Is Monitoring the New Mail Notification Quits When It Receives a UDP Packet


View products that this article applies to.

This article was previously published under Q329415

↑ Back to the top


Symptoms

The MAPI thread that monitors the new mail notification exits when it receives a User Datagram Protocol (UDP) packet on the termination port, and the program does not receive any notifications thereafter.

↑ Back to the top


Cause

This problem occurs because the new mail thread listens for a termination event on another UDP port. If any packet is received on this UDP port, the new mail notification thread exits, and no more new mail notifications are received. The client must be restarted for the new mail notification to work.

↑ Back to the top


Resolution

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server 5.5 service pack that contains this fix.

To resolve this problem immediately, download the fix by clicking the download link later in this article or contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: 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.
Component: The MDB Messaging Database

The following files are available for download from the Microsoft Download Center:
Release Date: November 18, 2002

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591� How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

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
   ------------------------------------------------------
   01-Nov-2002  14:32  5.5.2656.96  564,496  Emsmdb32.dll

NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

↑ Back to the top


More information

For additional information about this fix on Exchange 2000, click the article number below to view the article in the Microsoft Knowledge Base:
329024� XCCC: MAPI Thread That Is Monitoring the New Mail Notification Quits

↑ Back to the top


Keywords: kbhotfixserver, kbqfe, kbbug, kbexchange550presp5fix, kbfix, KB329415

↑ Back to the top

Article Info
Article ID : 329415
Revision : 7
Created on : 10/26/2006
Published on : 10/26/2006
Exists online : False
Views : 384