Office XP Corrupting PST's

[news.microsoft.com]

I am having a problem with Outlook XP corrupting PST created with Outlook
2000. I have applied service pack three to the computers to see if this
would rectify the problem. The pst's are ranging in sizes from 5 meg to 1
gig. This is not happening to all of my computers, just random ones.

The Machines are running on Windows 2000 sp4.

 

[Brian Tillman]

I am having a problem with Outlook XP corrupting PST created with
Outlook 2000. I have applied service pack three to the computers to
see if this would rectify the problem. The pst's are ranging in sizes
from 5 meg to 1 gig. This is not happening to all of my computers,
just random ones.

Outlook 2002 and 2000 use exactly the same format PST files, so you cannot
corrupt an OL 2000 PST simply by using it in OL 2002. What exactly are you
doing when you notice the corruption?

 

[Kurt Johnson]

All my Users are doing is trying to open up their archive folders with
Outlook 2002. And it is not everyone that is having the problem, it seems to
be totally random on multple computers. I have ran the scanpst.exe in
Outlook2002 and in Outlook2000 to attempt to fix the problem.
The exact error message we are getting is : Unable to expand the folder. the
set of folders could not be opened. An error occured that prevented the file
\\server name\folder\person's name\personal.pst from being saved. Close and
then restart all mail enabled applications.

At first I thought it might be security issues, but that is not the case
since it is even happening on local machines.

Kurt Johnson

 

[Brian Tillman]

The exact error message we are getting is : Unable to expand the
folder. the set of folders could not be opened. An error occured that
prevented the file \\server name\folder\person's name\personal.pst
from being saved. Close and then restart all mail enabled
applications.

While I don't claim it is the reason, the ablve message indicates that your
PSTs are on a network share, which is completely unsupported and, according
to Microsoft, prone to problems. Try moving your archive to a local disk
and see if this affects the behavior.

 

[Kurt Johnson]

Since you missed it the first time It is also happening on local machines.