DSCEngine.exe has generated errors and will be closed by Windows

[Prashant]

I am running LVDSC Run-Time System only and I am have problems with the Engine executable (error is in the main question). I realize the error I presented you with is general and vague, however it is the only error I am generating and my vi's are simple. I have three VI's, two are waveform charts reading tag data (TC's and analog input data). I have an .scf file consisting of 13 tags and a .iak file consisting of only 3 modules (network interface is serial). The engine will not start up when I call a vi even though I configured it to do so in my options (DSC>>TOOLS>>etc). I can only call the engine from windows explorer and when I do so it only runs for a few seconds and then shuts down the program
(all VI's). I have my .scat file located under my National Instruments folder and I have my VI's located under my LVDSC Run-Time System folder. There is nothing complex about what I have done. If I open the VI's they will open without the engine (and they will run but will not have the engine interface). If I stop the program and try to Launch the engine from the taskbar, it will not launch. Can someone tell me how to solve this problem and if there is some kind of discrepency between Windows and the Tag Engine.

[Aaron_G]

Prashant,

Please re-post this question in the LabVIEW Data Logging and Supervisory Control forum. Whereas you are using FieldPoint with LabVIEW DSC, the problem sounds like it is more centered around the LabVIEW DSC portion of things and not the FieldPoint side of things.

Regards,
Aaron

[Mike S. @NI]

Prashant,

First, I would recommend that you install the latest update and fixes for your version of LabVIEW DSC. You did not specify which version you have, but if you have DSC 6.0, you should definitely upgrade to 6.0.2. There are know issues similar to what you have described that have been addressed by these updates and fixes.

Once you have installed the latest update and fixes, make sure that the VI you have written will function properly before creating an executable. Once you have created the executable, you should test it on the development machine.

Regards,
Michael Shasteen
Applic
ations Engineering
National Instruments
www.ni.com/ask