NI TestStand Log Results Run-Time Error

[MechUnit]

Hello Community,

I am using TestStand 2016 32-bit & Labview 2016 32-bit

I am working with the TestStand Simple UI in Labview.

Recently I have been getting this error. I have never seen this error before and have been running my test code for years. The UUT_RESULT is logging correctly, but the STEP_RESULT is not. Please see attachment for the error message.

I have researched the error code, but could not find an answered solution.

Any help would be greatly appreciated.

Thank you

[Chuan19]

Is this only happening when using the LabVIEW VI?

You can try placing breakpoints to indentify on which step it's failing. 

Regards.

[MechUnit]

I have not tried it another way, only with the TestStand Simple UI run in Labview.

I attached two additional pictures of when the test prompts me where the Run-Time Error comes up.

[Carolynn.V]

Hi MechUnit,

Has the size or nature of your application changed recently? Another forum post addresses this error, and it seems to be on the ODBC driver side. I've linked the forum here for more context. Let me know if this information is helpful!

https://forums.ni.com/t5/LabVIEW/Time-out-error/td-p/647784

[MechUnit]

Hey Carolynn,

The size of my application has not changed. The error happens irregularly.

I read the post you sent and located the "DB Tools Execute Query.vi" and "DB Tools Set Properties.vi" in "C:\Program Files (x86)\National Instruments\LabVIEW 2016\vi.lib\addons\database\Auxilliary.llb". Are you able to show me an example of what Brian was explaining? I do not completely understand and would like to give it a try.

[Carolynn.V]

I would recommend starting with the second step that Brian recommended, as it would be a little bit easier to implement! This just requires changing the value wired to "command timeout" under "connection properties" in the DB Tools Set Properties VI (as linked below).

"DB Tools Set Properties VI"

http://zone.ni.com/reference/en-XX/help/370016F-01/lvdatabase/db_tools_set_properties/

The other troubleshooting step would require opening up the "DB Tools Execute Query VI" in LabVIEW and adding a while loop around the invoke node. 

"DB Tools Execute Query VI"

http://zone.ni.com/reference/en-XX/help/370016F-01/lvdatabase/db_tools_execute_query/#examples

[MechUnit · Accepted solution]

I tried increasing the command timeout, but it was taking over 40 seconds in order to save my data to the database when it use to take a second. I ended up solving the issue and figuring out that the problem was in my TestStand Schema. The statements within the schema have a section called "Command Text". My query said "SELECT * FROM MYTABLE", which caused my data logging to slowdown as my table grew over time. In my sequence file I only cared about adding records to the database and did not need to select any records, but the Command Text can't be left empty. To solve my issue, I made the Command Text query select only one record by writing "SELECT TOP 1 * FROM MYTABLE". Now my database logging is fast again with no timeout.

Thank you for your time and help!