System Level Exception When Calling LabWindows/CVI .obj File From TestStand SequencePrimary Software: TestStandPrimary Software Version: 3.0 Primary Software Fixed Version: N/A Secondary Software: LabWindows/CVI Run-Time Engine
Problem: Why do I get a System Level Exception when I try to call a CVI .obj file from my TestStand sequence?Solution: This behavior can be caused by Data Execution Prevention (DEP). DEP is a Windows security feature that prevents code from executing in certain situations. By default on Windows XP and Vista, DEP is set to 'Opt-In.' This means that any process can allow itself to be bound by the rules of DEP. Usually only system processes have this option set, but you can build programs which 'Opt-In.' The TestStand Sequence editor does not 'Opt-In' to DEP but if you are creating a custom User Interface, and you are having this problem, you can disable DEP for your program. There are two steps to this process:
Some Data Execution Prevention featuress are based in hardware. Only computers whose hardware supports DEP can use all features. Therefore, even with the same software settings, you may experience different behavior on different computers
Related Links: MSDN Linker Options: /NXCOMPAT Wikipedia: Data Execution Prevention Attachments:
Report Date: 04/07/2008 Last Updated: 06/11/2009 Document ID: 4K69OJT3 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

