KB Article #182149
VA 5.2 fails to start with the error "Could not start 'ves' service. Error= ERROR_INVALID_HANDLE"
Problem
During a new or upgrade install on Windows to a version of Validation Authority Server 5.2, the VA Server cannot be started from the VA Administration UI. An error is given stating that the server could not be started, and the admin log has the message:
Could not start 'ves' service. Error= ERROR_INVALID_HANDLE.
Resolution
This can result from a permissions issue with starting the Axway Validation Authority service from the Axway VA Admin service when it is running as the Local Service user, which is the new default in version 5.2, when VA is unable to change the permissions during install or upgrade due to security restrictions. Changing the user for the Axway VA Admin service to Administrator or another user with equivalent privileges will resolve the problem.
To change the service to run as Administrator:
- Go into Windows Services panel.
- Stop the Axway Validation Authority service if it is running.
- Stop the Axway VA Admin service.
- Right click on Axway VA Admin service and choose Properties.
- Go to Log On tab and set the userid and password for the Administrator account then click OK.
- Start the Axway VA Admin service and make sure it starts successfully.
- Go into VA Admin UI and start the VA server from there.