XFOR: IMC Appears Hung with Improper DN Format

Last reviewed: February 12, 1998
Article ID: Q166540
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0 and 5.0

SYMPTOMS

The Internet Mail Connector (IMC) or Internet Mail Service may stop processing mail and a mail backlog may build in the connector's mailbox in the Information Store (MTS-OUT).

Under the debugger, the connector's threads appear inactive and waiting on a critical section.

CAUSE

An improperly formatted distinguished name (DN) causes the IMC or IMS to overwrite memory and corrupt the heap.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

This is a very isolated case in which a third-party product, Baranof's MailCheck, was set up with a DN that looked like the following:

   /O=ORGNAME=OU=SITENAME

A proper DN should look like /O=ORGNAME/OU=SITENAME. Baranof's software does not check the validity of the DN when entered during the product's setup. As a result, messages sent from MailCheck contain this incorrect DN and caused the IMC to seem to stop responding.

With the fix applied, the IMC or IMS validates the DN before writing it into memory.

MailCheck is manufactured by Baranof's, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.


Additional query words: crash hang
Keywords : kbbug4.00 kbbug5.00 kbfix5.00.sp2 XFOR kbusage
Version : WinNT:4.0,5.0
Platform : winnt
Issue type : kbbug
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.