LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unhandled MSI error at install

Thanks for teh reply. I gave that a try but it has made no difference on my machine. I've continued searching for more info on MSDN but still haven't run across a listof MSI error numbers that includes this particular one.
 
I may have to break down and call my local NI rep for assistance.
 
 
0 Kudos
Message 11 of 15
(1,931 Views)
update...
 
A gent at Microsoft pointed me toward some information on Windows Installer which lead me to this page with Microsoft System Error Codes...http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes__0-49...
 
Error 267 says the directory name is invalid. From the text of the error my uneducated guess is that something is not allowing the LV setup app to create a directory. MSI reporta problem back to Kernell32.dll which reports this error 267?  Possibly this is the "NIDIR" noted in the first line of the error?
 
I'm not sure where to go from here.
0 Kudos
Message 12 of 15
(1,989 Views)
update...
 
A gent at Microsoft pointed me toward some information on Windows Installer which lead me to this page with Microsoft System Error Codes...http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes__0-49...
 
Error 267 says the directory name is invalid. From the text of the error my uneducated guess is that something is not allowing the LV setup app to create a directory. MSI reporta problem back to Kernell32.dll which reports this error 267?  Possibly this is the "NIDIR" noted in the first line of the error?
 
I'm not sure where to go from here.
0 Kudos
Message 13 of 15
(1,922 Views)
Another update (notes for future use)
 
I spoke with an NI rep and he pointed me toward another thread where a similar error occurred when installing LabVIEW FPGA. They were able to resolve the error by using the Microsoft Windows Installer Cleanup Utility http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 I downloaded the utility and learned that it cleans up corrupted Windows Installer settings caused by registry errors, failed/aborted installation attempts that leave partial registry settings or partial windows installer data.
 
I have also run through some of the methods for resolving Windows Installer errors listed on this page as well http://support.microsoft.com/default.aspx?scid=kb;en-us;555175 .
 
Another page titled : "Windows Installer fails silently after you upgrade to Windows Installer 3.1"  http://support.microsoft.com/default.aspx?scid=kb;en-us;898628 detailes a method for determining the version of Windows Installer 3.1 that is installed on your computer. I have the latest version installed.
 
So far I have still not resolved the problem. I will post updates as I find more information.
Message 14 of 15
(1,912 Views)

The problem is solved on my machine.

To make a long story short, something in my software/OS configuration is insisting that a drive "F:" be present. I installed a 1GB USB drive and re-designated it drive F: and proceeded to install LabVIEW 7.1

 

This solved the problem and I was able to install LabVIEW 7.1 PDS..

 

I checked the space available on the USB drive before and after the installation. There was no change and at no time did the activity light on the USB drive give any indication the drive was being accessed.

 

I did a cursory check of the registry (I'm no expert on that however) and didn't find anything. Any theory on what's going on here?

 

.

Message Edited by Skoorb on 12-10-2005 02:06 PM

Message 15 of 15
(1,874 Views)