CVI Build Problems

[Double_D]

Here's the build debug output.

[Mert_A.]

When you changed the source of NI-488.2 to the Aug 2007 driver CD, other products were automatically re-sourced to that distribution as well.  It appears that Measurement & Automation Explorer 4.3, which resides on disk 2 of that distribution, did not have its source path updated properly.  There may be other products on disk 2 that also were not properly updated.

To resolve this, go the the Drivers & Components tab, click on NI Measurement & Automation Explorer 4.3 in the list, then take a look at the Component Source on the right portion of the tab.  If the name does not correctly identify disk 2 of the August 2007 driver CD, or the path is not E:\, then try to change the source to disk 2 of the August 2007 driver CD.

If for some reason that doesn't work, open the file Program Files\National Instruments\Shared\MDF\Bin\MDFInfo.xml and replace all occurrences of

<distLocation></distLocation>  (or it may be <distLocation/>)

with

<distLocation>E:\</distLocation>

Let me know how it goes.

Mert A.
National Instruments

[Double_D]

When I looked at the Edit Installer dialog, there was no path listed for NI-MAX.  I changed the MDFInfo.xml file as you suggested and restarted CVI.  The MAX path was now shown as E:.  I then attempted the build again.  It got much farther this time, but asked for Disk 1 of the November 2007 Device Drivers distribution (this was after I had already been prompted to insert the August 2007 Disks 1 and 2 earlier).  I reviewed the Edit Installer dialog once more.  This shows that the source for NI-DAQ is the November 2007 Disk 1.  Since I am not installing NI-DAQ with this application (the checkbox is not checked), I'm not sure if this is the problem or not.  I tried to change the source with the August 2007 Disk 1 installed in my CD drive, but was unsuccessful, getting a "selected distribution does not contain NI-DAQmx 8.6...". 

Do I need to uninstall the NI-DAQ version from the November 2007 disks?  Following the procedure provided by NI for fixing the problem with the latest DAQ version did not mention uninstalling and going to the previous version.

[Mert_A.]

Most likely, there is some anonymous support component that is depended on by NI-488.2 (or some other checked product) that is still being sourced from the November 2007 Driver CD.  It is likely that the support component was upgraded by the Nov DCD, and so cannot be sourced from the Aug DCD anymore (the distribution builder can only include versions of components that are currently installed on your system).  I am mostly sure that the MAX database corruption issue associated with the Nov DCD is limited to the core DAQmx components, and are not dependencies of NI-488.2.  In that case, it is safe for you to go ahead and provide the Nov DCD when you are prompted for it. 

It is not safe to deploy DAQmx 8.6 from the Nov DCD.  Note that the reason you cannot change the source of NI-DAQmx 8.6 to the Aug DCD is that it is not exactly the same version. It was rebuilt in between the two releases, and now the specific version that is installed on your system can only be found on the Nov DCD.  The implication is that if you would like to safely include DAQmx in any of your distributions, you must uninstall it and reinstall from the Aug DCD (or any other installer previous to the Nov DCD).

I will try to confirm for you that the issue is caused by a core DAQmx component, and I'll let you know when I find out.

Mert A.
National Instruments


Message Edited by Mert A. on 12-12-2007 04:32 PM

[Mert_A.]

As I stated earlier, the problem is limited to DAQmx 8.6 from the Nov DCD. You can safely distribute anything else from the Nov DCD. I would recommend that you upgrade DAQmx to version 8.6.1, which can be downloaded here.  Once you do that, DAQmx will be sourced from that distribution, rather than the Nov DCD.  Note that before you run the DAQmx 8.6.1 installer, you should burn it to a disk or move it to a directory for permanent storage.  If you were to run it from a temporary location and then move/delete it, you would likely have to point CVI to it the next time you build a distribution.

Mert A.
National Instruments

[Mert_A.]

CORRECTION: The problem is limited to DAQmx 8.6 and a number of modular instrument drivers which depend on DAQmx.  The full list appears in the table here.  Until you upgrade DAQmx to version 8.6.1, you should not distribute any of those products, as they may cause the target system's MAX database to become corrupted.

I apologize for the incompleteness of my previous response.

Mert A.
National Instruments

[Double_D]

The build seems to work now.  When I ran the installer on the target machine, however, I received the error messages shown in the attached screenshot and the installation did not complete.  When I did a dependency check on the build specification, no problems were reported.

[Mert_A.]

Could you post a distBuildDbg.log from a successful build of the distribution, as well as the distribution itself?

Mert A.
National Instruments

[Double_D]

Attached is the log file for the distribution build.  I'm not sure how to send the distribution itself, as the whole thing is > 150 MB in size.  Is there a subset of files that can be posted?

[Mert_A.]

It looks like all these problems are the result of some sort of problem occurring while upgrading the LabVIEW runtime engine from 8.2 to 8.2.1.  I suspect that the 8.2.1 runtime engine is missing from your local product cache (C:\Program Files\National Instruments\Shared\ProductCache\), and so it is not being copied into your distribution.  Because it is not copied into the distribution, some of the intall-time product dependency checks are failing.

From the log, I can see that the LabVIEW 8.2.1 runtime engine should have been copied into cvidistkit.AIMS_PC\Volume\bin\p26. Please check if the directory contains a folder named lv82rte, and if that directory contains any files.  Also, examine C:\Program Files\National Instruments\Shared\ProductCache\ and look for a "NI LabVIEW Rutime Engine [8.2.1]" directory.  If that directory is missing, it confirms my suspicions.  The solution in that case would be to repair the LabVIEW 8.2.1 runtime engine installation.  To do so, go to Add/Remove Programs, find National Instruments Software in the list, and hit the Change/Remove button.  This will bring up a list of all the NI software on your system.  Find NI LabVIEW Run-Time Engine 8.2.1 in the list, and hit the Repair button on the right.

Let me know what you find.

Mert A.
National Instruments