Partially migrated PST Client Driven

[Warwick]

G'day all,

I'm using EV7.5 SP3.  Running client-driven migration.  All is good, apart from a little issue i had this morning.  One of the clients PST migration was interrupted due to the loss of service to the server which was hosting the PST file.

Under Files in the Personal Store Management, it showed as migration failed, accompanied by an 8567 Event with the following text:

Error occurred with client-driven migration of PST '\\HARVEYS\e$\harveys\home\danielco\archive.pst'.

The PST file could not be opened. Error code: '0x80040119'.

Reference: 'PstMigrationFailed'.

There is still a chunk in the holding area.  I sort of expected it to just pick right back up again after it's failure, but it didn't.  I have tried setting the status of the file back to Ready to Copy (as the log in the outlook debug log suggests it knows the count of messages it has done so far, and the chunk it is on), but this results in an 8567 Event ID every minute with the following text:

Error occurred with client-driven migration of PST '\\HARVEYS\e$\harveys\home\danielco\archive.pst'.

Unexpected migration status.

Reference: 'HasPstChunkMigrated'.

I have now set the file to Do Not Migrate and my errors have stopped, but I do want the migration to continue and finish the PST.

Any ideas how I go about this please!?

Warwick

[MirrorSphere]

Hi,

What version of Outlook +SP is that client using.

Did you notice excessive memory usage from the client when migrating this PST.  Is this a particular large PST file or were there multiple PST files for this user?

[Warwick]

Hi,

It's a thin client user, the terminal server is Win 2003 SP2 32 Bit Std, Office 2003 SP3.

No excessive memory usage.  He had multiple PST's (3 of them), 1 was 2.4gb (somehow!! I thought there was a 2gb limit!), which successfully migrated yesterday and the PST was removed this morning.  The second is 1.6gb and this started yesterday, and continued this morning, until 9:11am when a colleague of mine failed a part of our Windows cluster over to another node, which was hosting the PST that was being imported.

Let me know if you need any more info.

Warwick

[Arie]

Hi,

I have the exact same problem! Did you find a solution? Please let me know.

Regards

[MichelZ]

Hi guys

After a failure (even in client-driven migration), EV waits for the configured retry value (usually a day) until it continues to migrate, but only if Outlook was closed during this period.

So it could really take a while for EV to pick migration up again on the file.

Hope this helps...

Cheers

Michel

[Arie]

Hi Michel,

Thanks for your reply, it certenly helps.

I'll wait a day or two and we'll see what happens.... I'll post the results.

Regards

[SHI-CRO]

You can also reset the count attempt in Outlook.  Hold down CTRL and Shift and then press an EV button on the toolbar.  In the panel there, you can reset the attempt count.  This is helpful if you want to test policies, but don't want to wait a day between attempts.

[Mnereng]

Any resolution to this?  I've encountered this error numerous times with no leads yet.