lvdaq problem with executable

[tjw2]

Updated to Labveiw 8.0.1 recently and did the mass compile. When I
generate and executable with installer, an error saying that lvdaq.dll
is not a valid labview file shows up. Anyone know why??

TJW

[tjw2]

Let me clarify one thing. The error shows up after installing the
program on another computer when I try to run the executable.

Thanks for any help on this one.

TJW

On Mon, 29 May 2006 18:45:27 -0400, tjw <tjwhitaker@charter.net>
wrote:

>Updated to Labveiw 8.0.1 recently and did the mass compile. When I
>generate and executable with installer, an error saying that lvdaq.dll
>is not a valid labview file shows up. Anyone know why??
>
>TJW

[Travis G.]

Hello TJW,

Could you create executables that performed DAQ operations prior to upgrading your software?  Do you have the correct LabVIEW Run-Time Engine and DAQ driver installed on your target machine?  You can easily check what National Instruments software you have installed on a machine by going to Measurement & Automation Explorer (MAX), and expanding the Software section.  Verify that the correct version of the LabVIEW Run-Time Engine and NI-DAQ driver appear.  You can include the DAQ driver and Run-Time Engine with your executable by creating an Installer using the LabVIEW Application Builder.

Also, are you logged in as the Administrator on the system on which you are trying to run the executable?  One thing to check here is the user rights for the C:\Program Files\National Instruments directory.  Browse to the National Instruments directory, right-click on it, select Properties, and go to the Security tab.  Ensure that whatever user you are logged in as when trying to run the executable has 'Write' privilages enabled for this folder.  Although no files are written to in this folder, on some machines 'Write' privelages must be enabled for a program to access the DAQ dll.

Let me know if this helps,

Travis G.
Applications Engineering
National Instruments
www.ni.com/support

[tjw2]

Travis G.

Thanks for the reply. Very Strange. I couldn't find your message using my newsgroup application. Anyway - to answer your questions:

Could you create executables that performed DAQ operations prior to upgrading your software?  Yes, in versions 7.x. I didn't try in 8.0 before updating to 8.0.1.

Do you have the correct LabVIEW Run-Time Engine and DAQ driver installed on your target machine?  Yep, I used the one that came with the LV 8.0 distribution.

You can easily check what National Instruments software you have installed on a machine by going to Measurement & Automation Explorer (MAX), and expanding the Software section.  Verify that the correct version of the LabVIEW Run-Time Engine and NI-DAQ driver appear.  Labview 8.0.1, NIDAQmx 8.0.0f0, Traditional NIDAQ 7.4.1f4.

You can include the DAQ driver and Run-Time Engine with your executable by creating an Installer using the LabVIEW Application Builder. That is indeed what I have been doing.

Also, are you logged in as the Administrator on the system on which you are trying to run the executable?  One thing to check here is the user rights for the C:\Program Files\National Instruments directory.  Browse to the National Instruments directory, right-click on it, select Properties, and go to the Security tab.  Ensure that whatever user you are logged in as when trying to run the executable has 'Write' privilages enabled for this folder.  Although no files are written to in this folder, on some machines 'Write' privelages must be enabled for a program to access the DAQ dll. I am installing this on a WIN2000 OS (hmm, created on an XP system; could that be an issue??) and the properties dialog box doesn't have a Security Tab. I am signed on as the Adminstrator. I also went in and made the NI directory shared temporarily with everyone having write authority (I know its not the same but I'm getting desperate here). Still get the problem.

Lvdaq.dll is being put into the DATA directory in the build. I've made sure all other copies of Lvdaq.dll have been deleted. Still have the problem.  Arrrrghhh!

TJW

[Travis G.]

Hello TJW,

Thanks for looking into the questions I asked in my previous post.  If possible, could you attach a copy of your executable to this post so that I can try running it on my machine?

Also, I know this sounds strange, but I'm finding some documentation of an issue similar to this where a second mass compile solved the problem.  Try mass compiling the vi.lib directory located at C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib.  You can initiate a mass compile from within LabVIEW 8.0 under Tools > Advanced > Mass Compile, which will then ask you to specify a directory to mass compile.

If this still doesn't solve the problem, my last recommendation is to upgrade to the latest version of the NI-DAQmx driver (8.1).

Let me know if any of this helps, and I'll see if I can replicate the behavior with your executable on my machine.

Regards,
Travis G.
Applications Engineering
National Instruments
www.ni.com/support

Message Edited by Travis G. on 05-31-2006 04:03 PM

[tjw2]

Travis,

This is getting more and more strange. I tried the mass compile vi.lib and got a large number of errors (33 pages when I pasted the status log into MSWord). I checked a few of the "bad vi's" to see what was going on and, for example, "VISA Bytes at Serial Port" had an unwired node (actually, it had no wired nodes, and no controls or indicators). Another one that I checked had an unwired node and it had a comment in German. I don't think I had any errors on the first mass compile.

Obviously it is time for a complete reinstallation (sigh!). I will get the new install finished tonight and again download the 8.0.1 update in case the last download had problems. I'll get the mass download started tonight and let you know tomorrow if things have improved. Or maybe I just just forego the update to 8.0.1 for now and see if the executable works.

Tom W.

[Travis G.]

Hello Tom W.,

That indeed sounds very strange.  Unfortunately, as you've stated, your best bet here is to perform a compelte uninstall/reinstall.  Let us know how this turns out, and if you see any similar errors with future executables.

Regards,
Travis G.
Applications Engineering
National Instruments
www.ni.com/support

[tjw2]

OK - I uninstalled everything associated with LV8 and then reinstalled. I got the following error

Error 1402. Could not open key: HKEY_LOCAL_MACHINE\Software\Classes\LVDB.Application\CLSID. Verify that you have sufficient access to that key, or contact your support personnel.

When I checked the CLSID, TOM (my cleverly named signon name) had write permission but ADMINISTRATORS did not. So I created ADMINISTRATORS, gave them write permission and installed Labview 8 without further errors. Then I updated to 8.0.1 and that seemed to go OK. Upon opening LV8 after the 8.0.1 update, a message telling me I had to mass compile came up - so I started the mass compile. After only about 20 minutes, an error popped up saying that Labview had experience a fatal error and would have to shut down. So I redid it all and got back to the same place and got the same message after the same amount of time into the mass compile. So what the heck - I decided to try to go ahead perform another mass compile of vi.lib directly. When I tried that, I got the same errors described previously (I checked the first 8 or so; they were identical to the errors from the previous attempt to directly mass compile vi.lib).

I now suspect a bad disk. I will be contacting NI tomorrow to see if I can get another one. If anyone has in other idea about what could be going on. I would like to hear it. Oh, by the way, I can create an executable and installer, and the installation completes on a separate machine without error. But when I try to run the executable, I get the same LVDAQ error described previously.

Has anyone ever checked the percentage of programmers that have no hair left?????

TJW

[Travis G.]

Hello Tom W.,

So after some more research, I've found some resources that may shed some light on this situation.  Take a look at this Knowledgebase:

KB 3VG9LHOH: Crash in lvdaq.mxx While Mass Compiling LabVIEW 8.0.1 

This KB recommends upgrading to NI-DAQmx 8.1 before mass compiling.  The link to where to download NI-DAQmx 8.1 is in the related links section of the KB.  I apologize, I should have found this information for you sooner and for you and your hair's sake...

Also regarding the issue with the registry keys, this is discussed in this Knowledgebase:

KB 3SSEHU0F: Error 1402 When Installing LabVIEW 7.1 or 8.0 

If you run into that problem again, follow the steps listed in that KB.

Again, I apologize for the inconvenience, but if you have the patience, I would recommend a reinstall using version 8.1 of the NI-DAQmx driver.

I hope this helps,
Travis G.
Applications Engineering
National Instruments
www.ni.com/support

[tjw2]

I just uninstalled all the LV8.x and NIDAQ8.x, then reinstalled LV8.0 and NIDAQ8.0. Then updated to NIDAQ8.1, then updated to LV8.1 and mass compiled --- still have the same problem. By the way, I downloaded new copies of everything, including LV8.0 before reinstalling. Whatever the problem is, it must be related to some file that is hanging around after the uninstall. Do you have something to really uninstall everything? I talked to someone at NI on Friday and they said they were going to send me a file to remove everything but it hasn't shown up yet. Will there be a problem with activating LV8 after a total uninstall?

By the way, I did not uninstall LV7.1.1. Could that be an issue?

I've gone through the uninstall/reinstall bit 4 times now. I would really like to get this solved.

TJW