Vector error during run causing method to abort

Hamilton (Venus)
1

Hi All,

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.

2

Hi @MariaNParsebio,

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.

Thank you,
Dan

4 Likes
3

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!