For example, our MySQL connection is setup very simply:

driver={MySQL ODBC 3.51 Driver};Server=server;uid=selectaccount;pwd=*********;


It works fine for a query like:

SELECT * FROM db.table LIMIT 1;

And will return what is expected.. but something simple like

SELECT 1 FROM DUAL;

Returns:

Exception in Task: System.Exception: System.OverflowException: Arithmetic operation resulted in an overflow.
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.NFMCAMDOGBCBCKKAEOJICMPGMOLBJPKAAHOI.HJFIADPLOHNMCEFCBBMALDJFPNMAJJBMIBPA(TaskProcessClass , ConnectionClass , Boolean , String , Int32 , CommandType , Boolean , String , List`1 lstParameters, StringBuilder& , StringBuilder& , VariableReplacerClass , JobClass , TaskClass , TriggerClass , OdbcCommand& , TaskSQLOutputSettingsClass ) in C:\sourcefiles\code\VisualCronService\apiSQL.vb:line 1700
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.GKHJKBDAJKKLOCDAGMDEFBPILHJMKGOIPBBJ.Run() in C:\sourcefiles\code\VisualCronService\Jobs\TaskProcesses\Database\clsProcessTaskSQL.vb:line 69



This only appears to happen w/ MySQL connections, as similar Oracle and MSSQL setups work fine.


We are on version 7.5.0

Try using MySQL->MySQL connection type instead of ODBC.

---

If I change the Data provider type to MySQL it says it can no longer find the driver I'm specifying.. I'd guess cause its trying to use what VC uses by default? And I can't seem to take the driver parameter out of the existing connection string..

Ideally I'd like to have it use the specified MySQL ODBC 3.51 Driver to have it consistant w/ our workstations, was just hoping there was something I could change to get around whatever the exception seems to be.

So I can just change the Data provider to MySQL like you suggested, and then delete what is in the driver param, but I can't seem to remove it.. I'd just make a new one but then I'd have to switch a ton of tasks to the new connection..

Resulting string is:

driver=;server=server;uid=selectuser;pwd=pass;

Its kind of ugly. It still seems weird that I can connect successfully using the ODBC data provider, specifying the driver, but certain queries fail, doesn't it?'

I would first create a new one and verify it works (with a new Task). Maybe you cannot run the DUAL command through ODBC that way in VisualCron.

---