Article ID: 889086 - Last Review: October 26, 2006 - Revision: 2.2 You may experience unexpected behavior in a Windows XP-based computer when you try to access public folders on Exchange 2000 Server
Important This article contains information about how to modify the
registry. Make sure to back up the registry before you modify it. Make sure
that you know how to restore the registry if a problem occurs. For more
information about how to back up, restore, and modify the registry, click the
following article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows registry On This PageSYMPTOMSIf you have the Google Desktop search tool loaded on
a Microsoft Windows XP-based computer, you may experience the following symptoms when you
try to access public folders on Microsoft Exchange 2000 Server:
CAUSEThis issue occurs because thousands of folders open in a
short time when you try to access public folders on a Windows XP-based computer that has the Google Desktop search tool loaded. This behavior causes the Exchange 2000 Server
public folders to perform at a slower rate than
expected. Additionally, many users use the Google Desktop and Look tools. Because many users use these tools, the public folder server quickly runs out of resources. This behavior causes the public folder server to stop responding. RESOLUTIONHotfix informationA 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.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, submit a request to 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: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.PrerequisitesBecause of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3).For more information, click the following article number to view the article in the Microsoft Knowledge Base: 301378
(http://support.microsoft.com/kb/301378/
)
How to obtain the latest Exchange 2000 Server service pack
Additionally, this hotfix requires the information
that is in the following Microsoft Knowledge Base article:870540
(http://support.microsoft.com/kb/870540/
)
Availability of the August 2004 Exchange 2000 Server post-Service Pack
3 update rollup
Hotfix file informationThe 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 ------------------------------------------------------- 27-Dec-2004 07:22 6.0.6617.34 2,338,816 Mdbmsg.dll 27-Dec-2004 06:41 6.0.6617.34 4,452,352 Store.exe STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONWarning Serious problems might occur if you modify the registry
incorrectly by using Registry Editor or by using another method. These problems
might require that you reinstall your operating system. Microsoft cannot
guarantee that these problems can be solved. Modify the registry at your own
risk. After you install this hotfix, you must modify the objtFolder registry key to limit the maximum number of users who can open a MAPI session. To do this, follow these steps:
| Article Translations
|
Back to the top
