Data file not closed properly??

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

Everytime our users have Outlook open then close it
(properly), but need to get back into it immediately, they
receive this message.

"The date file 'personal folder' was not closed properly."
"This file is being checked for problems"

This message started appearing about a week ago. I can't
find any information about it or what's the real cause.
Is it because of SP3 for Office? Does anyone have a clue??

Please help...
 
My Outlook 2000 sometimes has a problem when I close with the close window
button [X] in the top right, but does not seem to when I use File menu then
Exit.




Everytime our users have Outlook open then close it
(properly), but need to get back into it immediately, they
receive this message.

"The date file 'personal folder' was not closed properly."
"This file is being checked for problems"

This message started appearing about a week ago. I can't
find any information about it or what's the real cause.
Is it because of SP3 for Office? Does anyone have a clue??

Please help...
 
Mike said:
Everytime our users have Outlook open then close it
(properly), but need to get back into it immediately, they
receive this message.

"The date file 'personal folder' was not closed properly."
"This file is being checked for problems"

This message started appearing about a week ago. I can't
find any information about it or what's the real cause.
Is it because of SP3 for Office? Does anyone have a clue??

Please help...

I reported the same problem in a followup in another thread.

It started happenning with SP3 to me. What I can gather is that for
large PST files (1 gig+), if outlook is closed by shutting down
windows, Outlook isn't given enough time to close the PST files
properly. The next time you open windows, it gives the "not closed
properly" message. A workaround is to close outlook first, wait some
time, then shut down your system.

I have Win2k, Office2002, and multiple 1.5gig pst files.

Again, this appears to be an SP3 bug, not sure who/how to report this
to MS.

-MVL
 
Back
Top