mpande
Posts: 64
Joined: Tue Sep 28, 2021 1:52 pm

Error 1719. The Windows Installer Service could not be accessed.

Thu Apr 07, 2022 3:40 pm

We've been doing an automated deployment of upgrades, and have run into several instances of "Error 1719. The Windows Installer Service could not be accessed." appearing in the logs.

An example in the logs looks like this:
MSI (c) (AC:44) [05:09:30:008]: PROPERTY CHANGE: Adding EXE_CMD_LINE property. Its value is '/exenoupdates /forcecleanup /wintime 1649093056 /qn '.
MSI (c) (AC:44) [05:09:30:008]: PROPERTY CHANGE: Adding AI_IE_Ver property. Its value is '11'.
MSI (c) (AC:44) [05:09:30:008]: PROPERTY CHANGE: Adding AIEXTERNALUI property. Its value is '2'.
MSI (c) (AC:44) [05:09:30:008]: Doing action: AI_DpiContentScale
Action start 5:09:30: AI_DpiContentScale.
MSI (c) (AC:10) [05:09:30:008]: Invoking remote custom action. DLL: C:\Users\POSTGR~1\AppData\Local\Temp\MSI1B08.tmp, Entrypoint: DpiContentScale
MSI (c) (AC:D8) [05:09:30:008]: Cloaking enabled.
MSI (c) (AC:D8) [05:09:30:008]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (AC:D8) [05:09:30:008]: Connected to service for CA interface.
MSI (c) (AC:10) [05:09:30:180]: Could not set proxy blanket on CA proxy interface. Error: 0x80070534
CustomAction AI_DpiContentScale returned actual error code 1601 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (AC:44) [05:09:30:180]: Note: 1: 1719
MSI (c) (AC:44) [05:09:30:180]: Product: NOP -- Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.


The sites in question are not in safe mode. Rerunning the upgrader has always resolved the issue, but this requires manual intervention. Are there any common causes of this issue, or any suggestions you can offer?

Liviu
Posts: 1026
Joined: Tue Jul 13, 2021 11:29 am
Contact:  Website

Re: Error 1719. The Windows Installer Service could not be accessed.

Fri Apr 08, 2022 3:22 pm

Hello Max,

Can you please tell me if you are able to reproduce this on multiple clean machines, or is it specific to one machine only?

To be honest, we have not encountered this problem recently. I am afraid that is not an Advanced Installer issue, more likely a Windows Installer problem on that machine.

As per Microsoft documentation, this error could occur if the Windows Installer Service is disabled or if the Windows Installer Service is not registered properly (the registry are corrupted).

In order to solve the issue, you can try the solutions from the below MSFT article before re-installing:

Windows Installer Service error 1719


It looks like you can solve this if you re-register the Windows Installer Service or if you manually start the Windows Installer service (if is stopped).

Hope that helps!

Best regards,
Liviu
________________________________________
Liviu Sandu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

mpande
Posts: 64
Joined: Tue Sep 28, 2021 1:52 pm

Re: Error 1719. The Windows Installer Service could not be accessed.

Tue Apr 12, 2022 4:13 pm

We have not been able to reproduce this locally, or with our customer machines. The issue is occurring randomly on customer machines. On those customer machines rerunning the same upgrade works, which makes me think there is no issue with registry corruption or a disabled service.

Does advanced installer have a mechanism to reboot system before applying an upgrade?

Liviu
Posts: 1026
Joined: Tue Jul 13, 2021 11:29 am
Contact:  Website

Re: Error 1719. The Windows Installer Service could not be accessed.

Wed Apr 13, 2022 9:47 am

Hello Max,

Unfortunately we don't have predefined support for this yet.

However, that capability to "Uninstall Old Version - Reboot - Resume installation with the New Package" was already implemented by our development team and will be included in our next major release that should be out by the end of this month.

We will notify you when this will be available. Thank you for your patience. 

Until then, as a workaround, in the latest version of your project you can add manually in the “Table Editor” page in the “InstallExecuteSequence” table a new row: ForceReboot.
The ForceReboot action must come between InstallInitialize and InstallFinalize in the action sequence of the InstallExecuteSequence table.

For the ForceReboot action you can have something like that:

Action field: ForceReboot
Condition field: ( NOT Installed AND OLDPRODUCTS ) AND ( NOT AFTERREBOOT = "1")
Sequence field: 1502
force reboot.png
force reboot.png (86.64KiB)Viewed 5906 times
If that sequence is already present in your project, you can increase the number, for example to 1503.

Please note that the “Table editor” feature is available only in an “Enterprise” or higher project type.

Hope that helps!

Best regards,
Liviu
________________________________________
Liviu Sandu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

wholt@nabancard.com
Posts: 9
Joined: Mon Feb 01, 2021 11:15 pm

Re: Error 1719. The Windows Installer Service could not be accessed.

Thu Apr 14, 2022 4:23 pm

AI:
out of <100 upgrades this error is representing a 5% rate of failure. Just last night, in upgrading only 27 installs, 1 out of 27 failed due to the 1719 error. Given that our software is business critical for our customers, such a failure rate cannot be tolerated and will be unmanageable if our install base gets into thousands. Given that all we do is rerun the installer again, and everything is normal, either we need the updater to be more fault tolerant, we have to figure out how to avoid, or I have to look for other products to meet our needs. I just renewed our annual maintenance, so I would hate to have that be in vain. Do we need to involve Microsoft support?

Liviu
Posts: 1026
Joined: Tue Jul 13, 2021 11:29 am
Contact:  Website

Re: Error 1719. The Windows Installer Service could not be accessed.

Fri Apr 15, 2022 11:15 am

Hello,

I'm sorry for the trouble you faced.

An installation can fail with this error for several reasons. The ones that could apply in this case:
  • Antivirus or Defender program might block.
  • The Windows Installer Service is not running.
We can not control this and that it all depends on the OS where the setup is running. It's outside the MSI what's happening.

As it looks like, the Windows Installer service does not start in time to handle the installation when the MSI is launched for the first time. By default the Windows Installer is not running, it is started when needed. Most likely, it fails to start in time to handle the first installation, so when running the MSI for the second time, it is running and can handle the installation properly.

If you start the Windows Installer from the command line, you can see that it says "START_PENDING":
msiserver.png
msiserver.png (12.5KiB)Viewed 5885 times

You can also have a look on the following article where is debated the same issue faced on another product:
Windows Installer Service could not be accessed

Regarding the MP extension, you have 30 days to get your money back. Send us the Order Reference number that you've received when you extended the MP and we will give you a refund, no worry about that.

As a side note, any tool you would be using to create the installer will face the same behavior. It cannot be controlled by the installer. Just on a quick Google search and you will find dozens of users that faced this error when installing various apps, even well know apps such as Microsoft Office. It does not depend on the tool used to create the setup.

I'm afraid that the tool used to create the installer cannot do anything to fix this specific error. Since this is a Windows related problem, you should contact Microsoft support and have their feedback.

Best regards,
Liviu
________________________________________
Liviu Sandu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Catalin
Posts: 6509
Joined: Wed Jun 13, 2018 7:49 am

Re: Error 1719. The Windows Installer Service could not be accessed.

Thu Apr 28, 2022 4:26 pm

Hello,
Does advanced installer have a mechanism to reboot system before applying an upgrade?
This improvement has been added in version 19.4 of Advanced Installer, released on April 26th, 2022.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

mpande
Posts: 64
Joined: Tue Sep 28, 2021 1:52 pm

Re: Error 1719. The Windows Installer Service could not be accessed.

Tue May 17, 2022 4:49 pm

Thanks! Just to verify is this the radio box Product Information / Upgrades / Order / "Uninstall old version first, reboot and then install new version" ?

Catalin
Posts: 6509
Joined: Wed Jun 13, 2018 7:49 am

Re: Error 1719. The Windows Installer Service could not be accessed.

Wed May 18, 2022 9:01 am

Hello Max,

You are always welcome!

Yes, that is the option.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”