Article ID: 305403
Article Last Modified on 5/14/2007
APPLIES TO
- Microsoft Outlook 2002 Standard Edition
This article was previously published under Q305403
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you open a form in Outlook 2002, you may receive the following error message:
CAUSE
This problem can occur if Outlook 2002 cannot read the local forms cache.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
307841 OFFXP: How to Obtain the Latest Office XP Service Pack
To enable this fix, you need to edit the registry.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To enable this fix:
- Start Registry Editor (Regedt32.exe).
- Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\10.0\Outlook
- On the Edit menu, click Add Value, and then add the following registry value:
Value name: ForceFormReload
Data type: REG_DWORD
Value data: 1
- Quit Registry Editor.
WORKAROUND
To work around this problem, manually clear the forms cache. For additional information about how to manually clear the forms cache, click the article number below to view the article in the Microsoft Knowledge Base:
195754 OL2000: How to Clear the Outlook Forms Cache
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Office XP Service Pack 1.
Keywords: kbbug kberrmsg kbfix kbofficexppresp1fix kbofficexpsp1fix KB305403
