Running the Enterprise Vault Configuration fails with the error: Unable determine if the Enterprise Vault Directory Service exists. The RPC server is unavailable.
| Article:TECH125671 | | | Created: 2010-01-17 | | | Updated: 2010-01-22 | | | Article URL http://www.symantec.com/docs/TECH125671 |
Problem
Running the Enterprise Vault Configuration fails with the error: Unable determine if the Enterprise Vault Directory Service exists. The RPC server is unavailable.
Error
Cannot start the Enterprise Vault Configuration Wizard
Unable to determine if the Enterprise Vault Directory Service exists
The RPC server is unavailable
Solution
OVERVIEW
When running
the Enterprise Vault Configuration the following error pops-up on the screen and
the Enterprise Vault Configuration is unable to proceed:
Figure
1
TROUBLESHOOTING
Running a
DTRACE of EVRundll generates the following in the Dtrace Log:
335 12:33:28.390
[2364] (EVRunDll) <4992> EV:M CSnapInApp/IsLaunchedFromEVRunDll() -
Launching application is EVRunDll.exe
336 12:33:28.390
[2364] (EVRunDll) <4992> EV:M GetComputer - enter
337 12:33:28.390
[2364] (EVRunDll) <4992> EV:M GetComputer -
[EVSERVER]
338 12:33:28.390
[2364] (EVRunDll) <4992> EV:M Entering function VACOpenSCManager()on
computer EVSERVER...
339 12:33:29.468
[2364] (EVRunDll) <4992> EV:M Leaving function VACOpenSCManager() with
status: The RPC server is unavailable. ; bsDirIP =
192.168.10.1
340 12:33:29.468
[2364] (EVRunDll) <4992> EV:M CAUIProduct::CanUserRunWizard:
DoesSCMServiceExist failed with [0x000006BA] [The RPC server is unavailable.
]
RESOLUTION
Change the
binding order for the NIC that is being used for primary
communications
Check the
advanced configuration for the NIC cards in Windows:
1. Click on
"Start", "Control Panel", and right click on "Network
Connections"
2. Click
"Open"
3. Click on
"Advanced", then click on "Advanced Settings"
4. Verify that
the primary NIC is at the top of the list. This is known as the NIC binding
order. The primary NIC usually has the host name of the system assigned to it in
DNS or the host file.
|
|
Legacy ID
345808
Article URL http://www.symantec.com/docs/TECH125671
Terms of use for this information are found in Legal Notices
Thank you.