Fatal Error - LABVIEW.LIB could not locate "FDestroy Path"

[Aneesh]

Hi All,

I made my application in LabVIEW 6.1 Japanese.

I made some changes to this program using LabVIEW 7.0 (Evaluation version) and Save to 6.1.

Then I compiled with LabVIEW 6.1 and make the EXECUTABLE using Application Builder.

When I execute my application in the measurement platform a fatal error occurred.

"LABVIEW.LIB could not locate 'FDestroy Path'".

What should I do to solve this issue?

Can any one help me.!!!

Thanks in Advance

Aneesh PS

[Travis_M.]

Hello,

I think the issue here comes as a result of upgrading code, then saving for previous.  The LabVIEW.lib file is a library file used to interface external code with LabVIEW primarily to handle memory management operations.  There is a different version of the LabVIEW.lib file for each version of LabVIEW.  My guess is that  when you modified your code in LabVIEW 7, you began using the 7.0, and when you switched back you were either still calling the 7.0 version, or you had a call in the code to a function (specifically the FDestroyPath) that does not exist in 6.1.

You might want to start with a mass-compile of your LabVIEW project before you build your executable (http://digital.ni.com/public.nsf/websearch/A4C3AEF93240280A86256931006FB66C?OpenDocument).  Maybe delete or rename the LabVIEW 7 version so that you are positive that you are never using it in your LabVIEW 6 project. 

In either case, it’s probably best to find where exactly you are attempting to use LabVIEW.lib, and troubleshoot from there.

Hopefully this helps!  Please let us know how things go, and if you have any additional questions.

[Aneesh]

Hi Travis,

First of all thanks for your help.

As per your comment I changed the VI's using LabVIEW 6.1.

The modification was addition of a Strictly Typedef Enumeration Control as VI's parameter.

The compilation and Build process was smooth.

But when we RUN the executable or the Source VI, itself, the same error occurs.

Eagerly waiting for your reply.

Thanks in Advance

Aneesh PS

[Travis_M.]

Hello Aneesh,

I think I failed to ask a very important question: does this behavior only happen in built LabVIEW executables, or does it happen in the runtime environment as well?

If it happens in the development environment as well, you will need to do some more debugging to determine exactly where that function is being used.  I don't think I've ever heard of anyone using LabVIEW.lib FROM LabVIEW -- its used by your external code to call LabVIEW memory routines.  I would attempt to track down any external code which links LabVIEW.lib and make sure the right version is called.  It might also be the case that something in your install of LabVIEW 7 went wrong and modified the location of or the actual LabVIEW.lib file.  If you don't have access to the external code you might consider backing up your LabVIEW 6 code, removing all versions of LabVIEW on your computer, then reinstalling the one that it used to work with.  Before you do this, though, I would make sure that you only have 1 instance of LabVIEW.lib on your computer.  Attempt a search for that filename, and rename/remove all other copies.  If you still get this error, I'm betting either the error is in the code of your external code (i.e. you are calling a function that does not exist), or the external code requires a different version of LabVIEW.lib than is present on your computer (either a newer, or older version depending).

If it does not happen in the development environment but it does with the built application, we might need to take at a few other things to get to the bottom of this.

Please let me know how it goes!

[Aneesh]

Hi Travis,

We got all VI's as an LLB file. We convert the LLB file to folder using VI Library Manager and make the updations.

While we convert this LLB to folder and then run the appliaction, the run time error occurs.

But when we run the application before converting to LLB, it works fine.

So we are re-working on the source code, which is not converted to LLB.

Is there any problem with LLB conversion?

Thanks in advance.

Aneesh PS

[Travis_M.]

Good afternoon,

I am sorry to hear that you are still experiencing these errors.  I really think that we need to narrow down which specific node is resulting in an error.  It is possible link against LabVIEW.lib in LabVIEW code, but it is also very likely that your error could be coming from one external code module.  In your first post you mention that you are building an executable, but in a later post you mention building a llb.  If the error comes from the llb we can try to isolate it by running individual VIs in the archive.  Try to build the library with block diagrams still attached, so you can make generous use of Highlight Execution.  I am confident that once we identify the node which results in the error it will all become much clearer as to what is causing the problem.

Hope this helps!

[Aneesh]

Hi Travis,

Sorry for the confusion.

Actually we got the files for development as LLB files. Then we convert them to Folder and make the changes.

But that was not the problem.

While I try with debug option, I found that the Error occurs at "Snd Play Wave File.vi" which was supplied by our customer.

The error occurred in the Windows95/NT option's Call Library function node. Here it calls lvsound.dll.

This Snd Play Wave File.vi is NI's VI.

I replaced the VI supplied by our customer with the VI from National Instrument. (in my machine)

Now it was solved.

But I didn't found any difference between the two, in the block diagram.

Can you tell me why this happens.

Any way thanks for your help.

Thanks and Regards

Aneesh PS

[Travis_M.]

Hello Aneesh,

Glad to hear that the process of narrowing down the offending VI was able to resolve the error!  I am a little unclear on what you mean when you say “we convert them to Folder and make the changes”, and I don’t know how your customer modified the Snd Play Wave File VI.  However, I can say that that particular VI does call a DLL (the one you mentioned) which is responsible for playing the wave file.  I am almost certain that using you customer’s VI resulted in LabVIEW calling a different version of the DLL somehow.  Though both of the sound VIs look the same, check that the path to the lvsound.dll is the exact same in both your customer’s and your VI -- it could point to different versions of the dll.

Hope this helps!