...
The above error message when launching the Velocity thick client may be attributed to one of the follow reasons.
...
Velocity Services are not running on the Velocity server
...
DNS not resolving the hostname of the Velocity Server
...
Networking related issue not allowing traffic over TCP port 2025
...
Misconfigured database settings
...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Troubleshooting
Velocity Services are not running on the Velocity server
Open services.msc and ensure the Velocity services are running. The Velocity Security Domain Service specifically needs to be running to allow thick client connections.
...
DNS not resolving the hostname of the Velocity Server
Velocity connects to the Velocity Application via the hostname. Therefore, Windows DNS setting should allow the the hostname of the Velocity Server to resolve. You can try the command on the client workstation to see if DNS is resolving the hostname.
| Code Block |
|---|
nslookup VelocityServerHostName |
...
Networking related issue not allowing traffic over TCP port 2025
Using Microsoft’s TCPView from the Sysinternals suite. Can help troubleshoot potential issues with the network connection. In the below example, we can see Velocity performed a Sys Sent over TCP port 2025, but did not receive a message back from the Velocity Server.
...
Misconfigured database settings
Running the following SQL query results in the value of the what Velocity client is trying to connect to when launching Velocity. The appropriate response should be the hostname of the Velocity Application Server.
...
If the value is incorrect, then you can contact your SQL database administrator to correct the issue via SSMS, or you can reinstall the Velocity client ensuring you are entering the correct value for the ‘Velocity Server location’.
...
Lack of resources on the Velocity Server due to too many Alarms
...
See the following document on reviewing the number of active alarms and how to clear them.
...