12-12-2015 10:04 PM
It might be a good time to exploit the advantages of building an installer to make sure it is always installed the same way and with the same options...
12-13-2015 01:01 PM
12-13-2015 01:32 PM
If it doesn't look for it again, does that file exist on the other computers that aren't asking for it?
12-14-2015 11:45 PM
Yes,,, over and over agian... this is driving me crazy. The machine was a brand new computer, freshly installed!!
12-14-2015 11:46 PM
12-15-2015 12:02 AM
Additional detail...
The attached screenshot shows that in the task bar the before-mentioned malignous windows appear with the same program name as the main program (AFICS)
---
Fabio
12-15-2015 01:46 AM - edited 12-15-2015 01:56 AM
@FSFirenze wrote:
Additional detail...
The attached screenshot shows that in the task bar the before-mentioned malignous windows appear with the same program name as the main program (AFICS)
---
Fabio
Calling it malignous is definitely overreacting, sorry! I have something similar on one of my machines. Every time I startup any 32 Bit NI application I get a dialog that the Runtime Engine for LabVIEW 8 needs to be installed. I can cancel that and everything continues as normal or I can wait until I get a final dialog that the computer needs to be restarted. If I chose yes the computer restarts and does the same next time again. If I chose no, I can continue to work with the program.
Annoying? yes you bet! Malignous? definitely not!
This whole mess started after I had decided to install some LabVIEW toolkit for an earlier version of LabVIEW than the latest that was also installed on that computer. And that installation somehow got hosed. It has to be mentioned that there are just about every LabVIEW version installed on that computer since 7.1 and many toolkits, CVI versions, and what else. So it is actually amazing thata all those software versions still can coexist together and this problem while annoying is defintely caused by a combination of installations that NI doesn't and couldn't even test.
Now your problem is obviously not exactly the same, but the symptoms are similar enough. Something in the Windows registry got hosed during install of your application or something that gets installed together with it. What it could be I unfortunately can't tell you. I did some registry hunting but Windows Installer technology is a 10 headed monster with 11 tails and 12 claws. I doubt there is anyone on this planet who still fully understands all the relationships, conditions and trapfalls that are present in it.
My recommendation for you, your health and the feelings of the people around you: Wipe that harddisk and do a reinstall! It's radical and takes a bit of time but it will save you from ulcers and other nastyness.
07-03-2020 12:24 PM
Update ... 5 years later and several developments into the software, I have installed it on a few more machines with no issues till .... today the issue repeats exactly as described above on a fresh computer just purchased.
The installation has used the same runtime engine, drivers, support files that I've always used, but on this specific machine it shows the message. not to mention that the exact same software on another machine doesn't show the message ....
I hope some expert has 10 minutes to relook at this thread and provide recommendations!
Thansk
09-29-2020 09:38 PM
I want to cry ... I just found the solution .... 5-6 yrs later ...
I just needed to install Acrobat Reader ...
Not sure about the connection here, but once installed the message disappeared.
09-30-2020 03:55 AM
It could be a toolkit you use in your executable, that comes with its help documentation provided in PDF form. VIs can contain links to them and while this information is usually scraped from the VI code when building an executable, that is not true for VIs that are set to maintain their front panel (because they are meant to display they front panel at some point). Or something in your buid installer that tries to open a PDF file.