Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SynchInMigrationMode fail - AD Migration

Updated: 21 May 2010 | 5 comments
James Slack's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi,

I'm back again sorry.

Using Quest to do AD / Exhange migration, old domain to new domain. EV server will stay on Old domain for now. Users should move from Old domain / Exchange server to New domain / Exchange and keep just one Mailbox in EV which they can access and vault new items to. All EV setup has been done that I can think of, but a migrated user is unable to vault new items.

I set SynchInMigrationMode to 0 as suggested to me, but it just came up with errors. When I tried to Synchronize a mailbox we had migrated, it was showing all the values as 0 in vault (0kb 0 mails etc) so I did a bit of research.

Here is what I found on SynchInMigrationMode:
http://seer.entsupport.symantec.com/docs/292785.htm

HKLM\SOFTWARE\KVS\Enterprise Vault\Agents\SynchInMigrationMode
DWORD - 1

The values are as follows:
0 - (Default.) Generate an error in the event viewer log.
1 - Link the new mailbox to the old record.
2 - Create a new record for the new mailbox

Reading this, it looks like option 0 does nothing but raise alerts, option 1 links the mailbox and option 2 creates a new mailbox on Vault.

So, from this, I tried option 1. After doing so, it allowed us to see mail on the test user when doing a sync and showed that the mailbox was already enabled. Now this user can view vaulted items in outlook (not in OWA – though OWA was working on the new domain for a new user) and the user can’t manually vault off items.

Looking in the vault events, I find Event ID 3350:

A new mailbox was linked to an existing entry in the Enterprise Vault database.
New mailbox: /o=MENZIES/ou=MENZIES-AG/cn=Recipients/cn=Alan.Yin
Existing entry: /O=Menzies Transport Services/OU=NTAMI/cn=Recipients/cn=Alan.Yin
Wait until the archive task has finished processing, then reset the SynchInMigrationMode registry value. See the documentation for further details.
For more information, see Help and Support Center at
http://evevent.symantec.com/rosetta/showevent.asp

Using the rosetta link, I get this page:
Details
Event Number 3350
Severity Information
Application or service EV
Typical message
A new mailbox was linked to an existing entry in the Enterprise Vault database. New mailbox: %1 Existing entry: %2 Wait until the archive task has finished processing, then reset the SynchInMigrationMode registry value. See the documentation for further details. For more information, see Help and Support Center at http://evevent.veritas.com/rosetta/showevent.asp
Comment
Please contact SYMANTEC support.
That event number does not yet have a corresponding solution on this system, or it may require intevention from a SYMANTEC engineer.

So, I have logged a call with Symantec, but if anyone has any ideas happy to try them!

Thanks for looking - James

Comments

James Slack's picture
01
May
2009
2 Votes +2
Login to vote

Solution

OK, This was a weird one.

We don't know what caused it but a complete uninstall and reinstall fixed this.

Had to properly remove Vault from the Exchange FE and BE servers and put it back pre vault and then reinstall and rerun the OWA setups.

We, being me and Symantec, checked all the config before and after and it was all set up correct... technically nothing changed with the reinstall - but it worked after!

I have also been looking at another mailbox today that is showing up as 0kb 0mail when it is not empty. I also can't sync this mailbox and I suspect this is due to not having set Vault up before moving him over. I am going to move him back and then try again and at the moment I suspect this will work.

James Slack's picture
07
May
2009
0 Votes 0
Login to vote

Follow up

Still having the same issues with this account - showing 0 kb 0 mail - however, it is showing the cause in the event log now.

Event ID 3333

This mailbox has duplicate entries in the directory and cannot be processed.

LegacyDN:
/o=MENZIES/ou=MENZIES-AG/cn=Recipients/cn=justin.apps
DefaultVaultID:
13A4143BCCEE6884DBF11A1809EF46C931110000vaultsite

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp

However, the Rosetta just says "no info - call support" which is what I have been faced with every time I have used Rosetta bar one.

So, perhaps I will call Symantec Support again and see where this goes - but I suspect something is wrong with the AD migartion.

If anyone has any info on this 3333 event, please let me know - if not I will update the post as soon as I do.

Cheers

James Slack's picture
23
Jun
2009
0 Votes 0
Login to vote

Note for anyone reading this

This was solved in a later post and involved deleting the SQL records for the users in question.

Look at how many records a user has:

USE EnterpriseVaultDirectory
SELECT *
FROM ExchangeMailboxEntry
WHERE (LegacyMbxDN LIKE '%Slack%')order by MbxAlias

delete the user

USE EnterpriseVaultDirectory
DELETE
FROM ExchangeMailboxEntry
WHERE (LegacyMbxDN LIKE '%Slack%')

I didn't work out this solution, I was told about it in these very forums. I just hope down the line it will help someone who ends up in the boat I was in!!

Evault Professional's picture
02
Dec
2009
0 Votes 0
Login to vote

How to determine which row to delete? Part 1

  I posted a similar comment in Symantec's forum (https://www-secure.symantec.com/connect/forums/ev-...) but ran into this one while investigating.

  I have duplicate entries in SQL for 2 out of the 7 journal accounts we are using. We do not want to create new Journal Accounts to resolve this issue (Event ID 3333). How can I determine which duplicate to delete?

 One of the rows for these duplicates contains similar fields filled in each column within this table (ExchangeMailboxEntry) as those 5 additional Journal Accounts mentioned above that are working.

 The other row for these duplicates does not contain any data in most of these columns. However when I run a synchronization; the journal task seems to be pointing to this duplicate based on the screenshot attached and empty values.

Please advise on any comments,
Thanks,
Dennis
 

 (Sorry - I am having trouble uploading my screenshot. I will edit this posting if I can get it to work)
 

Dennis
STS Symantec Enterprise Vault 2007
STS Symantec Enterprise Vault 8.0 for Exchange
STS Symantec Enterprise Vault 9.0 for Exchange

Evault Professional's picture
09
Dec
2009
1 Vote +1
Login to vote

Solution for Part 1 discussion mentioned above

These were the steps I followed to resolve this issue. Hope it helps!

 I compared the text in tables “JournalTarget” and “ExchangeMailboxEntry” for column “ExchangeMailboxEntryId”. The Journal account listed in table “ExchangeMailboxEntry” that did not have its “ExchangeMailboxEntryId” referenced in the “JournalTarget” table was the duplicate entry.
 
 Once the duplicate was identified; I stopped the “Journal Task” for those Journal Accounts reporting Event 3333 and set the Journal Target Archiving value to “Off”. The duplicate rows were deleted in the SQL table “ExchangeMailboxEntry”.  Once the duplicate rows were deleted; I changed the Journal Target Archiving value to “On”, restarted the Journal Task and ran the synchronization.
Event 3333 was no longer reported.

Thanks,
Dennis

Dennis
STS Symantec Enterprise Vault 2007
STS Symantec Enterprise Vault 8.0 for Exchange
STS Symantec Enterprise Vault 9.0 for Exchange