Pst Import Woes ....

[uk_newbie]

Hi All,

i am trying to import some PST in to the vault using the wizard driven method. The method works to up a point but then it fails due to (im guessing) a corrupt message.

I have used the dtrace on pst migration to identify what message is corrupt (although this does seem like a very long winded method).

It seems that any messages with a foreigh character, ie a email from "Bonhôte, Andréé" , stops the import.

I have set the pst language to be western eurpoean.

Is there any setting / options or a reason, why an email with a foreign character would cause the pst import to fail?

Is there any "quick-wins" when working with corrupt pst's? or any tools? i have tried scanpst with no joy

I would love a pst import feature where we can just say "ignore" corrupt messages. :)


thanks in advance.

[Rob_Wilcox1]

We're in the process of releasing a post EV 8 SP 2 hotfix which will do just what you suggested .. :)

It actually does 3 things ...

a) We had a problem migrating and archiving SMIME signed messages into an archive which was vault cache enabled.

b) We had a problem where there were non-printable ASCII characters in the first 120/240 characters of the message body, these would not migrate or archive if the archive was vault cache enabled.

c) We had a problem where if we encountered a "bad" message in a PST it would fail the whole PST.  Now we will properly log (in the event log) the folder and subject of the message, and move on to the next message.

Before leaping on to that fix though, we're also investigating another issue which you might be encountering.  Can you check your regional settings, and your language for non-unicode applications?  Do they match?  It doesn't matter what they are as long as they match .. if you don't you might encounter the problem we've just recently discovered.  To verify ..  can you post your DTRACE, or the relevant bit with the error on it +/- 25 lines or so.

Hope that helps,

[MichelZ]

Rob

Are you sure with the reginal settings / language for non-unicode applications?

Because I'm sure that Enterprise Vault complains about the "language for non-unicode applications" if it is NOT set to English when installing EV.
So EV does complain if they match (German), and wants that they do NOT match (Reginal Settings -> German / non-unicode -> English)

Cheers
Michel

[Rob_Wilcox1]

The complaint during the install is different ...  I can't remember the exact details of that at the moment.  I do know what you mean though.

I'm talking about "after" that.  I've got 2-3 cases where customers get a specific issue when archiving some mails (or PST importing them) and the issue is that they hav regional settings set to Hungarian, but the non-unicode bit is set to English - so the "fix" for them is to set the non-unicode to Hungarian.

I won't know if uk_newbie is having that problem, which we haven't fixed, or one of the other ones that I described which we have fixed, until I see the trace.

Make sense?

[MichelZ]

Not yet.

So you say EV does complain for non-unicode not set to english for no real reason?
(There must be reason it does it)

And now the "fix" is to *ignore* the original *requirement* of having it in English....  :)
That's what does not make sense right now.

But I'm sure you'll work it out :)

[GCSPT]

Having been confused slightly by this in the past, taken oppurtunity to revisit. could this link explain why we have  to set the 'language for non-unicode programs' to english?
http://www.microsoft.com/globaldev/tools/apploc.mspx

[uk_newbie]

Hi All,

Many thanks for the replies.

You were correct, we had a mismatch. Regional was set to English-UK, unicode was set to English-US.

I set both to UK, rebooted, but pst still fails.

I used this to get the trace to find the corrupt message
http://seer.entsupport.symantec.com/docs/320832.htm


here is trace:

(CDirectoryServiceObject::ChunkPstFile) [lines {...,17522,17524,17537,17543,17549,17552,17555,17558,17594,17599,17602,17605}] built Jul  3 19:54:22 2009|Description: Unexpected fn exit path.
1317 10:06:04.385  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessFolders (Exit) |
1318 10:06:04.385  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessFolders (Exit) |
1319 10:06:04.385  [7472] (MigratorServer) <8084> EV:L CMigrator::CheckJobState (Entry) |
1320 10:06:04.385  [7472] (MigratorServer) <8084> EV:M CMigrator::CheckJobState (Exit) |
1321 10:06:04.385  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessFolders (Entry) |
1322 10:06:04.385  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessMessages (Entry) |
1323 10:06:04.385  [7472] (MigratorServer) <8084> EV:L CMigrator::GetFolderCustomPropIds (Entry) |
1324 10:06:04.385  [7472] (MigratorServer) <8084> EV:M CMigrator::GetFolderCustomPropIds (Exit) |Success  [0] |
1325 10:06:04.385  [7472] (MigratorServer) <8084> EV:L CMigrator::BuildFolderPath (Entry) |
1326 10:06:04.385  [7472] (MigratorServer) <8084> EV:L CMigrator::GetParentFolderName (Entry) |
1327 10:06:04.385  [7472] (MigratorServer) <8084> EV:M CMigrator::GetParentFolderName (Exit) |Success  [0] |
1328 10:06:04.385  [7472] (MigratorServer) <8084> EV:M CMigrator::BuildFolderPath (Exit) |Success  [0] |
1329 10:06:04.385  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessMessages|Processing messages|Folder: Calendar
1330 10:06:04.622  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessMessages (Exit) |Success  [0] |
1331 10:06:04.701  [5652] (DirectoryService) <5556> EV:L CAuthHelper::ValAuthString AuthToken:10.100.114.35 pKF5***** ==> User:INTERNAL\mdalton (hr=Success  [0])
1332 10:06:04.701  [5652] (DirectoryService) <5556> EV:M DirectoryService: ADO: GetObjectsBySIDs |
1333 10:06:04.858  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessFolders (Exit) |
1334 10:06:04.858  [7472] (MigratorServer) <8084> EV:L CMigrator::CheckJobState (Entry) |
1335 10:06:04.858  [7472] (MigratorServer) <8084> EV:M CMigrator::CheckJobState (Exit) |
1336 10:06:04.858  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessFolders (Entry) |
1337 10:06:04.858  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessMessages (Entry) |
1338 10:06:04.858  [7472] (MigratorServer) <8084> EV:L CMigrator::GetFolderCustomPropIds (Entry) |
1339 10:06:04.858  [7472] (MigratorServer) <8084> EV:M CMigrator::GetFolderCustomPropIds (Exit) |Success  [0] |
1340 10:06:04.858  [7472] (MigratorServer) <8084> EV:L CMigrator::BuildFolderPath (Entry) |
1341 10:06:04.858  [7472] (MigratorServer) <8084> EV:L CMigrator::GetParentFolderName (Entry) |
1342 10:06:04.858  [7472] (MigratorServer) <8084> EV:M CMigrator::GetParentFolderName (Exit) |Success  [0] |
1343 10:06:04.858  [7472] (MigratorServer) <8084> EV:M CMigrator::BuildFolderPath (Exit) |Success  [0] |
1344 10:06:04.858  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessMessages|Processing messages|Folder: Journal
1345 10:06:04.953  [5652] (DirectoryService) <5556> EV:M HRXEX fn trace :|Source     : .\DirectoryServiceObject.cpp (CDirectoryServiceObject::GetRootRecordsBySIDsAndPermissionsEx) [lines {7266}] built Jul  3 19:54:22 2009|Description: Unexpected fn exit path.
1346 10:06:04.969  [5652] (DirectoryService) <5556> EV:M DirectoryService: ADO: dbo.GetUserVolumeSets |
1347 10:06:04.969  [5652] (DirectoryService) <5556> EV:L CAuthHelper::Reset Cancel registration? true CancelId: 0
1348 10:06:04.985  [5652] (DirectoryService) <6744> EV:M CDirectoryServiceObject::GetWebAppURLByArchiveId - leaving with [http://evs001.internal.colt.net/EnterpriseVault]
1349 10:06:05.048  [5652] (DirectoryService) <6656> EV:M DirectoryService: Method call: CDirectoryServiceObject::ReadDirectoryStorageServiceComputerByVault, param (1497E1BA1CF94CE4CB63301DCD9EC2B591110000evs001) |
1350 10:06:05.048  [5652] (DirectoryService) <6656> EV:M DirectoryService: ADO: SELECT ComputerEntryId,ComputerName,ComputerRootPath,ComputerSiteEntryId,ComputerAdminNote,VaultSoftwareVersion,ComputerNameAlternate,FileServerManagementUrn,SvcNamesUpgradeState,CacheLocation,CacheSize,VaultStoreEntryId,RootIdentity,VaultEntryId,Type,Hidden FROM view_computer_vault WHERE VaultEntryId = ? |
1351 10:06:05.095  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessMessages (Exit) |Success  [0] |
1352 10:06:05.332  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessFolders (Exit) |
1353 10:06:05.332  [7472] (MigratorServer) <8084> EV:L CMigrator::CheckJobState (Entry) |
1354 10:06:05.332  [7472] (MigratorServer) <8084> EV:M CMigrator::CheckJobState (Exit) |
1355 10:06:05.332  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessFolders (Entry) |
1356 10:06:05.332  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessMessages (Entry) |
1357 10:06:05.332  [7472] (MigratorServer) <8084> EV:L CMigrator::GetFolderCustomPropIds (Entry) |
1358 10:06:05.332  [7472] (MigratorServer) <8084> EV:M CMigrator::GetFolderCustomPropIds (Exit) |Success  [0] |
1359 10:06:05.332  [7472] (MigratorServer) <8084> EV:L CMigrator::BuildFolderPath (Entry) |
1360 10:06:05.332  [7472] (MigratorServer) <8084> EV:L CMigrator::GetParentFolderName (Entry) |
1361 10:06:05.332  [7472] (MigratorServer) <8084> EV:M CMigrator::GetParentFolderName (Exit) |Success  [0] |
1362 10:06:05.332  [7472] (MigratorServer) <8084> EV:M CMigrator::BuildFolderPath (Exit) |Success  [0] |
1363 10:06:05.332  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessMessages|Processing messages|Folder: Sent Items
1364 10:06:05.758  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessChunkOfMessages (Entry) |
1365 10:06:05.758  [7472] (MigratorServer) <8084> EV:L CMigrator::CheckJobState (Entry) |
1366 10:06:05.758  [7472] (MigratorServer) <8084> EV:M CMigrator::CheckJobState (Exit) |
1367 10:06:05.758  [7472] (MigratorServer) <8084> EV:L CMigrator::isEligibleForArchive (Entry) |
1368 10:06:05.758  [7472] (MigratorServer) <8084> EV:L CMigrator::ValidCodepage (Entry) |
1369 10:06:05.758  [7472] (MigratorServer) <8084> EV:M CMigrator::ValidCodepage (Exit) |
1370 10:06:05.758  [7472] (MigratorServer) <8084> EV:M CMigrator::isEligibleForArchive (Exit) |
1371 10:06:05.758  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessChunkOfMessages|Processing item|Subject: LANLINKs for Switzerland
1372 10:06:05.805  [7472] (MigratorServer) <8084> EV:L CMigrator::ProcessItem (Entry) |
1373 10:06:05.805  [7472] (MigratorServer) <8084> EV:L CMigrator::SetArchiveFolderVault (Entry) |
1375 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CBaseDirectoryServiceWrapper::CreateDirectoryService() - Entry [m_nNumTries = 40]
1376 10:06:05.805  [7472] (MigratorServer) <8084> EV:L CBaseDirectoryServiceWrapper::CreateDirectoryService() - Successfully communicated with an EV Directory Service on the local machine
1377 10:06:05.805  [5652] (DirectoryService) <5556> EV:M DirectoryService: ADO: GetArchiveFolderVEID |
1378 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MarkFolder has started
1379 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MarkFolder calling HrMAPIOpenFolderExKVSPstMig
1380 10:06:05.805  [7472] (MigratorServer) <8084> EV:M HrMAPIOpenFolderExKvs - Looking for folder [Sent Items]
1381 10:06:05.805  [7472] (MigratorServer) <8084> EV:M HrMAPIOpenFolderExKvsPstMig - Folder Sent Items exists, opening to look for next folder
1382 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MarkFolder getting filter value object
1383 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MarkFolder creating hidden message
1384 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MarkFolder() - Returned from CreateHiddenMessage() where ArchiveId: 163AEBD0839D224409D46940D613365DB1110000evs001 and ArchiveFolderId: 19E099BF9CCA7B44EA7FE992D49736DF71110000evs001 with [0x8004060C]|
1385 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MarkFolder() - Error [0x8004060C]
1386 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MarkFolder has quit
1387 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::SetArchiveFolderVault (Exit) |Exception occurred.  [0x80020009] |
1388 10:06:05.805  [7472] (MigratorServer) <8084> EV~E Event ID: 6469 An exception has occurred.| [Internal reference CMigrator/SAFV/ce] |
1389 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessItem (Exit) |Catastrophic failure  [0x8000ffff] |
1390 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessChunkOfMessages (Exit) |Catastrophic failure  [0x8000ffff] |
1391 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessMessages (Exit) |Catastrophic failure  [0x8000ffff] |
1392 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessFolders (Exit) |
1393 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::ProcessFolders (Exit) |
1394 10:06:05.805  [7472] (MigratorServer) <8084> EV:M CMigrator::MigrateFolders (Exit) |Catastrophic failure 

------------------------------------------
Looks like something in sent items.


This issue has become quite critical as its impacting a large roll out. Any chance to try the hotfix? :)

thanks

[Rob_Wilcox1]

MichelZ ...  we should take that up offline, as it's offtopic to this particular issue.  PM me, if you like.

[Rob_Wilcox1]

I feel your error is "different" to the ones that I've seen, and unfortunately it's not easy to gather all the right information here.  As I said there is a post EV 8 SP 2 hotfix which allows the migrator to move on past problem messages, however, we still have to understand what's causing the problem on the problem message, so using the hotfix shouldn't be something that is done lightly.  You could end up with 10,000 messages in the PST, and 10,000 of them get skipped, if the real problem lies elsewhere.

The best best is to open a Support case, and talk to them about :

EV 8.0 SP2 Hotfix-Cumulative storage fixes for Etracks 1807076  1810625  1835530

[jiller50]

I am particularly interested in part ‘C’ of this hotfix. I currently have over 150 PSTs in my environment with this “unexpected error,” and the number grows everyday.  I understand that the migrator will move past the message and log a warning with specific information (which is excellent). But, how does EV handle the rest of the migration?

When it reaches the end of the PST, does it just leave the PST with the corrupt messages in it? Is the PST still attached to the user’s Outlook?   How is the file listed under Personal Store Management in the VAC, as ‘Complete’ or ‘Migration Failed?’ 
Thanks!

[Rob_Wilcox1]

Jiller50..

Some of what happens depends on your shortcut creation policy in the PST policy ...

a) no shortcuts
The failed items are left in the PST, and nothing else is done with the PST as far as I understand.

b) shortcuts in the pst
The failed items, and the shortcuts will still stay in the PST and nothing else will be done with it.

c) shortcuts in the mailbox
The shortcuts and the failed items will be moved to the mailbox.  In fact the failed items even get to go in their own folder in the mailbox.  If all of the moves are successful, then the PST is tidied up per the policy, if the moves aren't successful, then the PST is left as is.