G
Guest
What is the deal with "frmcache.dat" and Outlook 2003. Since moving many of
our users from Office XP to Office 2003 (with SP1) we have continuous issue
with the frmcache. Outlook works fine for a while but will eventually starts
to do quirky things like not being able to right click on messages or not
being able to attach messages inside new emails. You can fix the problem by
closing Outlook and deleting the frmcache file. There are various other
symptoms too.
Some things to state up front....
1. When Outlook is "quirky" the frmcache file is always about 10K in size.
When you delete and recreate it it is about 170K. So a small frmcache size
is an indication that we have a problem.
2. We have added the reghack "ForceFormReload" as per KB 839804 and set to
the value of "1" on all the desktops and this does work sometimes. i.e by
closing and opening Outlook the problem goes away for a while about 50% of
the time.
What is the deal with this? I know it is a bigger issue as Google is full
of posts with the same problem. Does MS have a hotfix or one in the works?
Anyone any ideas? We are holding off on purchasing about 150 Office 2003
licenses until we fix this problem.
Thank you
our users from Office XP to Office 2003 (with SP1) we have continuous issue
with the frmcache. Outlook works fine for a while but will eventually starts
to do quirky things like not being able to right click on messages or not
being able to attach messages inside new emails. You can fix the problem by
closing Outlook and deleting the frmcache file. There are various other
symptoms too.
Some things to state up front....
1. When Outlook is "quirky" the frmcache file is always about 10K in size.
When you delete and recreate it it is about 170K. So a small frmcache size
is an indication that we have a problem.
2. We have added the reghack "ForceFormReload" as per KB 839804 and set to
the value of "1" on all the desktops and this does work sometimes. i.e by
closing and opening Outlook the problem goes away for a while about 50% of
the time.
What is the deal with this? I know it is a bigger issue as Google is full
of posts with the same problem. Does MS have a hotfix or one in the works?
Anyone any ideas? We are holding off on purchasing about 150 Office 2003
licenses until we fix this problem.
Thank you