Visokio website     Downloads     Video tutorials     KnowledgeBase  
Sources: ODBC connection crashes? - Visokio Forums
Sources: ODBC connection crashes?
  • Alexander     Alexander March 12, 2014 6:27AM

    One of our clients is trying to connect to a ODBC Connection. When they hit the "connect" button. Omniscope closes and gives an error. Error messages just sent to Visokio.
    They are using 2.8 b1216.
  •     tjbate March 12, 2014 6:34AM
    Alex - Please check that the data source, the ODBC driver and the Omniscope installation are all aligned, either all 64-bit or all 32-bit? What repository/database are they trying to connect to? Access?
  • Alexander     Alexander March 12, 2014 6:36AM
    Both 32 bit. connection to sql dayabase
  •     tjbate March 12, 2014 6:38AM
    OK we will check the error reports...why are they using ODBC drivers, when JDBC drivers would be much better?
  •     tjbate March 12, 2014 6:39AM
    Also switching to 64-bit would be much better?
  •     chris March 12, 2014 6:39AM
    Can you use the SQL Server driver instead?
  • Alexander     Alexander March 12, 2014 6:43AM
    Because the SQL direct connection didn't work, they are trying other solutions. There is some knowledge about ODBC and none about JDBC, therefore they went for the ODBC option.

    It is a bit strange, as we (OPC) can connect to their database with a SQL connection. And they are not able to connect to this same database.

    I hope the error report will help you to solve this? Nevertheless, the ideal situation would be to get the SQL connection working.
  • Alexander     Alexander March 12, 2014 6:45AM
    I also recommended 64 bit and SQL Server. (Very pleased to hear that I share the experts opinion)

    Thanks by the way for the incredible rapid responses!!
  • Alexander     Alexander March 31, 2014 5:03AM
    Hi Thomas,

    Can you update me on the error reports?

  •     donald April 3, 2014 6:01AM
    The error is at the ODBC driver level which is crashing the java virtual machine. We have some diagnostics from Omniscope itself but not enough to be conclusive.

    Can you confirm the architecture (64 bit/32 bit) and whether you are using the Microsoft SQL Server 2008 or jTDS driver for the successful connection ?

    The error report that we have is occurring on a 32 bit OS, can you confirm the size of the dataset that you are working with just to rule out memory limitations ?

    We would also like to try connecting the 32 bit OS version using the JDBC driver in advanced mode (this device driver is the one used when you select the "Microsoft SQL Server 2008" driver.

    We can help with the correct syntax during a screen sharing session or you can email us the connections details that you use in the SQL Server connection and we can create the url for it.

    Download the Microsoft JDBC Driver 4.0 for SQL Server
    Run the sqljdbc_4.0.2206.100_enu.exe file to extract the "Microsoft JDBC Driver 4.0 for SQL Server" directory
    Copy the "Microsoft JDBC Driver 4.0 for SQL Server" ddirectory into your Program Files directory.
    C:\Program Files\Microsoft JDBC Driver 4.0 for SQL Server

    In Omniscope select the Database Table block
    Connection details
    Select database: JDBC (Advanced)
    Driver jar path: C:\Program Files\Microsoft JDBC Driver 4.0 for SQL Server\sqljdbc_4.0\enu\sqljdbc4.jar
    Driver class:
    Press Connect


    Compare to using the jTDS driver

  • Alexander     Alexander May 2, 2014 4:03AM
    Hi Donald,

    Did you find a solution for the problem with the proxy settings that prevented us to configure the SQL connection?

  •     donald May 2, 2014 1:45PM
    Hi Alexander

    We are still working on a fix for the proxy settings interfering with the connection to the SQL Server. I will post an update as soon as we have something that you can try.


It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership