dynamic IUse Node has no referenced VI to call

[BrentSchenk]

i tried to convert my labview 2009 project to labview 8.6.  The conversion appeared to work and that finished up so i closed labview 2009 and did an open with labview 8.6.1 on the newly created project.  On opening i get the following error:

compiler error.  Report this problem to National Instruments Tech Support.

Dynamic IUse Node has no referenced VI to call.  Node = 0x0B6245DC

would anyone be able to explain this?  Also, does posting this count as reporting it to NI Tech Support.  Thanks for any help!

Brent 

[Ipshita_C]

Hi Brent,

This sounds like an internal error and I would suggest going to this link and reporting it so that this can be investigated further. You can create a support request through either phone or email. Hope this helps!

Ipshita C.

[brentschenk2]

I'm getting this same error message now for a completely separate issue.  I am just trying to copy a project file and open it up somewhere else.  ive tried to my harddrive, a flash drive, and a different PC.  what could be the cause of this?  when i try to run the project it just says the VI will not compile.

[Daniel-H]

Brent2,

Like Ipshana recommended for Brent1, this is an internal issue that you're going to need to discuss further with an engineer.

Daniel

[brentschenk2]

both posts are from the same person, i just couldnt remember how to login to that account.  anyways, i opened up a ticket Reference#7329028.  Luckily i have a service contract so hopefully we can get this resolved quickly.  I found that i can save as to a different location on my PC and open it successfully.  I tried doing a save as to a flashdrive and opened it successfull, but when i took that flash drive to another PC it gave me the same error.  Somewhere in there, LabVIEW has a path set somewhere that it needs and is not getting when the files are moved.

[brentschenk2]

If anyone is curious as to how that previous one turned out, what i needed to do was to use the built in build functions in labview to make the whole project into a zip file and it worked.

I just recently had the same problem except it was on my source computer and it was occurring in previous versions of code as well (in clearcase YUCK!).  anyways, the solution to this problem was to force the entire VI hierarchy to recomple via:

http://digital.ni.com/public.nsf/allkb/C1C6FE6231966E278625661F0054A970

hope this helps anyone in the future!

[SerjsVIEW]

Hi Guys!

I just encountered a similar problem after trying to use LV 2015 out of the box with my project written on LV 2014.

The sollution was stupidly simple:

1. I looked for the broken VI (conveniently it was the main VI)
2. Pressed CTRL and clicked on the broken run button to force compile.
3. Enjoyed a program that compiled again!

Thanks for the tip!