Several times per day, Windows Installer keeps popping up. Message indicate that feature is on a network resource and source is local temp folder, it is not on the network at all. If I open temp, this folder is not in the temp. This problem has been seen on several workstation, some users have IBM Notes 9 and other have IBM Lotus Notes 8.5.3. They are both on lates FP and IF.
Temp folder is temp and why Installer is trying to get anything from it? Please assist how to resolve this issue and why this is happening?
Subject: Same problem - multiple machines
We are having the same problem on several of our machines. Upon machine startup, the Windows Installer pops up and says:
“The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package “IBM Notes 9.0.1 Social Edition.msi” in the box below.”
And, like the user above is experiencing, the default source points to c:\users\username\appdata\local\temp\etc. All users are on the latest Windows 10 and IBM Notes 9.0.1 FP6 and above.
Just started yesterday morning, July 9, 2018. Any help is greatly appreciated.
Subject: see previous response, it seems Google misfired…
Easy fix.
After that, complain to Google so they fix Chrome.
Subject: Solution is in editing Chrome 67 file
Chrome 67 made a boo boo, see: https://translate.google.com/translate?hl=nl&sl=auto&tl=en&u=https%3A%2F%2Fblog.digiway.it%2Fdwblog.nsf%2Fdx%2Fgoogle-chrome-v67-ibm-notes-problema-lancio-inatteso-dellinstaller.htm https://translate.google.com/translate?hl=nl&sl=auto&tl=en&u=https%3A%2F%2Fblog.digiway.it%2Fdwblog.nsf%2Fdx%2Fgoogle-chrome-v67-ibm-notes-problema-lancio-inatteso-dellinstaller.htm
It accesses the installer Key assigned to IBM Notes. So it’s Google’s fault, not IBM.
Thanks to Vittorio Orefice for publishing an easy fix:
Solution one (very simple)
In relation to the problem reported with Chrome that performs the opening of an installer that requires the executible.msi of the client notes, we propose the following solution:
- Close Chrome;
- Open the path C: \ Users \ \ AppData \ Local \ Google \ Chrome \ User Data ;
- Rename the “Local State” file (it has no extension, it is a text file).
At the next launch of Chrome the “Local State” file is created and the anomaly does not occur further.