I wish I had that luxury, but I don't. That is why I have yested this thing to death in a test environment. But, I still realize things can go down the wrong road real fast.
Here is the fix for the error, when you have multiple journal services per Exchange server.
Note: The end of Step 2 says "This will produce errors." That's the reference to the error I was getting...
-----------------------------------------------------------------------------------------
The process for re-creating all Journaling services would be as follows. Let me know if you have questions.
1. Perform DR as outlined in Operations Guide.
2. Be sure to run the Enterprise Vault Configuration as outlined in the DR procedure. This will produce errors.
3. Rename the Journaling services that have been created.
o Ensure all Enterprise Vault Journaling services are stopped.
o Open the registry on the vault server and expand to "\HKLM\System\CurrentControlSet\Services\". Find the keys under this level starting with "EV_J_". Take note of the service ID in the name of the registry key following the "EV_J_" for one of these keys.
o Open Enterprise SQL Manager and expand to "\Databases\EnterpriseVaultDirectory\Tables\"
o Right click on the "JournalingServiceEntry" table and select "\Open Table\Return all rows"
o Find the record with the matching "ServiceEntryId" from the registry key and highlight/copy the "Description" variable.
o Go back to the registry and select that corresponding "EV_J_
" key under "\HKLM\System\CurrentControlSet\Services\".
o Update the "DisplayName" registry key with the copied text from the SQL "Description" variable.
o Repeat this until all journaling services that exist so far have been updated with the correct service names.
4. Re-run the Enterprise Vault Configuration program again.
5. Repeat steps 2 through 4 until all services are added and named correctly.
Regards,
.............................................................
Have fun.
Ed