XCON: A Recipient Address That Is Longer Than 1,024 Characters Causes IIS to Stop Responding (317280)


The information in this article applies to:

  • Microsoft Exchange 2000 Enterprise Server, when used with:
    • the operating system: Microsoft Windows 2000
This article was previously published under Q317280

SYMPTOMS

If a message contains a recipient address that is longer than 1,024 characters, Inetinfo.exe, the process for Internet Information Services (IIS), may stop responding when Inetinfo.exe processes the message. The Dr. Watson dump file shows the module at the top of the stack as Mailmsg.dll.

This problem may occur when you mount an information store that contains the message that contains a recipient address that is longer than 1,024 characters. Because IIS stops responding, the Simple Mail Transfer Protocol (SMTP) queues stop and do not process new messages until you apply the fix that is described in this article, or until you remove the message.

CAUSE

Inetinfo.exe stops responding in Mailmsg.dll. However, this problem occurs because of a problem in the heap allocation of Staxmem.dll.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

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
   ---------------------------------------------------------
   05-FEB-2002   17:01   5.0.2195.4888   8,464   Staxmem.dll
   30-MAY-2001   12:03   5.0.2195.3649   3,584   Spmsg.dll

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows 2000 Server. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type:MinorLast Reviewed:10/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbSysAdmin kbWin2000PreSP3Fix kbWin2000sp3fix KB317280
©2004 Microsoft Corporation. All rights reserved.