G
Greg
Recently I reported a problem with a PST file getting
overloaded but not being repaired with the 2GB Truncate
and SCANPST utilities. It was suggested by an MVP that I
further truncate the PST file to below 1.5 Gb. I
truncated the original file down to 1.4 Gb and still got
the error when running SCANPST (halfway through Phase 6 of
8, the scan would quit with the message "An error has
occurred which caused scan to be stopped. No changes have
been made to the scanned file. Fatal Error 80040819). So
then I truncated it down to below 1Gb -- same result. Is
there any way I can perform a forced reindexing on the
truncated PST file with something other than SCANPST,
since that utility doesn't seem to be doing the job?
Thanks
overloaded but not being repaired with the 2GB Truncate
and SCANPST utilities. It was suggested by an MVP that I
further truncate the PST file to below 1.5 Gb. I
truncated the original file down to 1.4 Gb and still got
the error when running SCANPST (halfway through Phase 6 of
8, the scan would quit with the message "An error has
occurred which caused scan to be stopped. No changes have
been made to the scanned file. Fatal Error 80040819). So
then I truncated it down to below 1Gb -- same result. Is
there any way I can perform a forced reindexing on the
truncated PST file with something other than SCANPST,
since that utility doesn't seem to be doing the job?
Thanks