Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 1 (SP1).
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
836993�
How to obtain the latest service packs for Exchange Server 2003
Restart requirement
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) 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
--------------------------------------------------------------
29-Oct-2004 01:06 6.5.7232.48 3,261,952 Mdbmsg.dll
08-Oct-2004 02:12 3,304 Redir.asp
29-Oct-2004 01:40 6.5.7232.48 5,144,064 Store.exe
Hotfix installation information
After you install this hotfix, four new events are logged to notify you if both of the following behaviors occur:
- DACL enumeration takes longer than expected. By default, this event is logged if DACL enumeration takes 20 seconds or longer.
- The publication of public folder notification messages takes longer than expected. By default, this event is logged if notification publication takes 60 seconds or longer.
In this scenario, one or more of the following events are logged:
Event ID 1236Event Source: MSExchangeIS
Event Category: General
Event ID: 1236
Event Type: Warning
Description: Publication of a notification notification to n subscribers (n estimated) of folder folderName in database "DatabaseName" succeeded, but took an abnormally long time (Number of seconds) to complete. This latency may be indicative of the notified folder or its parent having too many child folders with differing access rights. It may also be indicative of performance problems with your hardware.
Event ID 1237Event Source: MSExchangeIS
Event Category: General
Event ID: 1237
Event Type: Error
Description: Publication of a notification notification to n subscribers (n estimated) of folder folderName in database "databaseName" failed with error errorCode, and took an abnormally long time (NumberOf seconds) to do so. This latency may be indicative of the notified folder or its parent having too many child folders with differing access rights. It may also be indicative of performance problems with your hardware.
Event ID 1238Event Source: MSExchangeIS
Event Category: General
Event ID: 1238
Event Type: Warning
Description: Enumeration of numberOf entries for the ACL of folder folderName in database "databaseName" succeeded, but took an abnormally long time (numberOf seconds) to complete. This latency may be indicative of the folder having too many child folders with differing access rights. It may also be indicative of performance problems with your hardware.
Event ID 1239Event Source: MSExchangeIS
Event Category: General
Event ID: 1238
Event Type: Error
Description: Enumeration of numberOf entries for the ACL of folder folderName in database "databaseName" failed with error %5, and took an abnormally long time (numberOf seconds) to do so. This latency may be indicative of the folder having too many child folders with differing access rights. It may also be indicative of performance problems with your hardware.
You can control the default times that these events are triggered in by modifying the following registry subkeys:
- To change the DACL enumeration threshold, modify the value in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Value name: Abnormal OFLIST Enumerate Latency Threshold
Value type: REG_DWORD
Value data: 20000 (default)
- To change the public folder notification message publication threshold, modify the value in the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Value name: Abnormal Publish Latency Threshold
Value type: REG_DWORD
Value data: 60000 (default)
These registry values must be specified in milliseconds.� If both of these registry subkeys do not exist, or if the value is 0 (zero) or is a negative value, the default value is used.