I'm assuming that if you have a service request number, you have already contacted NI's phone support? Did they have any information on this? Many times, these *.cpp errors can be very hard to track down. Here is how I go about it (and have been successful so far!):
1. Save a backup copy of your VI.
2. View the Block Diagram. Delete a small chunk of the code. Modify the VI so that it is again runnable. Use constants, etc instead of the code that used to be there.
3. Run the VI. If you still get the error, then you now know that the piece of code you deleted was not causing it. If the code runs, then you know that chuck of code did cause the problem.
4. If you still get the error, remove some more code from the Block Diagram and run it again. Continue to d
o this until you find which part of your code is causing the problem.
5. Once you have found the chuck of code which causes the error, follow highlight execution mode through this, and watch all data, until you determine exactly what is causing this error.
This is the most effective way I have found to hunt down these errors. Once you have detailed info on what region of your code causes the problem, NI can usually track it down for you.
J.R. Allen
