Wrong Run Time Engine Comes with SW Update

[Dumbhead]

I happily received the quarterly update of Labview 8.5. I was so excited and installed it immediately and created my first dll application.

when I tried to demonstrate the excellent idea of using dll to distribute my code, I was hit by an error message,

"LABVIEW.LIB was not called from a LabVIEW process". What the heck!

It turned out that the run time engine comes with the update disk is version 7.1.1.

Why did NI do this? I am such a dumbhead person and would think when I get an update it should have included everything in the package.

It is quite a bit of challenge to find out the problem, but it is definitely waste of time. Maybe NI has enough resource to support such of a waste...

[altenbach]

I've upgraded to 8.5 and did not enounter any such problems.

Your report does not include enough information to troubleshoot the problem. Did you demonstrate the dll on the same machine used to build the application or on another system? Did you built an installer?

[Dumbhead]

Here is what I have done.

I have created an dll with a test vi. the code was originally programmed with 8.2.1. Alfter upgrade to 8.5, the vi has been reload and saved. Then build the vi to a dll with 8.5 and a installer. with the builder, run time engine is loaded. no other selected.

then the installer transfer to another pc without lavview. when vb program called the function in the dll, it shows the error message.

LABVIEW.LIB was not called from a LabVIEW process

At Knowledgebase, there is an item providing the following.

-------------------------------------------------------------

Problem:
I receive the following error when I call a DLL (dynamic link library) that I built with LabVIEW 6.0:
LABVIEW.LIB was not called from a LabVIEW process
Why am I getting this error?

Solution:
The CINTOOLS that come with LabVIEW are version-specific. If you compiled a DLL for use with an older version of LabVIEW using the CINTOOLS for that version, you will likely receive errors when attempting to use that DLL/CIN with later versions of LabVIEW. In order to use the DLL/CIN in the current version, you should relink the DLL with the LABVIEW.LIB for the current version. You will have to recompile the DLL/CIN with the new CINTOOLS.

If you call an old DLL or CIN in a VI compiled as a LabVIEW DLL, you receive the aforementioned error and the application terminates. This is because the old LABVIEW.LIB does not know how to correctly locate the LabVIEW Run-Time Engine. This error may also occur if you include older versions of VIs that ship with LabVIEW in your LabVIEW DLL. You should mass compile those VIs to update them to the current version of LabVIEW prior to including them in your LabVIEW executables or DLLs (see the related entry below).

--------------------------

Then I checked the NI Software Modify/Removal at Control Panel-Add/Remove Program. In the list, there is no RUn Time Engine 8.5. But when I download the runtime engine and try to install it to PC, it seems that the engine is alreayd installed.

Now I am really cluelss what went wrong. Any idea?

[Kevin_H]

Thank you for contacting National Instruments.  The LabVIEW Run-Time engine appears to have some confusing settings here.  It looks like the Run-Time Engine(RTE) 7.1.1 is the last RTE that appears in the Add/Remove Programs list.  I have all RTEs installed here, and the last one that shows up is 7.1.1.

If you open up Measurement and Automation Explorer, and expand the Software tree, you should be able to see all the newer versions of the RTE.  If you do this, are you able to see the newer versions of the RTE, or are you still only seeing version 7.1.1?

Also, I want to clarify the problem.  You have a DLL you created in 8.2.  You upgraded the VI that uses the DLL, and created an installer with only RTE 8.5 included.  When taking the project to another computer, you recieve this error.  Is this correct?

A couple of follow up questions:

Have you tried recreating the DLL in LabVIEW 8.5?

Have you tried including the LabVIEW RTE 8.2 in the installer as well?  If the DLL has not been re-linked, this could be a workaround that may prevent you from having to recreate it LabVIEW 8.5.

I look forward to hearing back from you.

Regards,

Kevin H

[Dumbhead]

Thanks Kevin for your follow up.

No, the dll has been created all along with 8.5. the vi was originally created with 8.2.1 and before creating the dll, the vi was opened and saved with 8.5. so I belive that everything should be in 8.5. but I still got the error message. I am currently away from my office. I will attach the vi for your evaluation later.

will try the RTE 8.2 and let you know later.

[Dumbhead]

I have tried to install all RTE, 8.5, 8.2.1, 8.0,1 and 7.0.1 on my machine. it didn't help.

i did created a simple sample with 1 input and 1 output. the dll and VB application can call the dll no problem.

it is very frustrating and everything I did in within Labview environment. But the dll generated from it does not work.

the vi was originated in 8.2.1 and reopened and saved with 8.5 with even its all sub vis. then build the dll with LV 8.5 (both Forth Quarter Edition and Third Quarter edition). Showing same error all the time.

I am very disoppointed with LV now.

[Matthew_Kelton]

I have had no issues with 8.5 either, but my main reason for posting is to make sure you saw the email NI sent out about the most recent quarterly update.  The big issue is with some of the device drivers, but since they have the 8.5 DVD with Device drivers, you may want to consult this notice if you installed device drivers when you installed 8.5.

[Matthew_Kelton]

I'm a bit confused by your posts.

Does the DLL work on the machince in which you installed LabVIEW and just doesn't work on the other machine without LabVIEW?  When you say you installed the RTE's is that on your development PC or the other PC?

If you look at the installer you built, one of the subdiretories (named pyy where yy is an incrementing number) in the bin directory should have the lvxxRTE, the xx being the version number.  Obviously, it should be 85 if you and LabVIEW did everything correctly.

[Kevin_H]

Het Matt,

I do not believe the MAX Software Corruption issue applies to this situation.

To the originial poster:

Can you create this DLL in 8.2.1, and use it on another machine with no problems?  That will be a helpful piece of information to know in troubleshooting this.

Regards,

Kevin H

[Matthew_Kelton]

Kevin,

I didn't mean to imply that it was the cause of the problem.  I just noticed that he mentioned he just got his quarterly update and installed it.  I figured if he didn't get the email or didn't read it, I would let him know of other potetnial problems down the road.