Archiving error on OL 07 says non-unicode, but pst created by OL 0

[Guest]

I get the following archive error under Outlook 2007. I've deleted the
archive and created a new one using OL 07. I still get this error. Note
that the archive is on a file share so that auto-backups occur. I'm not sure
if the "Deleted Items" error is related, but I always get both errors
together. I've used scanpst to clean the archive file, renamed it, created a
new one using OL 07 and then copied the emails from one to the other.
Problem usually returns in 3-4 days.

Error while archiving folder "IPM_SUBTREE" in store "Mailbox - Tony". You
are attempting to archive your data to a Microsoft Outlook 97-2002 Personal
Folders File (.pst) which is a non-Unicode data file. To preserve
multilingual data, you must choose a Unicode data file, such as the Microsoft
Office Outlook Personal Folders File (.pst). See Help for more information.

Error while archiving folder "Deleted Items" in store "Current Archive".
Problems with the destination store M:\TONY\Outlook Archives\2007 Archive.pst.

 

[Guest]

It looks like you have encountered the Old format vs the new format issue.
Run a serach for "convert PST" in the Outlook section and you will find
several suggestion for converting from the old format (see my war story at
http://www.microsoft.com/office/com...n-us&mid=9309a22c-dd7a-4a46-aa40-62fcc51c7abe).
For whatever reason MS does not automatically (to my knowledge) convert the
file from the old ANSI format to the new Unicode format.

I've managed to convert the mail portion of my PST file but I'm still trying
to learn what I need to do to convert the calendar, task list, notes and
other non-email files. Also beaware that if you use the method I did you will
also have a manual effort to update all of the filters you setup. The whole
process took me about 6 hours much of that was learning what to do, and a big
chunk was updating my filters.

 

[DL]

Could it be that storing a pst over a network isnt supported by MS as it can
lead to corruption.
Have you tried creating a local Archive and seeing how that performs?
Just a thought

 

[Guest]

The archive file was created with OL-07 - so I don't think a convert should
be necessary. But since this is MS, I tried a convert both before and after
a scanpst run. Since this has been going on since December, I've tried many
different ways. Last was to create a new archive and import all the files
from the replaced archive. That didn't work either.

 

[Guest]

That's actually a thought - but it doesn't make logical sense. Shouldn't an
archive be on a file share which routinely gets backed up? We have a large
network with a corp. policy requuiring company critical files - archived
email from customers - to be on a server rather than on the local
workstation. Since I also use the archive continuously - we have a 2 weeks
old go to archive and a max size on the mailbox - it's always open. Archive
doesn't run when OL is not up, so I leave it up to run the nightly archives.
If I use the pst backup option, I have to shut down the email every night -
but the archive then has to run during the day. If I have the archive files
on a local drive, I can't back them up or copy them because they are in use.
Round and round . . .

I did have the archives locally for a few days once before, and had
problems. But I'm not sure what order things were in vis-a-vis conversions
and scanpst at the time I tried it.

Bottom line - I'll try this again but I would prefer a better solution.
Remember the archive files were created by OL07.

 

[DL]

I was merely pointing out that MS doesn't support the use of a pst file over
a network as it can lead to corruption of the pst
I assume MS designed pst files for use on local PC's whilst ost & exchange
was designed for network use.
Whether the pst is an archive is immaterial.