Jump to content
Sign in to follow this  
ColinR

Error building package : Error 74 on Package: OPEN

Recommended Posts

Hi.

 

I am building my first .lvlib for distribution using VIPM - the free, 2010 version.

 

The library has a few application vis and a couple dozen lower-level vis, including a sub-project. It also relies on an installed .dll that is not being included as part of the package. I have opened all files again to ensure they are executable and there are no broken dependencies.

 

I receive the error below and have no idea how to debug. I cannot seem to locate a log or get any google hits on the error.

 

Thanks,

C

 

Error Details:

Code: 74

Source: Invoke Node in Library.Open__ogb.vi->Generate Resources Copy Info__ogb.vi->Build Application__ogb.vi->Build Application from Build File__ogb.vi->Build Application from Build File__ogb.vi.ProxyCaller

<APPEND>

Method Name: Library:Open

Share this post


Link to post
Share on other sites

Just upgraded to 2012. Same problem.

 

What version of LabVIEW are you using?

Can you try clearing your object cache in LabVIEW?

See here:

http://zone.ni.com/reference/en-XX/help/371361H-01/lvdialog/clear_object_cache_db/

 

You are also welcome to send your zipped code to our support here and we can work on it on our end to find the problem for you:

Submit JKI Support Ticket

 

 

 

Share this post


Link to post
Share on other sites

What version of LabVIEW are you using?

Can you try clearing your object cache in LabVIEW?

See here:

http://zone.ni.com/reference/en-XX/help/371361H-01/lvdialog/clear_object_cache_db/

 

You are also welcome to send your zipped code to our support here and we can work on it on our end to find the problem for you:

Submit JKI Support Ticket

 

I've cleared the object cache. No luck.

 

I'm on a fresh install of 2012 Developer 12.0f1 . One thing I did not realize is that 2012 comes with VIPM, so I installed an older version, then 2012. Not sure if this could create any problems.

 

I'd prefer not to send unlocked code, and I'm unsure if a library of protected vis will do you any good. If it will, I'll send it over. Is there no way to get a more detailed log of where it is erroring out through the applications?

 

Thanks.

Share this post


Link to post
Share on other sites

See here for some common package building issues:

http://support.jki.net/entries/21417213-troubleshooting-package-building-problems

 

According to this, the error indicates that "Memory or data structure corrupt."

 

No idea what that means. VIPM tries to open the library (I assume you use LVlibs) and the action generates this error. I wonder if this is related to the DLL call. You can try paring down your code until the problem goes away.

Share this post


Link to post
Share on other sites

See here for some common package building issues:

http://support.jki.net/entries/21417213-troubleshooting-package-building-problems

 

According to this, the error indicates that "Memory or data structure corrupt."

 

No idea what that means. VIPM tries to open the library (I assume you use LVlibs) and the action generates this error. I wonder if this is related to the DLL call. You can try paring down your code until the problem goes away.

 

Thanks. I'll try building it piecewise. Do you happen to know if it's possible to build VIs with dll function calls without including the dll?

Share this post


Link to post
Share on other sites

Got it sorted.

 

Had a project in a subfolder that called the library itself. I would think that LV would figure out this structure problem, but no. Anyway, all better.

 

Thanks.

C

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.