J
Jordan
I have been backing up my .PST from Outlook 2003 at my
office to a CD for sometime now so I have tried this on
multiple 'export to a PST' pst files using compressable
encryption and one with no encryption. My office uses
Exchange 2000 and the clients are all Outlook 2003 in
cached mode.
I copy the file from the CD and I change the read-only
attribute and confirm it is off. When I try to import
into my PST files that I exported from the office, I get
a message that says, "The file in (local location) is not
a personal folders file". I get the same message whether
I try to import it, set it as the archive location, try
to use it as a new data file, etc... I have been
searching the web for a while and although I have found
others with the same problem, there has been no solution
posted to any of them. I thought that was what the
export to PST function was for. I have had to import
other PSTs at the office for other users and never
experienced this. It does not seem to provide the same
message as compatibility problems do. Trying to use
scanpst to repair it also results in the identical
message. The file size is less than 700Meg.
Any help is greatly appreciated.
Thanks,
Jordan
office to a CD for sometime now so I have tried this on
multiple 'export to a PST' pst files using compressable
encryption and one with no encryption. My office uses
Exchange 2000 and the clients are all Outlook 2003 in
cached mode.
I copy the file from the CD and I change the read-only
attribute and confirm it is off. When I try to import
into my PST files that I exported from the office, I get
a message that says, "The file in (local location) is not
a personal folders file". I get the same message whether
I try to import it, set it as the archive location, try
to use it as a new data file, etc... I have been
searching the web for a while and although I have found
others with the same problem, there has been no solution
posted to any of them. I thought that was what the
export to PST function was for. I have had to import
other PSTs at the office for other users and never
experienced this. It does not seem to provide the same
message as compatibility problems do. Trying to use
scanpst to repair it also results in the identical
message. The file size is less than 700Meg.
Any help is greatly appreciated.
Thanks,
Jordan