The vRanger machine has been rebooted, but the application will not start up correctly. You are able to see that all three vRanger services are not started correctly. You right click the vAPI service, select properties, and reenter the account information that will run the service.
Once this has been completed you see the services is running correctly, but this action is needed each time the vRanger machine is rebooted.
This can be caused by another API/service running on the vRanger machine that is using the same port as the vAPI service. If the two services are attempting to use the same port you will need to change the current configuration. The port that is being used for the vRanger vAPI service is port 2480 is this port in use by another API?service on the vRanger machine?
To verify this please complete the following steps on the vRanger machine to verify the current ports being used in the configuration.
1. With vRanger API service running, run a "netstat -an" verify port 2480 is being used.
You will also see port 2481
2. Stop vRanger API service and run "netstat -an" verify that port 2480 is no longer being used.
3. You can install something like a smallftd server on the vRanger machine configuring it to use port 2480 on the vRanger machine
4. Try to restart the vAPI service you will most likely not be allowed to the port being in use by the secondary application
You can reconfigure the vRanger vAPI port usage by making changes in the locations listed below:
1. location of the file to change:
C:\Program Files (x86)\Quest Software\vRanger\PowerShell
2. Modify both configuration files (search for port 2480 and 2481 and replaced with a new, unused port numbers in the following places
vRanger.API.PowerShell.dll (1 place to change)
vRanger.API.exe (2 places to change)
After reassigning the new unused port you should have no further problem starting the services as needed to run the application.