Microsoft has released the Outlook 2003 post-Service Pack 1 hotfix package for Microsoft Office Outlook 2003. This article describes the following items about the hotfix package:
- Issues that the hotfix package fixes
- Prerequisites for installing the hotfix package
- Whether you must restart your computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes to use one or more of the hotfixes in the package
- The files that the hotfix package contains
This article describes the Microsoft Office Outlook 2003 issues that are fixed in the Outlook 2003 post-Service Pack 1 hotfix package that is dated February 26, 2005.
Issues that the hotfix package fixes
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
- Consider the following scenario. In Outlook 2003, you point to New on the File menu, click Choose Form, and then view a folder by using Category Tree view. You change the view to Category Tree view by clicking the rightmost icon in the upper-right corner of the Choose Form dialog box. When you do this, some forms may be listed under the wrong categories and subcategories.
This issue occurs when the initial view for the Choose Form dialog box is Category Tree view.
To work around this issue, you can change the view for the Choose Form dialog box to List view, open a different folder, and then reopen the original folder that you had viewed. Then, change the view back to Category Tree view. Now the forms will be listed under the appropriate categories and subcategories.
- Consider the following scenario. Your network administrator applies a Group Policy object that enables
the Encoding for outgoing messages policy. After the Group Policy
object is applied, a message encoding type that you previously selected
may be missing from the list of encoding types in the Preferred
encoding for outgoing messages list in Outlook 2003.
Note This issue may occur if
you repeatedly change the encoding type for your outgoing e-mail
- Consider the following scenario. In Outlook 2003, you want to send a message to a distribution list. You select a distribution list to add to the To box by clicking To and then selecting the name of the distribution list from the global address list. When you do this, the display name of the distribution list does not appear in the To box. However, when you click Send, the message is still sent to the members of the distribution list.
If the distribution list name is configured to use a double-byte character set (DBCS) font, members of the distribution list do not see the display name of the distribution list in the From box when they receive the message. Instead, the display name of the distribution list appears to recipients as a random collection of characters. This issue occurs because the distribution list name is not correctly decoded into the appropriate DBCS characters when a recipient views the message by using Outlook 2003.
This issue occurs if the following conditions are true:
- There is a POP3 server and an Exchange Server computer that is configured for the same user profile.
- The POP3 server is set as the primary e-mail server for the user profile.
Note This issue occurs only when you select the name of a distribution list from the global address list to add to the To box. This issue does not occur if you type the display name of the distribution list or the alias of the distribution list in the To box.
Service pack information
This problem was first corrected in Office 2003 Service Pack 2.
To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Office 2003
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.
The following list contains prerequisites for the hotfix package:
- The optimized version of this hotfix is a post-Office 2003 Service Pack 1 (SP1) hotfix. To install the hotfix, you must have Office 2003 SP1 installed.
For additional information about Office 2003 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
Description of Office 2003 Service Pack 1
- The full-file version of this hotfix is also the administrative version of this hotfix. You can install this version of the hotfix on a computer that is running Office 2003 with Office 2003 SP1 installed or on a computer that is running Office 2003 without Office 2003 SP1 installed. However, we have tested this hotfix more extensively on a computer that is running Office 2003 with Office 2003 SP1 installed than we have on a computer that is running Office 2003 without Office 2003 SP1 installed. If you install this hotfix on a computer that is running Office 2003 without Office 2003 SP1 installed, some file conflicts might occur. We support this configuration, but we do not recommend this configuration.
You do not have to restart your computer after you install this hotfix.
Hotfix replacement information
This hotfix is not replaced by any later hotfix.
You do not have to create or to modify any registry keys to enable any hotfixes that this package contains.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The global 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
26-Feb-2005 07:33 5.0.2919.6304 5,593,632 Office2003-kb894539-glb.exe
Microsoft Windows Installer .msp file information
Date Time Size File name
26-Feb-2005 05:04 9,196,032 Outlookff.msp (full-file/administrative)
26-Feb-2005 00:02 3,910,656 Outlookop.msp (optimized)
After the hotfix is installed, the global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table.
Date Time Version Size File name
18-Feb-2005 00:59 11.0.6423.0 88,264 Addrpars.dll
11-Sep-2004 02:17 11.0.6404.0 77,000 Dlgsetp.dll
27-Aug-2004 00:48 11.0.6402.0 132,296 Envelope.dll
29-Jan-2005 00:08 11.0.6420.0 346,312 Exsec32.dll
27-Aug-2004 00:48 11.0.6402.0 122,056 Impmail.dll
18-Feb-2005 02:16 11.0.6423.0 158,912 Oladd.fae
18-Feb-2005 02:16 11.0.6423.0 152,264 Olappt.fae
27-Aug-2004 00:57 11.0.6402.0 117,952 Oljrnl.fae
27-Aug-2004 00:57 11.0.6402.0 113,344 Olmail.fae
27-Aug-2004 00:57 11.0.6402.0 104,640 Olnote.fae
18-Feb-2005 02:16 11.0.6423.0 147,144 Oltask.fae
24-Feb-2005 21:34 11.0.6424.0 7,579,848 Outllib.dll
24-Feb-2005 21:32 11.0.6424.0 89,288 Outlmime.dll
28-Apr-2004 06:10 11.0.6353.0 196,296 Outlook.exe
24-Feb-2005 21:32 11.0.6424.0 141,000 Outlph.dll
27-Aug-2004 00:47 11.0.6402.0 44,744 Outlvbs.dll
11-Mar-2004 22:01 11.0.6254.0 74,936 Rm.dll
22-Jan-2005 03:20 11.0.6419.0 111,808 Sc2.sam
22-Jan-2005 03:20 11.0.6419.0 143,048 Schplus.sam
11-Oct-2004 19:29 11.0.6408.0 100,552 Transmgr.dll
- For additional information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
- For additional information about the differences between the two .msp files, see the "Strategies for updating Office 2003 installations" topic. To see this topic, visit the following Microsoft Web site:
For additional information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 894539 - Last Review: January 16, 2015 - Revision: 5.0
- Microsoft Office Outlook 2003
- Microsoft Office Outlook 2003 with Business Contact Manager
|kbnosurvey kbarchive kbautohotfix kbqfe kbhotfixserver kboffice2003sp2fix kbfix kbhotfixrollup kboffice2003presp2fix KB894539|