Exported PST issues - New Info

[Jordan]

I have been trying to import an 'exported pst' using the
export function (not copying the pst as I did not know
that should be the way to back them up). I have been
getting the 'not personal folders file' message
regardless of all the help I have been getting from this
newsgroup (thank you all). This includes the repair
tool, using file open, using file import pst, etc... All
into either Outlook 2002 and 2003. I went back through
my years of exported .pst's and found that my oldest
version (the client was probably Office 2002 (XP) or
earlier), which is not much use, did import fine. It
came up and asked me for a password and then imported
them into Outlook 2003 perfectly. Does that help anyone
guess as to why all later exported .pst's are giving me
the message 'not a personal folders file'? They were all
exported using Outlook 2003 (which, like the one that
worked, was attached to an exchange server using offline
cached mode and created a file around 678Meg).

This means so much, I appreciate any help,

Jordan

 

[Roady [MVP]]

And I guess you've also removed the "Read Only" file attribute?

If so I can only think of 2 things;
-bad media; the CD got broken (happens over time)
-you backed up while Outlook was still running.

If you backup the pst-file while Outlook is still running Outlook still
holds a connection. It only drops connections to pst-files (even when you
choose Disconnect) when you close Outlook.

You can use the following tool to find out what can be fixed;
http://officerecovery.com/outlook/index.htm

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Navigation Pane Tips & Tricks
-Create an Office XP CD slipstreamed with Service Pack 3

 

[Jordan]

Robert,

I did remove the read only attribute. I did more tests.
I found a .pst I burned to CD about two months ago and it
worked. I believe that is one of the only ones I created
without compressible encryption. I wonder if that is
part of the problem (or what a solution might be). I am
confident the CDs are in good shape. I did have Outlook
running everytime I performed an export (which I now know
is a bad thing).

Does trigger anything that might help?

Thanks for your time,

Jordan

-----Original Message-----
And I guess you've also removed the "Read Only" file attribute?

If so I can only think of 2 things;
-bad media; the CD got broken (happens over time)
-you backed up while Outlook was still running.

If you backup the pst-file while Outlook is still running Outlook still
holds a connection. It only drops connections to pst- files (even when you
choose Disconnect) when you close Outlook.

You can use the following tool to find out what can be fixed;
http://officerecovery.com/outlook/index.htm

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Navigation Pane Tips & Tricks
-Create an Office XP CD slipstreamed with Service Pack 3

-----

I have been trying to import an 'exported pst' using the
export function (not copying the pst as I did not know
that should be the way to back them up). I have been
getting the 'not personal folders file' message
regardless of all the help I have been getting from this
newsgroup (thank you all). This includes the repair
tool, using file open, using file import pst, etc... All
into either Outlook 2002 and 2003. I went back through
my years of exported .pst's and found that my oldest
version (the client was probably Office 2002 (XP) or
earlier), which is not much use, did import fine. It
came up and asked me for a password and then imported
them into Outlook 2003 perfectly. Does that help anyone
guess as to why all later exported .pst's are giving me
the message 'not a personal folders file'? They were all
exported using Outlook 2003 (which, like the one that
worked, was attached to an exchange server using offline
cached mode and created a file around 678Meg).

This means so much, I appreciate any help,

Jordan

.

 

[Roady [MVP]]

The encryption isn't an issue. Having Outlook open when burning the pst-file
corrupts it beyond repair for the scanpst.exe tool. Use the tool I suggested
in my other post.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Navigation Pane Tips & Tricks
-Create an Office XP CD slipstreamed with Service Pack 3

-----

Robert,

I did remove the read only attribute. I did more tests.
I found a .pst I burned to CD about two months ago and it
worked. I believe that is one of the only ones I created
without compressible encryption. I wonder if that is
part of the problem (or what a solution might be). I am
confident the CDs are in good shape. I did have Outlook
running everytime I performed an export (which I now know
is a bad thing).

Does trigger anything that might help?

Thanks for your time,

Jordan

-----Original Message-----
And I guess you've also removed the "Read Only" file attribute?

If so I can only think of 2 things;
-bad media; the CD got broken (happens over time)
-you backed up while Outlook was still running.

If you backup the pst-file while Outlook is still running Outlook still
holds a connection. It only drops connections to pst- files (even when you
choose Disconnect) when you close Outlook.

You can use the following tool to find out what can be fixed;
http://officerecovery.com/outlook/index.htm

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Navigation Pane Tips & Tricks
-Create an Office XP CD slipstreamed with Service Pack 3

-----

I have been trying to import an 'exported pst' using the
export function (not copying the pst as I did not know
that should be the way to back them up). I have been
getting the 'not personal folders file' message
regardless of all the help I have been getting from this
newsgroup (thank you all). This includes the repair
tool, using file open, using file import pst, etc... All
into either Outlook 2002 and 2003. I went back through
my years of exported .pst's and found that my oldest
version (the client was probably Office 2002 (XP) or
earlier), which is not much use, did import fine. It
came up and asked me for a password and then imported
them into Outlook 2003 perfectly. Does that help anyone
guess as to why all later exported .pst's are giving me
the message 'not a personal folders file'? They were all
exported using Outlook 2003 (which, like the one that
worked, was attached to an exchange server using offline
cached mode and created a file around 678Meg).

This means so much, I appreciate any help,

Jordan

.