Hi everyone. I’m having trouble with runs being aborted by VWorks due to some database issues/corruption? with the mySQL. I was wondering if anyone has done an uninstall and reinstall, and if there are any issues or watchouts?
I’ve exported my database through VWorks and have taken a full mySQL backup using the mySQL tool for that.
I’m using a Bionex branch of VWorks with mySQL 5.1.44. As well as ODBC 5.6.1.
Hi, I’m not familiar with Bionex VWorks, however which error do you get to make yiu think that the SQL database is corrupted? Can you access the inventory (in case your version has the inventory…)? Please let us know.
I will post the error when I get back to work tomorrow, I have the logs saved. However, it seems that every time the database errors, it kills the mySQL service. That is what is making VWorks unhappy. I’m certain the error stems from the database and not VWorks itself. I usually have to go into task manager services and restart the mySQL service, then VWorks will be happy for a few weeks. But the issue comes back eventually.
Setting up [Agilent’s version of] VWorks from scratch is pretty easy. I’ve done it many times and never had a problem with MySQL.
Here’s a guide for MySQL 8.0, although the latest one I did (only a few months ago) was still on MySQL 5.x. I think the steps are fairly similar. But you can also do some Google-fu to find the one you need.
Inactivity timeouts were always common between the ODBC Connector and the MySQL database. If you were to leave the VWorks application open without running a protocol overnight, it was expected that the first protocol you would run would abort due to the connection timeout. You can eliminate the timeout errors by increasing the timeout; I don’t remember where this setting is and do not have either software installed.
Interesting, which version are you referring to? At least with the Agilent version I’ve never heard of timeout issues in the last 8 years, but that’s good to know in case someone reports a similar issue!
I’ve had the problem that Pete describes on an install direct from Agilent. However, after my most recent setup of VWorks on a fresh Windows install I haven’t had the issue. I do wonder if checking the “Enable automatic reconnect” in the ODBC connector setup solves that issue and if it isn’t checked when Agilent sets up the system? See page 17 of the setup guide I linked earlier.