LabVIEW NXG Shows Error Stating GVI Is Not Accessible

Updated Oct 30, 2018

Reported In

Software

  • LabVIEW NXG

Issue Details

When viewing errors for my GVI, I see the following error:
Private.gvi is not accessible because it belongs to another library and is not exported. An item of a library must be exported for other libraries to access it.  Visit www.ni.com/r/vi-inlining for more information.

Solution

There are two possible ways to cause this error, both relating to private (non-exported) GVIs.  

The most common way to run into this error is if your GVI calls a private GVI the caller does not have access to call.  In this case, the solution will be to create a public (exported) GVI within the same library as the private GVI to access the private GVI.  This is a common technique used when using scope to abstract away implementation and provide an API to developers.  

This error can also be found in an unexpected way that will be addressed in future releases of LabVIEW NXG.  If you follow the coding practice mentioned above and write a public GVI that contains the private GVI, this public GVI may not be set to inline.  If the public GVI is inlined, the calling GVI will show the error stating it does not have access to the private GVI and will not run.  In order to get around this error, the only current solution is to disable the option selected to inline the GVI.

WAS THIS ARTICLE HELPFUL?

Not Helpful