Outlook 2003 importing a .pst EXCELLENT mind stumper! 1

[Internexus]

Okay what I did was I did a File>Import and export> export to a file> personal folder file> selected "Personal Folders + include subfolders> selected a path... > gave it it's own name and put a password on it. Made sure NOT to select "save this password"

So the file exported to my desktop. I immediately burned it to a cd.

Now I want to load it and if I try from the CD-rom it says "you do not have permission" or something to that extent.

Copy it to the desktop and it gives this error "The file C:\blahblahblah\desktop\blah.pst is not a personal folders file"

No matter what I try I can not get this thing to open. Any ideas guys?

 

[joepalm]

I would copy it back to the hard disk and try to import back to outlook from there.

JP

 

[Internexus]

That is exactly the method I am doing it. Any other ideas?

 

[petrosky]

Hi Internexus,

Try changing the read only attribute on the PST file.

Also worth trying the application scanpst.exe.

HTH,

Peter


Remember- It's nice to be important,
but it's important to be nice

 

[Internexus]

It has been unchecked on "read only" the whole time, I have not tried it with it checked. Also tried the scanpst.exe and it gave a similar error saying its not a valid personal folders file.

 

[petrosky]

Hi Internexus,

Yes, I meant to make sure the read only attribute was removed before trying to import.

Did scanpst.exe report any errors?

If you have created a default .pst for you outlook installation have you tried just opening the old PST?

File, Open, Personal Folders File.

Good luck.

Peter


Remember- It's nice to be important,
but it's important to be nice

 

[Internexus]

I recieve the same errors for the scanpst and the file>open>outlood file...

 

[Internexus]

Any other thoughts?

 

[darkrad]

i did exactly what u did, and i have same error as you. Please anybody know how to fix?

 

[Internexus]

Thank god I am not the only one that has created this fine bug

 

[karmic]

Can you just open the pst from outlook?
File - open - personal file folders ?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[Internexus]

Nope, recieve that error.

 

[karmic]

How big is your pst?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[Internexus]

118mb. I've opened larger just for reference.

 

[karmic]

just curious if you were above the 2 gig limit, just a stab in the dark...

You didn't mention if you formatted your system or not, is this a fresh build? are you using the same version of outlook? or one of the earlier versions? What's your operating system?

Have you made sure you have full access to the files? check the security tab and advanced and make sure you have taken ownership and have full security access to the file...

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[Internexus]

It's actually the exact same setup that was on the computer, i just backed up the e-mails, deleted them from the system and that was the ONLY change. I can't restore them since. On my home machine here I don't have any kind of security options to even check out for it but when I get to work tomorrow I will try to see if there is any settings on it. Thats a good though! Thanks

 

[Internexus]

I myself have still not come up with a solution to this issue. Has anyone else?

 

[arthurbr]

Could this be of any help ?

http://support.microsoft.com/?id=832925

 

[Internexus]

Nothing ;(

 

[stussy]

The only thing close I have encountered was this - we had a machine that was logged onto as domain\administrator, and the general info@ourcompany email was picked up from this PC. When we finally gave the machine proper domain logon, I thought I could just import the .pst under the new profile. Not so. Outlook gave me lots of similar messages to those you are getting. In the end I had to give full control permission on that file to the user, despite them being an admin of the PC already.

I know not its exactly the same setup as your machine, but checking the permissions on the file may be a start - maybe the outlook profile was created under a different logon?