unicode pst not valid in import/export

[EMERY_BILL]

found out that even though ol2003 creates the new and improved unicode
pst files, that the import / export utility stops at 4 gb.
way to go m$, nice job.
doing a lot of copying and pasting here in the "enterprise"

 

[DL]

Import/Export why, what for? - use copy
If you have a 4gb problem it is unlikely to be anything to do with OL

 

[Russ Valentine [MVP-Outlook]]

Old news. Just add it to the list of why exporting has never been the
correct way to transfer Outlook data. Were you not paying attention to our
admonitions? MVP's and experienced users have been documenting this for
years. Perhaps were you expecting Microsoft to document its shortcomings for
you. In case you hadn't noticed, they don't do that very well.

 

[EMERY_BILL]

i know that there isnt a 4gb limit anymore on pst files, you know that
and so does microsoft, and even outlook itself knows that as it will
continue to add items to a unicode pst file forever. the problem is
that the programs like exmerge, import/export, even copy and paste dont
know that.
i had to create multiple pst files and copy and paste parts of the
user's mailbox to it.
took a while.
btw, dont assume that the cached exchange mode program knows that
either because it doesnt. if you dont turn on cached exchange mode,
your imports of pst files will not show up on the server.
oh well, im sure that this will get better with ol2007 if anyone has a
machine with enough power to run it.
cheers

Old news. Just add it to the list of why exporting has never been the
correct way to transfer Outlook data. Were you not paying attention to our
admonitions? MVP's and experienced users have been documenting this for
years. Perhaps were you expecting Microsoft to document its shortcomings for
you. In case you hadn't noticed, they don't do that very well.
--
Russ Valentine
[MVP-Outlook]

found out that even though ol2003 creates the new and improved unicode
pst files, that the import / export utility stops at 4 gb.
way to go m$, nice job.
doing a lot of copying and pasting here in the "enterprise"

 

[EMERY_BILL]

im replying to myself on this because im so mad that im about to use a
ol2003 disk for a frisbie.
the ol devolpment team at microsoft is lucky that i dont work there
because if i did and if a program was released that supposedly
supported pst files greater than 4gb and any part of that program, let
me repeat, any part didnt, they would be fired retroactively. fired
retroactively means that they would owe me money.
you call it not announcing shortcomings, i call it a lie.

 

[Russ Valentine [MVP-Outlook]]

This is still end user error. Why must you insist on using export when it is
so clearly the wrong way to transfer Outlook data?
--
Russ Valentine
[MVP-Outlook]

i know that there isnt a 4gb limit anymore on pst files, you know that
and so does microsoft, and even outlook itself knows that as it will
continue to add items to a unicode pst file forever. the problem is
that the programs like exmerge, import/export, even copy and paste dont
know that.
i had to create multiple pst files and copy and paste parts of the
user's mailbox to it.
took a while.
btw, dont assume that the cached exchange mode program knows that
either because it doesnt. if you dont turn on cached exchange mode,
your imports of pst files will not show up on the server.
oh well, im sure that this will get better with ol2007 if anyone has a
machine with enough power to run it.
cheers

Old news. Just add it to the list of why exporting has never been the
correct way to transfer Outlook data. Were you not paying attention to
our
admonitions? MVP's and experienced users have been documenting this for
years. Perhaps were you expecting Microsoft to document its shortcomings
for
you. In case you hadn't noticed, they don't do that very well.
--
Russ Valentine
[MVP-Outlook]

found out that even though ol2003 creates the new and improved unicode
pst files, that the import / export utility stops at 4 gb.
way to go m$, nice job.
doing a lot of copying and pasting here in the "enterprise"

 

[Lanwench [MVP - Exchange]]

In

im replying to myself on this because im so mad that im about to use a
ol2003 disk for a frisbie.
the ol devolpment team at microsoft is lucky that i dont work there
because if i did and if a program was released that supposedly
supported pst files greater than 4gb and any part of that program, let
me repeat, any part didnt, they would be fired retroactively. fired
retroactively means that they would owe me money.
you call it not announcing shortcomings, i call it a lie.

Dude, chill out. Outlook is not the problem here (perhaps you are trying to
export this to a FAT32-formatted disk/partition?). And frankly, if you're
using Exchange, you shouldn't be using PST files anyway.

I echo Russ and the others who write that doing an export or import for this
purpose is not the correct procedure. If you buy a toaster oven, and try to
make strawberry/banana smoothies in it, you will definitely have some
problems, but don't blame General Electric for them.

 

[Brian Tillman]

found out that even though ol2003 creates the new and improved unicode
pst files, that the import / export utility stops at 4 gb.
way to go m$, nice job.
doing a lot of copying and pasting here in the "enterprise"

Sounds like you have a FAT32-formatted disk. Only NTFS goes beyond 4 GB per
file.

 

[EMERY_BILL]

ok, try and run exmerge on a mailbox that is greater than 4 gb. guess
what, it doesnt matter if the formatted volumre is ntfs or not. and if
pst files and import/export isnt the way to do it they why is it on the
menu and in countless articles in microsoft's knowlege base ? why is
there an exmerge program ?
the "correct procedure" is to have development teams that write
programs that work. and that means all features of the released
program. not just parts of it.
even the "cached exchange mode" of the new outlook fails if you try and
import more than 4gb at a time with no error messages . it just sits
there with all your stuff only on the workstation and not syncing with
the server. ie it cant sync more than 4gb even if the data is in
multiple folders !!
time to get back to basics, write some programs in assembler and then
get back to me . in the mean time
dont tell me that something works and then let me spend hours and hours
figuring out that it doesnt.

 

[Lanwench [MVP - Exchange]]

In

ok, try and run exmerge on a mailbox that is greater than 4 gb. guess
what, it doesnt matter if the formatted volumre is ntfs or not.

You weren't talking about Exmerge in your first post, were you? You never
mentioned it.

However, regarding Exmerge, http://support.microsoft.com/?kbid=916085 states
quite clearly:

"...this problem occurs because the ExMerge tool does not support Unicode
..pst files. Unicode is the default .pst file format in Outlook 2003. This
allows for a .pst file size of 20 GB. If you export data from Outlook 2003
by using the ExMerge tool, ExMerge exports the data in American National
Standards Institute (ANSI) format. This format allows for a .pst file that
is less than 2 GB."

So, 4GB isn't even an issue here.

and if
pst files and import/export isnt the way to do it they why is it on
the menu

Because there are times when it is useful. For example, if you wanted to get
a subset of your data out of your PST file or mailbox, into another PST
file.

and in countless articles in microsoft's knowlege base ? why
is there an exmerge program ?

Again, you weren't posting about Exmerge, or even Exchange, were you? You
were talking about Outlook. If you are having problems with Exmerge, you
should post in an Exchange group, as Exmerge is not part of Outlook.

the "correct procedure" is to have development teams that write
programs that work. and that means all features of the released
program. not just parts of it.

Many, if not most, people happily run Outlook/Exchange with no problems such
as you are experiencing.

even the "cached exchange mode" of the new outlook fails if you try
and import more than 4gb at a time with no error messages .

Why are you importing? Again, this is not the way to do it, as you have
already been told.

it just
sits there with all your stuff only on the workstation and not
syncing with the server. ie it cant sync more than 4gb even if the
data is in multiple folders !!

Don't import. If you want to get data from a PST file to a mailbox, and it's
larger than Exmerge can handle, *open* the PST file in the same profile as
the mailbox, and select the data you want, and copy it to the appropriate
mailbox folders.

time to get back to basics, write some programs in assembler and then
get back to me .

Sure, I'll get right on that!

in the mean time
dont tell me that something works and then let me spend hours and
hours figuring out that it doesnt.

If you'd done some basic research on either Outlook's import/export, or
Exmerge, you would not be here asking the questions you are now. If you are
responsible for supporting enterprise-level products such as Exchange, it's
your responsibility to learn how to use them properly.

If you have a question and want help with it, from strangers in a newsgroup,
for free, I suggest you learn how to post the questions such that you get
the assistance you desire. Ranting will not aid you in this pursuit,
although it may provide you with momentary pleasure.

 

[EMERY_BILL]

yes there should be a correction, exmerge doesnt support files greater
that 2 gb. not 4
and it's the overall sa size limits on several things that is truly
irritating. i dont remember asking anyone for any help , especially not
from you.
the reason we had to use import/export of pst files to migrate exchange
to a new box is because we couldnt get the migration to work any other
way. just ran out of time on it. looking up error messages all night
isnt fun
but it's pretty common when dealing with exchange

 

[Milly Staples [MVP - Outlook]]

Hmm, I did an Exchange migration in an afternoon with only one error - seems like the problem is pebkac?

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, (e-mail address removed) asked:

| yes there should be a correction, exmerge doesnt support files greater
| that 2 gb. not 4
| and it's the overall sa size limits on several things that is truly
| irritating. i dont remember asking anyone for any help , especially
| not from you.
| the reason we had to use import/export of pst files to migrate
| exchange to a new box is because we couldnt get the migration to work
| any other way. just ran out of time on it. looking up error messages
| all night isnt fun
| but it's pretty common when dealing with exchange
|
|
|
| Lanwench [MVP - Exchange] wrote:
|| In || (e-mail address removed) <[email protected]> typed:
||| ok, try and run exmerge on a mailbox that is greater than 4 gb.
||| guess what, it doesnt matter if the formatted volumre is ntfs or
||| not.
||
|| You weren't talking about Exmerge in your first post, were you? You
|| never mentioned it.
||
|| However, regarding Exmerge,
|| http://support.microsoft.com/?kbid=916085 states quite clearly:
||
|| "...this problem occurs because the ExMerge tool does not support
|| Unicode .pst files. Unicode is the default .pst file format in
|| Outlook 2003. This allows for a .pst file size of 20 GB. If you
|| export data from Outlook 2003 by using the ExMerge tool, ExMerge
|| exports the data in American National Standards Institute (ANSI)
|| format. This format allows for a .pst file that is less than 2 GB."
||
|| So, 4GB isn't even an issue here.
||
||| and if
||| pst files and import/export isnt the way to do it they why is it on
||| the menu
||
|| Because there are times when it is useful. For example, if you
|| wanted to get a subset of your data out of your PST file or mailbox,
|| into another PST file.
||
||| and in countless articles in microsoft's knowlege base ? why
||| is there an exmerge program ?
||
|| Again, you weren't posting about Exmerge, or even Exchange, were
|| you? You were talking about Outlook. If you are having problems with
|| Exmerge, you should post in an Exchange group, as Exmerge is not
|| part of Outlook.
||
||| the "correct procedure" is to have development teams that write
||| programs that work. and that means all features of the released
||| program. not just parts of it.
||
|| Many, if not most, people happily run Outlook/Exchange with no
|| problems such as you are experiencing.
||
||| even the "cached exchange mode" of the new outlook fails if you try
||| and import more than 4gb at a time with no error messages .
||
|| Why are you importing? Again, this is not the way to do it, as you
|| have already been told.
||
||| it just
||| sits there with all your stuff only on the workstation and not
||| syncing with the server. ie it cant sync more than 4gb even if the
||| data is in multiple folders !!
||
|| Don't import. If you want to get data from a PST file to a mailbox,
|| and it's larger than Exmerge can handle, *open* the PST file in the
|| same profile as the mailbox, and select the data you want, and copy
|| it to the appropriate mailbox folders.
||
||| time to get back to basics, write some programs in assembler and
||| then get back to me .
||
|| Sure, I'll get right on that!
||
||| in the mean time
||| dont tell me that something works and then let me spend hours and
||| hours figuring out that it doesnt.
||
|| If you'd done some basic research on either Outlook's import/export,
|| or Exmerge, you would not be here asking the questions you are now.
|| If you are responsible for supporting enterprise-level products such
|| as Exchange, it's your responsibility to learn how to use them
|| properly.
||
|| If you have a question and want help with it, from strangers in a
|| newsgroup, for free, I suggest you learn how to post the questions
|| such that you get the assistance you desire. Ranting will not aid
|| you in this pursuit, although it may provide you with momentary
|| pleasure.
||
||
|||
|||
|||
||| Lanwench [MVP - Exchange] wrote:
|||| In |||| (e-mail address removed) <[email protected]> typed:
||||| im replying to myself on this because im so mad that im about to
||||| use a ol2003 disk for a frisbie.
||||| the ol devolpment team at microsoft is lucky that i dont work
||||| there because if i did and if a program was released that
||||| supposedly supported pst files greater than 4gb and any part of
||||| that program, let me repeat, any part didnt, they would be fired
||||| retroactively. fired retroactively means that they would owe me
||||| money.
||||| you call it not announcing shortcomings, i call it a lie.
||||
|||| Dude, chill out. Outlook is not the problem here (perhaps you are
|||| trying to export this to a FAT32-formatted disk/partition?). And
|||| frankly, if you're using Exchange, you shouldn't be using PST files
|||| anyway.
||||
|||| I echo Russ and the others who write that doing an export or import
|||| for this purpose is not the correct procedure. If you buy a toaster
|||| oven, and try to make strawberry/banana smoothies in it, you will
|||| definitely have some problems, but don't blame General Electric for
|||| them.
|||||
|||||
|||||
||||| (e-mail address removed) wrote:
|||||| found out that even though ol2003 creates the new and improved
|||||| unicode pst files, that the import / export utility stops at 4
|||||| gb. way to go m$, nice job.
|||||| doing a lot of copying and pasting here in the "enterprise"

 

[Lanwench [MVP - Exchange]]

In

yes there should be a correction, exmerge doesnt support files greater
that 2 gb. not 4
and it's the overall sa size limits on several things that is truly
irritating. i dont remember asking anyone for any help , especially
not from you.

You posted in a technical support newsgroup for MS Outlook. I rather wonder
what you expected!

the reason we had to use import/export of pst files to migrate
exchange to a new box is because we couldnt get the migration to work
any other way. just ran out of time on it. looking up error messages
all night isnt fun
but it's pretty common when dealing with exchange

Many people (myself included) do this all the time and don't have the
problems you're running into. I hope you feel better after getting your
complaints off your chest, but please remember the purpose of this
newsgroup - and don't post at all if you don't want replies.

<snip>

 

[EMERY_BILL]

i have also done exchange migrations that worked. even used norton
ghost to do one and it worked fine.
problem is , that in this one we ran into multiple problems and didnt
want to migrate the whole thing so used exmerge and import export etc.

 

[Lanwench [MVP - Exchange]]

In

i have also done exchange migrations that worked. even used norton
ghost to do one and it worked fine.
problem is , that in this one we ran into multiple problems and didnt
want to migrate the whole thing so used exmerge and import export etc.

You might check out Recovery Manager for Exchange at www.quest.com. PST
files are best avoided when you can do so.