2013 Citadel ODBC SQL Crash

[Beardsell]

Retrieve Citadel Data via ODBC SQL produces a crash in the nilxtcor.dll file if the query is executed several times (appx 1000).  The amount of data requested varies the crash point.  Wondering if anyone has seen this behavior.  We saw this problem in 2011 and NI produced a fix.  Also the query test runs 5-10x faster in 2012DSC vs 2013DSC.

Our test:

We tried extracting 1 to 10 numeric variables over a 5 min span with a 10sec interval.

OS: Tried Windows 7 32 and 64bit

Applications: Standalone VB.Net exe, Labview Development mode or Labview standalone exe produces same result

Example of Query:

SELECT IntData.LocalTime,
 IntData."GRF-WKS225/OsmoseHist/tank1Volume"
FROM IntData IntData
  WHERE IntData.IntInterval = ' 00:10'
  AND IntData.LocalTime > ' 2014-05-14 13:30:00'
  AND IntData.LocalTime <= ' 2014-05-14 13:35:00'"

[DECONN]

Hi Beardsell,

I have not personally seen this issue but I had a few questions to explore the crash further. Is this a complete crash with an error report or are you receiving an error dialog/code of some sort? Are you able to reproduce it consistently or does it appear to be slightly random? Has all the testing been done on the same development system?

[Beardsell]

The program will freeze without an error code.  Windows Event Viewer is where I saw the nilxtcor.dll file as the faulting module. We can reproduce the problem.  Testing has been done on two different machines with different Citadal Databases.

During the testing we open-query-close then repeat.  The problem is occurring during the call to the DB Tools Open Connection.vi.  I will be doing additional testing today to see which component of that VI is problematic.

[Beardsell]

Digging a little deeper into the DB Tools Open Connection VI. The Invoke Node Connection_Deprecated-Open is where the error is being generated. The following Exception was produced:

Error -2147418113 occurred

Possible Reason ADO Error: 0x8000FFFF

[DECONN]

If I’m not mistaken, this is the Database Connectivity Toolkit. Which version are you using? I haven't been able to locate that particular invoke node yet but I'll dig into that VI some more.

[Beardsell]

Correct.  The module is the Database Connectivity Toolkit 2013.  We are also setting up a 2012 environment to see if we get similar results.

Scott

[mikeporter]

Step 1: Don't ODBC, use ADO

Step 2: Don't use the Database Connectivity Toolkit. Check here for alternative.

Mike...