LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Labwindows - the system cannot find the specified file

Trying to rebuild a project that has not been changed for a couple years, last built with older verision of labwindows.  The build completes fine with version 20.0.0 labwindows.  But when I try to run the installer I get "the system cannot find the specified file"

 

It does not show what the missing file is.

 

I can install older builds with no issue, so I do not think it is the computer or antivirus...

0 Kudos
Message 1 of 5
(1,030 Views)

Have you rebuilt the installer in cvi 2020 as well?



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 2 of 5
(998 Views)

Yes, rebuilt installer.

 

So this will only not install on a specific windows 10 computer. Other windows 10 computers the installer works.

 

I have attached a log file from the install, but I can't determine what the issue is, may be you can see it.

0 Kudos
Message 3 of 5
(988 Views)

As far as I can understand, the error is listed towards the end of the log file:

Error: Failed to access database: D:\Labwindows\O2ALERT\Rev 2.04\cvidistkit.o2alert\Volume\bin\dp\O2ALERT.msi

Looking at distribution kits I create for our products, it seems the installer cannot find the basic .msi file for your product: check the distribution folder and see if the file is present.

Are you trying to install from a local isk, a remote unit or a removable unit?



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 4 of 5
(982 Views)

Yes, file was there.  Not sure why it cant find it.  Even tried running setup as admin... no difference.

 

So, I copied the Volume folder (that has the entire install)  to my desktop.  then ran the setup file from the desktop and it worked.   Not sure why it worked,  I assume something in the directory structure.    Other computers on my network access the build folder as is, and it works fine?  At least it worked now!

 

Thanks!  

0 Kudos
Message 5 of 5
(975 Views)