error "variableRunTimeInterfaceRegistry"

[julienAu]

Dear all,

does someone already faced up this message ??

 

"Compiler error. Report this problem to National Instruments Tech Support.

NULL VariableRunTimeInterfaceRegistry"

It happens when i try to save vis. My project use Windows 10, LabVIEW 2020, and associated 2020 add-ons: Real-Time, FPGA, EtherCAT.

Thanks in advance,

Julien

[Bob_Schor · Accepted solution]

What did you do to provoke this error?

• Does it always occur whenever you open LabVIEW 2020 and open or create any VI?
• What specifically did you do just before this error occurs?
• Is there a specific VI that you are editing/saving/running that provokes this error? 

A short story -- a few years ago (probably 13 or 14, as it occurred with LabVIEW 2011), I had a VI that I wrote that every time I moved a wire on the block diagram, generated a "We apologize for the Inconvenience" announcement, and crashed LabVIEW.

I tried to fix this myself, but ultimately ended up sending the code to NI.  I then rewrote that (really trivial) VI from scratch, and the problem went away.  I happened to be at NI Week that August, and asked one of the NI Insiders giving a presentation if they ever found the bug, and she said "Yes -- are you the one that reported it?".

So if you have code that reliably causes a crash, do attach it for us to look at, poke at, and maybe help you fix it or at least work around the problem.

Bob Schor

[julienAu]

Dear Bob, 

thanks to your advices, I found a solution.

The error came from a VI with EtherCAT variables. I rewrote it from scratch as you mentionned. The error has gone... maybe I did something stupid on my VI, that I don't remember. I don't really understand what happened, but now it works...

Have a nice day !

Julien

[Bob_Schor]

What probably happened is that there is an extremely subtle bug somewhere in the LabVIEW compiler that if the barometric pressure is exactly right, and you move a wire in just the right way, LabVIEW will Apologize to you.  You can't find the bug, but if you simply re-write the code from the beginning, the barometric pressure will have changed, and the bug will go away.  When the Developers tweak the code ever so slightly for the next release, the dependence on barometric pressure will disappear and everyone will be happy ...  [That's at least my experience with LabVIEW 2011 ...]

Bob Schor