Need help with PST imports from EV9 to EV10

[NJCRU]

Hope you can assist with some PST import issues.

I do have a call logged with Symantec Case 05303194

One of my clients moved away from a Hosted Shared environment to their own dedicated environment.

This will Include :

Exchange 2010

Enterprise  Vault

SQL

They moved over a weekend and we only got involved after the move of Exchange to the new environment.

They exported all archive to PST and the CFG file.

The hosted (old) EV environment was the following.

EV 9.0.1

Exchange 2010

SQL 2005

New Environment:

EV 10.0.3

Exchange 2010

SQL 2008

1. I setup a new EV 10 server and its own dedicated SQL server
2. Enable some users for testing of archiving
3. Import some pst al working fine.
4. Then we started to get the following  popup “the PST Migration server on “server” has unexpectedly shut down”
5. Event id 2667 mainly
6. This only got worse as we started to import more and more pst and currently I cannot import one pst.

I cannot compare my policies with the old ev environment

I tried to import without the cfg file, added the registry key for embedded attachments although its only for EV 9

Check all permission on pst and for read only or hidden settings

Added EVA grant permissions to archive

Made sure deployment scanner has no errors

Open the pst in outlook as a data file

Delete all MAPi profiles uner outlook

Change profile expire to 1 day

[Rob_Wilcox1]

Do you get an application event log entry indicating a crash? What antivirus is on the server or the location hosting the PSTs? Have you tried importing via exchange PowerShell, then archiving the items?

[NJCRU]

I just get event id 2776

An exception occurred in routine

AddAttachmentListToMsgBody

EXCEPTION_ACCESS_VIOLATION @ 0x72CA6DEC

I did move the PST file to a partition that is excluded from the anti-virus (ESET Security) scans.

I will be trying the Exchange Imports today.  What will happen to the stubs in the clients mailbox that was recover from the previous exchange server?

Will EV detect it as orphaned stubs?

I also get Event ID 8390 - But think that is because the current stubs in the user mailbox is pointing to the old EV server.

[EV_Ajay]

Hi,

1. Check the Antivirus exclusion is set on both EV Server .

2. Observed this issue with auditing enable. Hence Disable auditing and get PST imported and then turn it back auditing on EV Server.

[NJCRU]

HI All,

Just an Update.

I disabled auditing to start the imports. It did then completed with errors with sync legacy stubs to the newly imported archives.

Then we deleted the EV Stubs via Exchange.

Then import the .PST files without the .cfg file back to EV.

All working fine.

The .cfg file is only if you intend to import the .PST file back into the same EV Site?

[EV_Ajay]

Hi,

Thanks for your update.

The CFG file have the configuration about the PST. Like Mailbox Name, etc.

If you only choose PST and provide manually the Archive Name at the time of Import Wizard it will be the same.

[Rob_Wilcox1]

Are you all sorted with this issue Nicki?