07-23-2012 02:49 PM
I have 9.5.1
07-23-2012 02:50 PM - edited 07-23-2012 02:50 PM
There's no reason the DAQmx version number should make a difference. I mean I installed Labview fresh from a labview CD shipped from NI. That came with an even older version of DAQmx and I still got this bug. This is also a brand new computer with full admin rights.
But ok I will go hunting for the latest version.
07-23-2012 02:53 PM
A workaround, depending on your situation, would be to just install the DAQmx drivers on the target machine and not include it with the installer.
07-23-2012 02:57 PM - edited 07-23-2012 02:58 PM
Yeah I know. I'm only deploying this on one machine but my boss wanted me to give him 1 installer to do it all for him - you know, incase they decide to upgrade the lab computer one day.
I also wanted to get this whole issue fixed now because we'll be using LabView for most of our product developments at the lab from now on. DAQmx will surely come in handy on other machines.
But I'll just install the driver locally since I just lost a full day of work...
The fresh install of labview actually slowed down performance because I included a bunch of the toolkits just in case, I'm going to remove them now.
Thanks.
07-24-2012 11:42 AM
I have been looking into this error a little more and might have some suggestions. When LabVIEW is installed I don't think that the manifest files are removed from the computer. The error corresponds to a specific manifest.
"NI Security Update KB5Q5FJ4QW for the LabVIEW Run-Time Engine 8.2"
You should be able to go into C:\Program Files\National Instruments\Shared\MDF\Manifests and remove this file out of this folder.
If this file is not in there please let me know, but I believe this error be be directly related to this file in some way.
07-24-2012 11:58 AM
Ok I will try this soon.
Currently moved on to simply using MAX and installing everything on the target computer locally.
07-26-2012 09:21 AM
I had the same problem and also troubleshot it to the addition of DAQmx to the installation package. Similar situation in that this was the first app I tried to build on a new computer. I had successfully built this app dozens of times on my old computer, so I knew it was related to the install of LV on my new machine.
Bottom Line: Removing the file worked!
Thanks to all who looked into this and saving me countless hours and good luck to the originator of this thread!
07-26-2012 09:45 AM
I lost so many hours because of this...
LOL
Glad this helped you 🙂
12-27-2012 05:00 PM
I just had this exact problem - adding DAQmx to an installer, deleting the manifest file as highlighted worked for me. I only spent an hour trying to fix this - thanks for everyone's persistence in tackling this. I too needed a single installer. And thanks for posting the solution once it was found!
12-27-2012 06:17 PM
Glad it worked :). This actually wasted soo much of my time...