Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

When an operator first launches to Velocity, the first task is to make connection to the Velocity database in SQL Server.

image-20240718-211200.png

Velocity reads the value called SQL Server at the follow Windows Registry location and tried to make a connection to the SQL instance. 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Hirsch Electronics\Velocity\Client
image-20240718-211436.png

Troubleshooting

  • Check to see if the the SQL Server service is running. If it is not running, start the service.

image-20240718-205723.png

  • Using Microsoft’s TCPView from the Sysinternals suite. Can help trouble shoot potential issues with network connection. In the below example, we can see Velocity performed a Sys Sent, but did not receive a message back from the SQL Server.

image-20240718-212048.png

  • Launching SQL Server Management Studio and trying to connect to the SQL Instance can also provide useful information regarding reasons you are unable to connect to the SQL Instance.

image-20240718-212619.png

  • If you can connect to the SQL Instance but you cannot view the Velocity database, it might be lack of permissions to the Velocity database. You should work with the SQL Sysadmin to add the appropriate permissions to the Velocity Users group.

image-20240718-215134.png

image-20240718-212953.png

  • No labels