We did a mass deployment of an upgrade. Roughly 5% of our sites downloaded the upgrade file, but did not run it. At the sample sites I inspected the logs contained the following.
Product: NabHospMon -- Error 1719. The Windows Installer Service could not be accessed.
The error was coming up within seconds of the installer starting. The upgrades in question installed were supposed to install .net 6.0 as a prerequisite as part of the process, but never got that far. At each site the upgrade could later be run successfully, indicating the problem wasn't a corrupt installer service or the like.
The updater logs would look like the following:
<< Advanced Installer (x86) Log >>
OS Version: 10.0.14393 SP0 (workstation) [x64]
CPU: Intel(R) Pentium(R) Gold G5400 CPU @ 3.70GHz
# 2022-06-09 12-41-37 [PID=7460|Thread=7036] | Running updater. Mode: 2
# 2022-06-09 12-41-38 [PID=7460|Thread=7036] | OpenUrl() returned:3758096403
# 2022-06-09 12-41-38 [PID=7460|Thread=7036] | Connect() failed
# 2022-06-09 12-41-38 [PID=7460|Thread=7036] | Running temp updater from path: C:\Users\POSTGR~1\AppData\Local\Temp\754457c9e14eca9cbc1325d2eb965a24\NabHospMonUpdater.exe
<< Advanced Installer (x86) Log >>
OS Version: 10.0.14393 SP0 (workstation) [x64]
CPU: Intel(R) Pentium(R) Gold G5400 CPU @ 3.70GHz
# 2022-06-09 12-41-38 [PID=4652|Thread=9920] | Running updater. Mode: 8
# 2022-06-09 12-41-40 [PID=4652|Thread=9920] | VerifySignatureTrust returnned: 0
# 2022-06-09 12-41-40 [PID=7460|Thread=7036] | Updater finished. Mode: 2. Return code: 0
# 2022-06-09 12-41-43 [PID=4652|Thread=9920] | Update "NabHospMon 2022.2.531.51" installer runned. Exit code: 1603. Return code: 0
# 2022-06-09 12-41-43 [PID=4652|Thread=9920] | Updater finished. Mode: 8. Return code: -536870900
# 2022-06-09 12-41-43 [PID=4652|Thread=9920] | Update installation failed LastError: 0xE000000C
Doing a reboot either in the middle of the process or at the end won't help as it's running into the issue immediately. My assumption is that nothing we do within the upgrade program can help, and that this must be handled by the updater program. How can we address this issue? Is there a setting on the updater we can adjust?
FOLLOW US
Get the latest news in Application Packaging