Unable to start the 'Veritas Enterprise Administrator Service' (vxsvc) service due to error:"V-39-53247-1 Error while connecting to localhost.Could not connect to server. Server may be down.."
Article ID: 100045598
Updated On:
Description
Error Message
The error below is reported while attempting to connect to VEA
Error V-39-53247-1
Error while connecting to
Could not connect to server. Server may be down. Please make sure that vxsvc is running on the target host.
Checking the Veritas Enterprise Administrator Service service (start > run > services.msc) it is in starting/stopping state. If vxsvc is killed from the taskbar and attempted for startup, it reports the error below:
Windows could not start the Veritas Enterprise Administrator Service service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion
In some cases, in the Windows Application Event Log, the following error is reported, showing 0xc0000135 Exception Code and the faulting module is vxvea3.dll
Log Name: Application
Source: Application Error
Date: <date>
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: <servername>
Description:
Faulting application name: vxsvc.exe, version: 3.4.996.0, time stamp: 0x5af2adb5
Faulting module name: vxvea3.dll, version: 6.3.9600.19304, time stamp: 0x5c7f684f
Exception code: 0xc0000135
Faulting application start time: 0x01d50fffd82e3197
Faulting application path: C:\Program Files\Veritas\VERITAS Object Bus\Bin\vxsvc.exe
Faulting module path: vxvea3.dll
Exception code 0xc0000135 = STATUS_DLL_NOT_FOUND
Cause
This issue can occur due to several reasons:
1) Check the causes listed at "V-39-53247-1 Error while connecting to local host" appears after starting the Veritas Enterprise Administrator console
2) The impacted server has a long PATH environment variable preventing appropriate loading of service owing to truncation.
3) The vxvea3.dll and other files are missing from the %VIP_PATH% directory (by default: <drive_letter>\Program Files\Veritas\VERITAS Object Bus).
NOTE: The cause #3 may be seen after a fresh install or an upgrade wherein issues occur during certain package installs/updates resulting in vxvea3.dll (and other files) not being properly installed.
Resolution
1) Ensure all checks from "V-39-53247-1 Error while connecting to local host" appears after starting the Veritas Enterprise Administrator console are completed.
2) Verify the entries for the PATH environment variable from This PC > Properties > Advanced System Settings > Environment variables > System Variables Pane > Path
Ensure the two entries below are the beginning of the PATH variable:
<drive_letter>\Program Files\Veritas\Veritas Volume Manager
<drive_letter>\Program Files\Veritas\Veritas Object Bus\Bin
3)
Sample output
If not, then use the Move Up option to move the two entries to the top of the list and take a reboot.
4) If the issue persists, then perform a Repair of the InfoScale from Programs and Features (start > run > appwiz.cpl), and ensure the current logged on user is a member of the Local Administrators group.
Issue/Introduction
For Infoscale on Windows, when launching the Veritas Enterprise Administrator (VEA) , any attempts to connect to the server fails with an error for Veritas Enterprise Administrator Service (vxsvc) service
Checking the status of the Veritas Enterprise Administrator Service (vxsvc) confirms that the service is in Stopped state. However, any attempts to start the service reports a startup failure.
