Labview installation failure

[vldmrrr]

I copied labview installation drive to my computer to install it later by mounting the installer as mapped network in XP virtual machine I plan to use for development.

The installation proceeds through accepting licenses and starts LV installer at which point it fails with the following error dialog:

---------------------------------------------------------------------------------------

Developer Error. The following errors were found in your ini file:

1. Specified file not found: [MsiEngine] WinNT PATH=

bin\WindowsInstaller-KB893803-v2-x86.exe

Correct the iini file and try again.

.\ConfigInfo.cpp(3171): InstallerError 11006

Developer Error. The following errors were found in your ini file:

1. Specified file not found: [MsiEngine] WinNTPath = bin\WindowsInstaller-KB893803-v2-x86.exe

Correct the ini file and try again.

<No Debug Message>

--------------------------------------------------------------------------------------

I verified that WindowsInstaller-KB893803-v2-x86.exe does indeed exist in Z:\Resources\Bin. Whats wrong?

[vldmrrr]

OK, resolved. As the error message states, the file is missing in 'bin\', while all NI product installer directories have 'Bin'. After renaming 'Bin' to 'bin' in LV installer, the error message changed to some other file, that was now missing in 'Bin'.

Solution, of cause, was to make copy 'Bin' folder named 'bin' in every product install directory.

Conclusions regarding QC etc are left to readers

[DAQjr]

That sounds peculiar... what filesystem are you using on Windows that is case sensitive?

I agree that the case should match, but noone else has run into this issue.

[vldmrrr]

The installer files were copied on host of VMware player (linux, ext3). The Xp guest running inside player access host files through shared folders mechanism of VMWare (samba?) and shows 'HGFS' for file system - never before heard of such. I presumed NTFS is case preserving, but you're right, I tried to create two folders with name only different in case on NTFS volume, and windows would not allow me do that.

[MartyMcDAX]

Thank you for bringing this issue to our attention.  There is a case mismatch in the installer, which is rarely seen due to the uncommon situation of installing software on a Windows machine from a Linux server.  This issue will be fixed in FRC 2013 software.

For anyone who runs into this issue for FRC 2012, you can work around the problem by copying the entire installer to the Windows machine and running it from there.

[donia]

Hi, I have this issue as well. However, when I try to change the name of Bin, the option is greyed out.

[MartyMcDAX]

Hi donia,

I'm not exactly sure which option you are referring to as being greyed out, but you can try changing the name to something else, like "test", then changing it back to "bin".  Or, you can copy the entire installer to your Windows machine and run it from there.