Can't find a user in Vault to enable their mailbox.
Updated: 21 May 2010 | 25 comments
This issue has been solved. See solution.
Hi,
Having some issues finding a few users.
The first one I am trying to enable in Vault has had a mailbox for months. He is in a child domain but I can see other users on the same domain and on the same mail store.
- When I try and do a sync for that user, he doesnt show up.
- When I go to enable new mailbox, he doesnt show up.
- When I look in AD, he is not hidden / disabled.
- When I use Vault, I can see a user who is in the same OU as him and the same mail store, I can also run a sync against this user no problem.
Am I missing something really simple here? Why can't I enable this user?
Cheers for your help
James
discussion Filed Under:
Comments
I am no expert at all, but
I am no expert at all, but when I was troubleshooting something similar yesterday I found the log file produced by the provisioning task very useful. Have you selected Full reports on the Reports tab of the Provisioning task? Can you see the user listed in the repotr file?
Carol
Yes, you need to check the
Yes, you need to check the Provisioning report for the user you are trying to enable. If users are not provisioned they don't show up to synch or enable.
Also, you can check the EV App log as it does log events around provisioning to let you know if something is amiss.
Tony Sterling
You may find these Technotes helpful
You may find these Technotes helpful: -
Mailboxes that are not part of a provisioning group cannot be archived by Enterprise Vault.
http://support.veritas.com/docs/290576
Error 41132 Failed to determine the provisioning group for the mailbox
http://support.veritas.com/docs/290792
Exchange Provisioning Task Report - Mailbox not processed as located on an Exchange Server that is not in the current domain
http://support.veritas.com/docs/316795
Thanks,
Mark
Supportability Analysis Engineer for Enterprise Vault products.
**REMEMBER TO VOTE IF THIS HELPS AND MARK IT AS RESOLVED TOO IF IT IS!!**
Thanks
Yes, I suspect that my provisioning task is failing. I am unsure where the log ends up though so I will have a look.
Cheers and will report back
James
OK - really confused now.
To fill you in - we are dong a migration for AD / mail using Quest. This has linked history etc. etc. I have Vault server running SynchInMigrationMode = 1 at the moment.
My user James.Slack has been migrated. I can access my old vaulted items but cannot vault new items and the "archive after 90 days" does not work.
I ran the provisioning task on the new domain which is only set to look at one OU at the moment.
I can see this entry in the log:
--------------------------------------------------------------------------
10:15:50 1 test OU=Quest Reverse Sync,OU=Users,OU=UK,OU=Admin Region,OU=Resources,DC=emea,DC=menzies,DC=net Default Exchange Mailbox Policy Default Exchange PST Migration Policy CN=James Slack,OU=Quest Reverse Sync,OU=Users,OU=UK,OU=Admin Region,OU=Resources,DC=emea,DC=menzies,DC=net Updated mailbox
Provisioning Group Summary:
test:
Mailboxes added: 0
Mailboxes updated: 11
Mailboxes relinked: 0
Mailboxes ignored because already processed: 0
Provisioning targets that returned no mailboxes: 0
Users without a mailbox: 0
New mailboxes ignored because of existing entries in the Enterprise Vault database: 0
Journal mailboxes found: 0
Users with mailboxes outside the current domain: 0
Users whose mailboxes were not synchronized: 0
Errors: 0
--------------------------------------------------------------------------
Which to me looks like it is there OK. However.
Synchronosation for my user = user not there
Run Now = user not there
Enable new mailbox = user not there
Disable mailbox = user not there
So, I am a bit stuck and lost now.
Any ideas?
EDIT: Also forgot to say, checked the EV log and the only provisioning stuff logged is starting / stopping events. No failures or issues.
it can also be, that user is
it can also be, that user is hidden from exchange adress list.
please check user object
Already checked it and the
Already checked it and the user is also enabled.
Thanks anyways.
Is that your proper OU? In
Is that your proper OU?
In SQL can you run a query for me?
USE EnterpriseVaultDirectory
SELECT *
FROM ExchangeMailboxEntry
WHERE (LegacyMbxDN LIKE '%Slack%')order by MbxAlias
What are the results?
Tony Sterling
Is the user already enabled
Is the user already enabled somehow?
Can you find the user in the ExchangeMailboxEntry Table? If yes, could you post the details of this entry?
Cheers
www.quadrotech-it.com - All your EV Tools | www.techfreak.ch
MichelZ, yes, I was enabled
MichelZ, yes, I was enabled on the old exchange / AD and so I guess I am an enabled user. But I cant see myself to do a sync or run or even disable.
I can see the mailbox in Archives / Exchange Mailboxes. What do you want to know?
Both my old and new users appear in the permissions tab.
Tony S I suck at SQL but will
Tony S
I suck at SQL but will hop on the SQL box and give it a go an report back.
Thanks
Tony Thanks for the clear
Tony
Thanks for the clear instructions, that helped me a lot as I really do suck at SQL!!
These are the results.
1CB91BF7EB392FB48B8C1C68573CEF1541n10000vaultsite 2878 (MARKED @ 00:00:44 07/27/07) /o=Menzies Transport Services/ou=NTAMI/cn=Recipients/cn=james.slack James Slack james.slack james.slack MAG 1 1 1 0 0 0 360000 62839 16F7FD66573BCF948AF7599DAE31580C01110000vaultsite 1 James Slack 0 2007-07-26 11:00:34.000 NULL NULL NULL NULL NULL NULL NULL NULL NULL
1DCFEA300302AA148BCC97A1494D81FCB1n10000vaultsite 2858 (MARKED @ 12:00:31 06/18/07) /o=Menzies Transport Services/ou=NTAMI/cn=Recipients/cn=james.slack James Slack james.slack james.slack MAG 1 1 1 0 0 0 293947 58086 16F7FD66573BCF948AF7599DAE31580C01110000vaultsite 1 James Slack 0 2007-06-17 23:00:39.000 NULL NULL NULL NULL NULL NULL NULL NULL NULL
1F64E045D4A11F14D8A2F9F6CB01368AE1n10000vaultsite 731 (MARKED @ 12:00:34 06/15/07) /o=Menzies Transport Services/ou=NTAMI/cn=Recipients/cn=james.slack James Slack james.slack james.slack MAG 1 1 1 0 0 0 316338 57670 16F7FD66573BCF948AF7599DAE31580C01110000vaultsite 1 James Slack 0 2007-06-14 23:00:20.000 NULL NULL NULL NULL NULL NULL NULL NULL NULL
15B234DF9E1D7BF43A9DFD8FAA701061A1n10000vaultsite 3079 /o=Menzies Transport Services/ou=NTAMI/cn=Recipients/cn=james.slack James Slack james.slack james.slack MAG 1 0 1 0 0 0 516922 105188 16F7FD66573BCF948AF7599DAE31580C01110000vaultsite 1 Menzies Aviation IT James Slack MW1 - IT Office Windows System Administrator 0 2009-06-16 11:03:35.000 NULL 199A30E25678B0440A4408F23B9C70F9B1012700vaultsite 148A9B121C9B80E44B2A10B3FCBB0B6C51012700vaultsite
1DFE558F6504D4363A7CE83487B617F941012p00vaultsite 12A66C79A9523480592F985CF29BE7F3D1012o00vaultsite CN=James Slack,OU=IT Test,OU=IT,OU=LHR - London Heathrow,OU=United Kingdom,DC=mag,DC=global f00b988d81a75e43bf8f359a34ee127c 2 0
1416645835723E048B655ECC6B7201B8E1n10000vaultsite 5182 /o=MENZIES/ou=MENZIES-AG/cn=Recipients/cn=james.slack James Slack james.slack 3 1 1 0 0 0 0 0 4 Menzies Aviation Plc Head Office GB;United Kingdom; Information Technology (IT) James Slack Building 557 MW1 (IT Dept) Windows System Administrator 0 2009-06-15 23:00:07.000 NULL 1E13C07DA622EF448813F811B6B87355A1012700vaultsite 148A9B121C9B80E44B2A10B3FCBB0B6C51012700vaultsite 1B30A0897DEB4EA4584379E92F0CBCC871012p00vaultsite 1566270D0EF950B4EB2A4784DA2C237DA1012o00vaultsite CN=James Slack,OU=Quest Reverse Sync,OU=Users,OU=UK,OU=Admin Region,OU=Resources,DC=emea,DC=menzies,DC=net ee41a57e15d70844a8bc1ad8bacd5d60 21 0
Any idea what's going on from this?
So, to sum up: - You have
So, to sum up:
- You have created a new Exchange Task for the new Server
- You have moved your User with Quest to the new Server / AD
- The provisioning task is seeing your User
- You have SynchInMigrationMode set to 1
Your problem now is that you cannot see the user in the Sync choice of mailboxes, but you can see other users which are in the same AD/OU and on the same Server
Correct?
Just for fun, could you remove the SyncInMigrationMode registry key?
Is there anything in the Eventlog after removing it and starting provisioning and sync?
Cheers
www.quadrotech-it.com - All your EV Tools | www.techfreak.ch
That's correct
That's correct MichelZ.
However, would removing the SyncInMigrationMode key not screw up our migration?
Strange...
I have just done an archive run on someone who is in the same OU as me and was migrated in the same way as I was and it just archived all his mails older than 90 days. Which is what I would expect.
So, how can i work out what is different between my account which doesnt show up and the working account which seems faultless.
Cheers - James
Tony
Doing that SQL bit for the working user, I found get only this result:
1338B2B0B53AC7046B654A6B2480FB1541n10000vaultsite 5191 /o=MENZIES/ou=MENZIES-AG/cn=Recipients/cn=Alan.Yin Alan Yin Alan.Yin Alan.Yin EMEA 1 0 1 0 0 0 399427 19644 189D15B11065A374199D2726F0328A8ED1110000vaultsite 4 Menzies Aviation Plc Head Office GB;United Kingdom; Information Technology (IT) Alan Yin Building 557 MW1 (IT Dept) 0 2009-06-16 13:53:34.000 NULL 1E13C07DA622EF448813F811B6B87355A1012700vaultsite 148A9B121C9B80E44B2A10B3FCBB0B6C51012700vaultsite 1B30A0897DEB4EA4584379E92F0CBCC871012p00vaultsite 1566270D0EF950B4EB2A4784DA2C237DA1012o00vaultsite CN=Alan Yin,OU=Quest Reverse Sync,OU=Users,OU=UK,OU=Admin Region,OU=Resources,DC=emea,DC=menzies,DC=net 99ee6b3483d7d845a637ea4ed2be016c 21 2
This is a lot different to what I found with my name search. Does this mean something is screwed up in SQL and if so, any idea what I need to change / fix?
Thanks
It seems from the results of
It seems from the results of the query that you have been moved around quite a bit. :)
you could run this command
USE EnterpriseVaultDirectory
DELETE
FROM ExchangeMailboxEntry
WHERE (LegacyMbxDN LIKE '%Slack%')order by MbxAlias
This will remove your entries, this is ok because after everything is synced it will repopulate with the correct data.
After your run the sql do a synch all mailboxes for your exchange server.
regards,
Tony
Tony Sterling
Command wont run
I tried but failed.
I get this error:
Msg 156, Level 15, State 1, Line 4
Incorrect syntax near the keyword 'order'.
when I ran this:
USE EnterpriseVaultDirectory
DELETE
FROM ExchangeMailboxEntry
WHERE (LegacyMbxDN LIKE '%Slack%')order by MbxAlias
I don't think you need to
I don't think you need to have the order by - the example failed as it didn't have a space between the ) and o parts.
This should work ok -
USE EnterpriseVaultDirectory
DELETE
FROM ExchangeMailboxEntry
WHERE (LegacyMbxDN LIKE '%Slack%')
Thanks,
Mark
Supportability Analysis Engineer for Enterprise Vault products.
**REMEMBER TO VOTE IF THIS HELPS AND MARK IT AS RESOLVED TOO IF IT IS!!**
Oh yeah!
That worked, thanks Mark.
As previously stated, I suck at SQL!! The weird thing is there is no space in the select query and that worked fine so I guess the Order part was just wrong (maybe?!).
Now to see if it helps me out. I will report back soon.
yes, that is my bad. I
yes, that is my bad. I copied it from my previous entry and forgot to remove the Order By statement. Thanks for cleaning that up Mark.
Tony Sterling
Right...
I reran the provisioning task for the new domain and got this:
----------------------------------------------
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=james.slack
Existing entry: /o=Menzies Transport Services/ou=NTAMI/cn=Recipients/cn=james.slack
Wait until the archive task has finished processing, then reset the SynchInMigrationMode registry value. See the documentation for further details.
----------------------------------------------
and now I can see myself to Sych!!
Now, I know this looks like it could just be a case of I should have disabled the old user, but the working users also have 2 live accounts and did not have this issue for some reason.
Anyways, I can see myself and am currently doing a run now so it looks like a win!!
Will report back final findings etc. soon.
Thanks
Glad to hear!
Glad to hear!
www.quadrotech-it.com - All your EV Tools | www.techfreak.ch
Working
Yep, that sorted it. All vaulted now!
I just did this on a user who was enabled in both domains and it is fine for him also!
Many thanks for all your help and input guys!
James
I love it when a plan comes
I love it when a plan comes together!!
Thanks,
Mark
Supportability Analysis Engineer for Enterprise Vault products.
**REMEMBER TO VOTE IF THIS HELPS AND MARK IT AS RESOLVED TOO IF IT IS!!**
Would you like to reply?
Login or Register to post your comment.