LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Media requested does not match media provided - BUT IT DOES?!

I'm trying to build an installer for my application.  It requires NI-CAN and NI-DAQmx.

 

The installer requested to know the location of the install media for both packages.  I downloaded the NI-CAN 14.0 installer, let the archive self-extract, and then pointed the application builder to the folder that NI-CAN 14.0 self-extracted to.  It was happy with that.

 

I did the same thing with NI-DAQmx, but now I get this bizzare error message - bizzare because it claims the requested and provided media descriptions do not match, but they clearly do!  

 

What is happening?  How do I fix it?

 

The closest thing I could find searching in the knowledgebase was this link:  http://digital.ni.com/public.nsf/allkb/830B0370F5314BF586257E0F0078884D.

However, that link said that the problem was different language packs - as far as I can tell, everything on my system is (and should be) english.

 

I downlaoded NI-DAQmx from this link:  http://www.ni.com/download/ni-daqmx-14.0/4918/en/

 

I tried downloading the run-timeNI-DAQ instead, but it didn't like that either.

 

Thanks for any help you can provide.

 

 

Message 1 of 15
(3,487 Views)

Greetings,

 

That is indeed a strange issue.  I'd recommend trying different versions of those drivers, specifically starting with the most recent versions.  It looks like a possible corruption in the driver.  

Andy G
Applications Engineering
National Instruments
0 Kudos
Message 2 of 15
(3,421 Views)

My installation disc for NI-DAQmx 14.0 seems to be broken so I tried to provide the media in some other way. I have the exact same trouble as you. Only difference is that my alert-box says:

 

"The media that you have provided is a valid installer, but it does not match the media requested.

Media Requested: NI-DAQmx 14.0
Media Provided: Ni-DAQmx 14.0
Path: ..."

 

If anyone found a quick fix for this, please tell mer :'(

 

I will start downloading Ni-DAQmx 14.1, maybe that helps. The installer of 14.1 contains 1.56 Gb of zipped media. It should be enough to provide media for the entire planet.

0 Kudos
Message 3 of 15
(3,293 Views)

Hi Mastias,

 

Unfortunately there doesn't seem to be an easy solution, as the only KB on the issue is the one presented above.  I'd recommend upgrading to the latest version of DAQmx, found here--http://www.ni.com/download/ni-daqmx-14.5.1/5271/en/.  Many times upgrading will resolve any corruption issues.

Andy G
Applications Engineering
National Instruments
0 Kudos
Message 4 of 15
(3,260 Views)

I also get a similar message. "The media you have provided is a different version of the requested media". At some point, LabVIEW decided that NI-VISA was in one of my executables. 

 

Naturally, the error message makes no mention of NI-VISA, but a process of elimination of additional installers showed that removing NI-VISA made the error message go away. 

 

Now, one might imagine that pointing LabVIEW to the NI installer for the exact same version of NI-VISA would solve this issue, but LabVIEW still insists that it's not the right version. This is true no matter which version of NI-VISA I select, including the version that I asked for. 

 

LabVIEW is notorious for corrupting its project files, so I am guessing that my only recourse is to recreate the project and hope for the best - but if anyone has any inkling of how to get LabVIEW to quit pouting, I would be grateful. 

J. Heerema, PhD - LabVIEW specialist
0 Kudos
Message 5 of 15
(1,309 Views)

Why do you say LabVIEW is "notorious" for corrupting its project files?  In the ten-plus years I've used LabVIEW, I've only had one become corrupt, and that was my fault because I let it automerge with a conflicted version in SVN.  Perhaps it is you who are notorious for corrupting LabVIEW project files?  😉

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 6 of 15
(1,299 Views)

Well, fair enough, perhaps I am to blame 🙂  I've used LabVIEW since 1988, and some of my projects are pretty huge, which might be why my mileage varies. But, looking past any personal digs, any insights on why LabVIEW has become confused about where to find NI-VISA installers?

J. Heerema, PhD - LabVIEW specialist
0 Kudos
Message 7 of 15
(1,292 Views)

@Andromeda wrote:

Well, fair enough, perhaps I am to blame 🙂  I've used LabVIEW since 1988, and some of my projects are pretty huge, which might be why my mileage varies. But, looking past any personal digs, any insights on why LabVIEW has become confused about where to find NI-VISA installers?


Unfortunately, I can only say I've heard of this before, but can offer no solution.  😞

 

My apologies, it wasn't meant to be a personal dig, so much as pointing out poor choice of wording.  Unfortunately, text doesn't have inflection, so it is sometimes difficult to convey subtleness.  For something to be "notorious" for a behavior, it has to be a widespread phenomenon, which it clearly isn't.  Thank you for being gracious in your reply.  🙂

 

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 8 of 15
(1,275 Views)

The reason is that the Installer builder can be very picky in what installer media it considers the same. The error message makes it look like only a specific major.version is expected but the Installer Builder wants the exact version, which when you download installer images can be very hard to match. Also the installer of a package that came with your LabVIEW Installer may have even a somewhat different name.

The solution is to install a newer version of that component but to watch out that you do not go to far as it may not support your LabVIEW version if the version differs more than 3 years. The downloaded installer may be already enough for that.

Rolf Kalbermatter
My Blog
0 Kudos
Message 9 of 15
(1,270 Views)

No worries - and in fairness to NI, it's been a few years since I had a rash of project file corruptions, so it may well have been fixed in the interim. 

J. Heerema, PhD - LabVIEW specialist
0 Kudos
Message 10 of 15
(1,228 Views)