Article ID: 328486
Article Last Modified on 2/21/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q328486
SYMPTOMS
You are using a domain that has the following servers:
- A Microsoft Windows 2000-based domain controller (DC1)
- An Exchange 2000 Service Pack 3 (SP3)-based server running on a Windows 2000-based member server
- An Exchange 2000 SP3-based expansion server running on a Windows 2000-based member server
If you send a message to a distribution list (DL), the message is not delivered and you do not receive a non-delivery report (NDR). When you track this message, you see that the message does not progress beyond the categorizer on the expansion server.
If you set the Diagnostics Logging level to 7 on the categorizer on the expansion server, the following event ID message is logged for each user who this message is not delivered to:
Event Type: Information
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 9000
Date: 31/07/2002
Time: 10:28:13
User: N/A
Computer: Servername
Description:
The function 'CPhatCat::ExpandRecipient' failed for reason 'The Message has too many recipients to deliver.
' when processing the recipient 'ParUser01@lwe2k.net' of type 'smtp'. A DSN has been generated.
Data:
0000: da 02 04 c0 U..A
CAUSE
This problem occurs if the default value of the msExchRecipLimit attribute in the Global Settings object is used instead of the value of the msExchRecipLimit attribute in originator object after the first hop to the expansion server.
RESOLUTION
Cumulative rollup information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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: MSExchangeTransport
The English version of this hotfix 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
--------------------------------------------------
Sep-26-2002 13:47:06 6.0.6332.0 372KB Phatcat.dll
Note Because of file dependencies, this update requires Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
WORKAROUND
To work around this problem, use any of the following methods:
- Increase the Recipient limit to a value that is greater than the total number of users. To do so:
- Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
- Double-click Global Settings.
- Right-click Message Delivery, and then click Properties.
- On the Defaults tab, set the Recipient limit to an appropriate value.
- Click to clear the Do not send delivery reports check box.
- Set the expansion server to Any. If you do so, DLs are expanded on the originator's server and the message is delivered successfully.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Additional query words: 191803 kbExchange2000preSP4marchbarFix
Keywords: kbhotfixserver kbqfe kbqfe kbbug kbexchange2000presp4fix kbfix KB328486
