This article was previously published under Q329349
This article has been archived. It is offered "as is" and will no longer be updated.
After you install Microsoft Office XP Service Pack 2 (SP-2), Outlook 2002 may stop responding (hang) in module Outlcm.dll when you download a message by using a Post Office Protocol version 3 (POP3) account, and you may receive the following error message:
Microsoft Outlook has encountered a problem and needs to close. We are sorry for the inconvenience.
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.
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:
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. 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.
Version File name ----------------------- 10.0.4510 Outlcm.dll 10.0.4510 Outlook.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The fix for this problem is now available as an update at the following Microsoft Web site: