During one of our runs on the Vantage, we received the following error that caused the method to abort. Has anyone run into this error before?
Main - error; An error occurred while running Vector. The error description is: Cannot track the action move volume. (An error occurred while running Vector. The error description is: Cannot begin transaction. (The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.) (0x60 - 0x12 - 0x15)) (0x61 - 0x1 - 0x52)
For context, we have successfully ran the method multiple times without error and nothing was modified before the current run.
This error occurs when communication between VENUS and the SQL Server is lost during a run. This can occur for a number of reasons including network issues (if the SQL server is hosted on a different server/PC), interference from a third-party (IT or antivirus software, or a different user), or a large LogFiles folder.
The first option of network instability is uncommon, but confirming the location or the SQL Server can help rule this in or out. If your server is located on the PC running the instrument (i.e. localhost), then this would not be the cause.
For interference from a third-party, this one is more difficult to troubleshoot. You will likely need ITs involvement to look at any events that might’ve occurred on the PC around the time of the error. If any of these events included antivirus scans or other similar software scans, this can lead to interruptions of the SQL Server service or data transmission.
The easiest option is to check the size of your LogFiles folder, and archive/delete any files that are no longer needed. If your folder is on the order of multiple GBs, then it is due for a cleanup. This can be done using the cleanup options found in this post.
In some instances, simply restarting the PC on a regular (minimum weekly) basis can help prevent this issue, as it clears up PC resources and can improve SQL Server service stability.
Thanks Dan! I’ll try cleaning up the log file and asking our IT for any scan events around the time of the error. I believe our server is on the same PC but I’ll also double check. Appreciate the help!
Hi @DanHartman_Hamilton we recently see an uptake in these error happening on Venus 6.2.3.(4706) and it is getting to a point that I think I know where the issue comes from, but I can’t prove it.
We have a Win11 system (latest updates) with Venus 6.2.3 freshly installed. We have user accounts managed via entra and we execute Venus with these accounts (lab operator/ method programmer roles assigned).
The methods executes sometimes fine. But sometimes…out of the blue we get these errors. It happend now two times on two completly different steps. We took a backup of the logfiles folder and removed the old ones. The database has been emptied and still we see these issues.
My next move is to migrate the databases to a dedicated SQL server, but before I do this. What other causes are there for these randomness.
With how the SQL Server is configured for VENUS by default (locally hosted, using Shared Memory, allowing multi-user connections) there aren’t many other causes. The things to look at are:
Software or policies that would restart the SQL Server Service mid-run, lock critical files, cause memory insertion, or flag complex queries
Limited resources: low memory, 100% CPU usage, disk full
Too many connections to SQL server causing latency
The next best steps for troubleshooting are checking the Windows Event Viewer and SQL Server Error Logs for entries around the time the error occurs to find specific information regarding the broken connection itself. If you’d prefer, you can share them with me and I will review to see if anything stands out.