(1) "Unable to display the folder. Microsoft Office Outlook could not
access the specified folder location. Another application closed
unexpectedly while using your Personal Folders file 'C:\Documents and
Settings\USER\Local Settings\Application Data\Microsoft\Outlook
\Outlook.pst'.
To prevent potential damage to your Personal Folders file, it will not
be available until you close all applications currently using it.
(2) The item cannot be displayed in the Reading Pane. Open the item to
read its contents". When try and open document the error message
"Can't open item" appears.
There is nothing special about the messages which cause the errors.
Most are simple messages with no attachments.
If you exit out of Outlook and start Outlook again, you can normally
read the same messages without any error. Occasionally you need to
delete the OUTLOOK.EXE process using Task Manager.
These errors occur a few times a week for each user. We are using
Outlook in cached mode.
I wonder if anyone has any ideas on what is causing this and how to
stop this happening.
Regards
Kanga
Hi!
There can be a number of reasons. 1. Cache mode 2. There could be
corrupt messages in your mailboxes or check your Information store for
integrity. Dismount the store and do a eseutil /mh on the databsases,
it should come back "Clean Shutdown"....firstly check if you have
enough disk space. Then do a eseutil /r to recover the database and
then a eseutil /p to repair the database. Then run a defrag if it
completes successful, run a full backup.
Cheers!
BossD
Whats is in the pst file?
If not used disconnect Outlook from the pst file and see if the problem
happens again. It could be the antivirus program that does something "funny"
to the file.
Leif
<ian.t...@googlemail.com> wrote in message
news:1180677627.9...@i38g2000prf.googlegroups.com...
No need to repair the database - problem seems to be local to the
workstation.
Leif
<derrick...@gmail.com> wrote in message
news:1180698232.4...@o5g2000hsb.googlegroups.com...
I don't think it is Symantec. I have had the same problem and it
happened after a compulsory restart after a security iupdate from
microsoft. I think they have changed the security settings and not
told anybody