What would cause an executable to open a LabVIEW session?

[Ray.R]

I'm not sure how to describe this in the title...  but here goes:

We inherited LabVIEW code.  The original code was used to create an executable that calls TestStand which in turn has VI modules within its sequence.  When running the original code, the LabVIEW development platform is not opened.  Everything is good and clean.

The new code causes LabVIEW to open a session as observed by seeing the icon on the task bar and seeing the splash screen when clicking on it.  If it is closed, it causes Active-X errors and the program fails.  If it is left alone, the program executes properly until it is closed at the end, when LabVIEW pops up a "Fatal Internal Error : ThEvent.cpp, line 236".

My investigation revealed that some VIs must have been edited after their original application was built.  The added complication is that those VIs are not within the project, but are called dynamically.  I did fix the complaining VIs (path changed, needed to be saved, etc), but that did not resolve the issue.

The reason for posting is because I cannot think of where to look to investigate this error.  In the meantime, I will look for any logs LabVIEW may have left behind.

[Matthew_Kelton]

Did the whole system get updated?  It is possible they forgot to change the LV Adapter settings before deployment and TestStand is setup to use LV Development for the VIs instead of the runtime.

If you don't have TestStand installed, you could try this (although it requires LV7.1 RTE): http://zone.ni.com/devzone/cda/epd/p/id/5242

It's probably doing this in the background, though:  http://digital.ni.com/public.nsf/allkb/C078C4325CD2287D8625725F007CC49F

[Ray.R · Accepted solution]

I did find the root cause for the behavior.  It was related to the TestExec.ini file.

The TestExec.ini file was replaced with the original one and the behavior dissappeared.

Wish I had more details, but there was no time to investigate further.