03-16-2017 12:54 PM
I ran into an odd problem that I've never seen before.
I have a project. I have a module that does some datalogging / pdf stuff. If I open the project first and then open that module it is fine ... code runs, compiles, no problem. I've been using this bit of code for almost a year now.
However I noticed something odd today... if I open it from disk without opening the project first, I get the following error:
Not only that, LabVIEW then crashes on program close and I have to kill it from the task manager. I've verified this on two separate computers
03-16-2017 01:52 PM
A good one, make sure you forward this repeatable case on to your local NI support.
03-17-2017 05:13 PM
Hi BowenM,
Could you provide the code that you're using that is causing this error? Do you happen to know if it's any particular VIs/functions in toolkits or addons? If you can pare down your code to the smallest reproducing case, it will be much easier to identify the root cause.
03-17-2017 06:47 PM
I'll try on Monday. I thought it an odd curiosity and didn't dig too deeply.
03-20-2017 04:41 PM
Unfortunately, I was unable to narrow it down to a single specific bit of code and ran out of time to mess with it. If someone from NI wants to investigate more I can do some screen sharing or something, but I'm not going to post an 1800 vi project 🙂
03-21-2017 09:32 AM
Hi BowenM,
Even if you don't have an active subscription to our Standard Service Program, you can still create a Service Request and speak directly with an Applications Engineer like myself if you are trying to report a bug.
Go to the Service Request Manager
If you have a service program membership, you can create a Service Request from here and submit it. If you do not, look under
"No, I do not have a service program membership. I need to:"
and select "Report a Bug"
You will then be able to enter your product information (LabVIEW Distribution and Version, OS, etc.) and a brief description of the behavior you're seeing.
You can also reference this forum thread to help give more context to the engineer who will be helping you out. However, just as a fair warning, they will probably ask just as I have done for a narrowed-down or simplified case that can be more easily shared, because in order for R&D to characterize the behavior and find a root cause they generally require that the bug be reproducible on multiple systems.
If you'd like to continue troubleshooting this error, please feel free to file a Bug Report service request. Let me know what you decide. Thanks!
Regards,
Jason O.
Applications Engineer
National Instruments