CVI Build Problems

[Double_D]

This one looks different than the last one.

[Mert_A.]

There's nothing suspicious in the area of code your exception is coming from, but I'd like to try to further narrow it down (hopefully) to an exact line. Also, if you could give some more details about the way you set up your new drive, it might help.  Specifically, was there any imaging/ghosting involved, or did you just reinstall all software on to a clean OS?  Can you tell me what NI software (CVI, Driver CD, etc) you installed, and in what order? I know you mentioned that you had version 8.1 and then upgraded to 8.5.  A screenshot of the NI software in the Windows Add/Remove Programs list may help, as it will give all names and versions.  Could you also export the following branch of your registry to a .reg file and post it as well?

HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer

Can you think of anything else peculiar or unique about the system, compared to other machines you have on which the distribution build works?

Attached is iteration 4 of the DLL.

Mert A.
National Instruments


Message Edited by Mert A. on 12-10-2007 06:44 PM

[Double_D]

Test.

[Double_D]

Attached is the latest debug log file, along with the exported registry branch for the NI Installer and a list of installed NI programs.  The new hard drive was imaged, using a standard image used on most of the systems in our facility.  I reinstalled CVI 8.1.1, Measurement Studio 8.1.1, and the device drivers from the August 2007 release.  LabVIEW 8.5 was installed sometime after the initial CVI installation.  I installed CVI 8.5 most recently.  I don't believe I installed device drivers then, as they were probably updated when LabVIEW was installed, but I'm not sure about that.

I don't have another system with a recent version of CVI installed, but I do have a laptop I can install it to for testing.

P.S. Adding more than one attachment to a post doesn't seem to work.  I tried to submit this post 5 or 6 times, with only the blank message above showing up.

[Mert_A.]

I believe I've found the problem, but I'm not sure what's causing it at this point, so I don't yet have a solution.  Using the attached DLL, please make me one more log file to confirm my expectations. You may not get an error popup this time, or you may get an entirely different kind of problem; that's because I've removed changed the code in a way that prevents the immediate cause of your problem.  Do not assume anything is actually fixed.  Just follow the usual steps, and if you get to the Edit Installer dialog, just cancel it and close the Manage Distributions dialog.

I suspect there may be a problem with one or more of the xml manifest files used to identify deployable components on your system.  It is also possible that the files are correct, but are not properly being loaded.  If you could also include a copy of your entire Program Files\National Instruments\Shared\MDF\Manifests directory in your zip file, I can hopefully determine if a specific file is to blame.

Also, if you can get to the Edit Installer dialog without an error, it's possible to enable a second kind of debug log file which may have some useful information.  Once the Edit Installer dialog is up, put the focus on one of the tab labels, then hit ctrl+shift+L; that will enable the logging.  Then close the dialog and, once again, repeat the process of creating a new distribution.  This log file will end up in your temp directory -- probably C:\Documents and Settings\<username>\Local Settings\Temp\distBuildDbg.log.

Thanks again with all your patience and your help in debugging this issue.

Mert A.
National Instruments


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

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

[Double_D]

The attached zip file has both debug logs and all of the files in the Manifests directory.  This was actually the first time I was able to get to the Edit Installer dialog.

[Mert_A.]

I believe I have a solution for you.  You should now restore your original cvi.dll if you haven't already done so.  Go to your Program Files\National Instruments\Shared\MDF\Manifests directory and delete (renaming is not sufficient) the file

NI LabVIEW Run-Time Engine 8.2 {45FA54F6-8574-49D2-9E2D-0BDDE6237822}.xml

It seems that the LabVIEW 8.2.1 upgrade to version 8.2 did not remove this manifest file, though it should have. The result was both an 8.2 and an 8.2.1 manifest with the same (not-so) unique identifier.

I will attach a copy of the file to this post, just in case you have some future need to restore it, for whatever reason.  If this doesn't completely solve your issue, or you have further troubles, let me know.

Mert A.
National Instruments

[Double_D]

OK, the error message is now gone.  When I do a build, I am prompted for the NI Device Drivers - November 2007 disk.  I have these disks; however, I just received notice from NI this week that these disks should be discarded because of a software problem (Document 4G4H4LQA).   According to that document, I should use the August 2007 release disks. 

 I have now edited the installer to use the August 2007 disks to load the NI-488 software.  The build now fails with the build log showing the following:
"Preparing to build deployment
Copying products from distributions
 
Error: Internal error. (Error code -40)
End Error Report"

[Mert_A.]

Yes, you are correct about the Driver CD issue.  Please use the second debug log method I described to generate a distBuildDbg.log for your new build error.  I can't say for sure whether this is leftover from the earlier issue, or something different, but the debug log should help clarify.

Mert A.
National Instruments