Hello, my company's application uses the Advanced Installer updater.
We are running into an issue where the updater scheduled task tries to run the service for a quiet non-elevated update, but we receive the following in the updater log:
```
<< Advanced Installer (x86) Log >>
OS Version: 10.0.17134 SP0 (workstation) [x64]
# 2019-01-29 13-58-27 [PID=14392|Thread=15112] | Service running from path: "C:\Program Files (x86)\<MANAFACTURER_NAME>\<APPDIR>\<UPDATER_FILE_NAME>.exe" /runservice /set loglevel "Error|Debug"
# 2019-01-29 13-58-27 [PID=14392|Thread=15112] | LegacyIpcObjectBaseName:
# 2019-01-29 13-58-27 [PID=14392|Thread=15112] | Unable to start service: <SERVICE NAME> LastError: 1053
```
This results in the updates downloading but not being installed.
Here are some screenshots of the pertinent settings for the service:
Updater
Updater Service
Updater Control
I've been investigating this for a bit, but all the info I can find on the 1053 error is related to other applications and the suggested fix I keep finding is to increase the timeout registry entry. That does not seem like a viable distributable solution.
Is it possible the service is timing out during the download of our update(s)? The updates average around ~250mb each so they can take awhile to download over slower connections.
I'm also curious what the message `LegacyIpcObjectBaseName` is about.
My current leads as of making this post are the !note on this page: https://www.advancedinstaller.com/user- ... dates.html
In particular does the requirement "The service name must match the name of the Updater file." require matching whitespace or lack there of in the service and updater file names?
The elevated updates page also seems to conflict with the `/runservice` entry on this page: https://www.advancedinstaller.com/user- ... dater.html.
```
Enables the Updater to run as a service. It can only be used if you want to manually install the service required by our Install updates without elevation support. The Updater service should be configured to start using the /runservice command line argument.
```
Or does "manually install the service" refer to checking the "Install support service" option for the updater?
Also as an aside what is the expected behavior if the update has "Use check frequency" set to true with the scheduled task set up? and are the service and scheduled task intended to be used together?
FOLLOW US
Get the latest news in Application Packaging