Red Gate forums: PST Importer 2010

Import Error: (0x80004005) HResult E_Fail...

NCDST.Admin — Tue, 29 Jan 2013 16:36:10 GMT

Recently, I've been experiencing an import error. We'll have PST imports successfully complete, while other PSTs will continuously generate the following error...

Error transferring message to exchange | System.Runtime.InteropServices.COMException (0x8004005): Error HRESULT_EFAIL has been returned from a call to a COM component.

When it does happen, there's about 4-8 emails affected. All random, all from different internal users.

I've done research on Microsoft's site and other Tech Sites, but I have not found any article related to this error message I'm receiving.

Any help would be appreciated!

RE: Our Requirements for a PST Importer Program

oiver — Wed, 13 Jun 2012 07:18:48 GMT

Hello, Robert

you can use Kernel for PST compact and compress program is compatible with various versions of Windows like Windows XP, Vista, 2000, 2003, 7. At least 7 MB space in computer hard disk is required for installation of PST compression software. The software allows the user to save email attachments of outlook accounts in a separate zipped folder, new PST file or unzipped folder. Making two separate compressed folders one for PST files and another for attachment files by this program serves dual purposes. One, it maintain original data structure of user�s outlook PST files and another, it can be conveniently unzipped by the same program, when required by the user.
For more please visit here...http://www.compactpst.com

RE: Import error: Exception from HRESULT: 0xC004AB16

biggy140886 — Fri, 05 Aug 2011 10:44:57 GMT

Thank you for the help.

Removed the Junk Mail folder in both cases (after some filtering) and both uploaded without error.

Cheers for the Speedy response, muchos appreciated.

Kind Regards,

Shani

RE: Import error: Exception from HRESULT: 0xC004AB16

Brian Donahue — Fri, 05 Aug 2011 09:54:15 GMT

Hello Shani,

You can get this rather obtuse COM error code if your PST contains a "junk email" folder. There is something special about the messages in that causes Exchange to complain about trying to import "junk" into the mailbox.

Import error: Exception from HRESULT: 0xC004AB16

biggy140886 — Fri, 05 Aug 2011 08:59:05 GMT

HELP!!!!

can anyone translate this error for me?

Import error: Exception from HRESULT: 0xC004AB16

is the message on two failures out of 8 importing into exchange.

we have tried restarting the importer service and restarting the system. ther are NEW .pst files and we are a little baffled as to what to do next.
-the accounts are setup the same as the others in AD.
-.pST's created in the same way

im going to try running scanpst and see if that bring any joy but any assistance in the matter would be much appreciated.

thank you

Kind Regards,

Shani

Import pst's into Clean Install of Exchange 2010

Lawrence Pepper — Fri, 14 Jan 2011 20:54:41 GMT

Question on your software.

I am interested in purchasing it if it will do the following:

We are moving from Microsoft SBS 2008 and Exchange 2007 to Microsoft SBS 2011 and Exchange 2010 sp1.

We have 30 users. We are going to go to each clent pc and manually export their Outlook data including mail, calendars, notes, contacts, etc.. to pst's and place them all in one location.

We then want to import them to a brand new installation of Exchange 2010. All their user accounts will be re-created from scratch but will have no data in them. What we need to happen is that when we import the pst's into their newly created mailboxes we need them to be set up exactly as they were before, with all subfolders, calendars, contact lists etc.

The literature on your site says they are imported into an archive folder. I do not want that. I need the structure of their current mailbox to be replicated exactly.

Thanks

L

RE: Import error: You must install Outlook 2010 (32-bit)

evilbeg — Mon, 20 Dec 2010 13:04:00 GMT

evilbeg wrote:

Good day people,

i get this error when i'm trying to import pst to a mailbox. I installed outlook 2010 32 bit it's activated.
PST importer is running on my exchange 2010.

I try to add 1 pst from a folder, i set the destionation mailbox and it says importing in status but then fails with the error mentioned before.

Ideas?

I'm running trial version, i really like the program (if i can use it i will buy it).

O.k. Found what it was.. Silly me doing it on the server side it works fine on the client side!

Import error: You must install Outlook 2010 (32-bit)

evilbeg — Mon, 20 Dec 2010 11:45:10 GMT

PST Importer 2010 v1.1 has been released

Ben Adderson — Thu, 16 Dec 2010 09:38:41 GMT

We are pleased to announce the release of PST importer 2010 v1.1.

To find out more about the product, or try our free 14 day trial go to http://www.red-gate.com/products/exchange-administration/pst-importer-2010/

Features in version 1.1

Version 1.1 of PST Importer 2010 includes the following features:

� Ability to import PST files directly into Microsoft Exchange
� Find every PST file on your network
� Optionally import non-mail items such as calendar entries and tasks
� Fully integrate messages into users� Outlook folder structure
� View live information on the progress of your import
� Manage corrupt and password-protected files
� Benefit from deduplicated message storage
� Schedule your imports to run manually, recurring or one-off

RE: Importing straight into Exchange 2010 SP1 archiving mailbox

Nigel Morse — Mon, 13 Dec 2010 08:25:27 GMT

V1 can't do this, but V1.1 due out later this week (all being well) has this ability.

Importing straight into Exchange 2010 SP1 archiving mailbox

mnollar — Tue, 07 Dec 2010 21:20:01 GMT

Is it possible to have the import job import the PST directly into the Archive mailbox for my users? I'd rather leapfrog the step of dumping everything into my production mail store if I can have it go directly to the archive. I know this is possible with SP1 through the Exchange Management Shell, but can PST Importer 2010 do this scripting without me having to hit Powershell?

Thanks,
Mike

RE: Import Exchange 2003 PST Into Exchange 2010 Possible???

marcel@funda.nl — Thu, 25 Nov 2010 11:02:44 GMT

Got my answer already from red-gate support after 5 minutes!

Great support!

And, yes it is possible to import 2003 PST into 2010!

Thanks

Import Exchange 2003 PST Into Exchange 2010 Possible???

marcel@funda.nl — Thu, 25 Nov 2010 10:39:53 GMT

Hello All,

Like the topic title says; is it possible to import exchange 2003 PST's into Exchange 2010?

Thanks,

Regards,

RE: Our Requirements for a PST Importer Program

ecayer — Tue, 02 Nov 2010 16:48:37 GMT

Hello, Robert.

Sorry for the delay in replying to you on this. There isn�t a short answer to all your points below: some of it is planned for a release that�s right around the corner, some of it is already possible, and some of it we aren�t likely to do in the very near term. So point-by-point�.

1. Discover all PSTs on both File servers and user workstations - Really don't like the agent based discovery since we'd have to deploy it to 2000 desktops

It is possible today to search network shares with the software. There are certainly good and bad things about an agent-based search, and we had to come down on one side. Avoiding firewall issues and not having to serialize the search on the administrative machine were a couple of the reasons we did make that choice.

2. Identify seperately PSTs that are mounted to Outlook currently to those that are present but unmounted.
3. Identify who is using the PST

This functionality was in pre-release versions of the product, but we had to remove it after it repeatedly performed very badly in usability tests. We tried a few different ways to present the user profile information as part of the search results, but we never encountered a user who made sense or use of it. Clearly, we can revisit that decision if you users tell us we were wrong.

4. When the Import process is kicked off remove the PST from the users Outlook profile, then copy/move it to the staging area.

The main difficulty here is doing anything that affects a user�s Outlook session if Outlook is open (an unfortunately common scenario). The best solution we know would be to put something in place so that this can occur when the user next closes Outlook. Synchronizing the import and removal is a need we are aware of, but we are not likely to ship a product with a built-in solution to this in the near future.

5. Collaborate results from PSTs discovered on file servers to PSTs mounted on users PCs pointing to those file server based PSTs.
6. Import the PST in to the new Archive store (Don't see a option today to do that) in to a sub-folder with the same Display Name the users had on the PST. (I only see a option to use file name).

We expect to ship a version that imports directly into the archive mailbox shortly as a v1.1. Also, despite the option having the text �file name� for the folder name, we do actually use the display name, which makes much more sense!

Some other thoughts. Since you do use a remote agent can it do anything like compress the PST as it copies across the wire. We have many users in remote offices over WAN links.

The PST file is compressed over the wire. If you want any more details on that or anything else I�ve mentioned, please let us know.

Thanks again for the feedback, and I hope that this glimpse into future capabilities helps with your planning!

Elizabeth Ayer
Exchange Product Manager

Our Requirements for a PST Importer Program

RobertGreenlee — Thu, 21 Oct 2010 22:22:44 GMT

We are in the process of a project to import all PSTs for out 2500+ users in to the new Personal Archive Folders of Exchange 2010. I did a quick demo but I found it lacking in many ways so I wanted to list out our requirements to see if its something you can work with. I know you can do some of these things but many important ones are missing.

1. Discover all PSTs on both File servers and user workstations - Really don't like the agent based discovery since we'd have to deploy it to 2000 desktops
2. Identify seperately PSTs that are mounted to Outlook currently to those that are present but unmounted.
3. Identify who is using the PST
4. When the Import process is kicked off remove the PST from the users Outlook profile, then copy/move it to the staging area.
5. Collaborate results from PSTs discovered on file servers to PSTs mounted on users PCs pointing to those file server based PSTs.
6. Import the PST in to the new Archive store (Don't see a option today to do that) in to a sub-folder with the same Display Name the users had on the PST. (I only see a option to use file name).

Some other thoughts. Since you do use a remote agent can it do anything like compress the PST as it copies across the wire. We have many users in remote offices over WAN links.

Are you guys workign on future versions to fix these shortcomings?

Thanks

Robert