URGENT - Updater service cannot be started anymore - Advanced Installer Community
Zsolt Kollarits
Posts: 409
Joined: Fri May 29, 2015 10:36 am

URGENT - Updater service cannot be started anymore

Dear Advanced Installer,

We´ve just noticed that in our latest release out Updater service cannot be started anymore due to an error. I will attach an image about the error.

In our previous releases we had no problem with the service, never. In the problematic release we use AI version 23.3, but I will attach our .aip file too.

Also we analyzed the issue with Process Monitor, I will send it over to you via WeTransfer.

Could you please take a look and tell us what the problem could be.

Best regards,
Zsolt
Attachments
error_service.png
error_service.png (5.89 KiB) Viewed 14267 times
Catalin
Posts: 7847
Joined: Wed Jun 13, 2018 7:49 am

Re: URGENT - Updater service cannot be started anymore

Hello Zsolt,

I have had a look over the AIP file you provided, but I could not see anything suspicious in there.

It looks properly configured.

Do you recall if this started happening after a specific change you've done to your project?

This support is entirely done via Windows Installer. The service is created, started, stopped, etc. via standard actions proprietary to Windows Installer.

Please provide me with a download link, via email, for your setup so I can further test and investigate this on my end.

Additionally, please also provide the log file, as the one you provided is not correct (cannot be read). It looks something as it follows:
Screenshot_182.png
Screenshot_182.png (7.87 KiB) Viewed 13286 times

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Zsolt Kollarits
Posts: 409
Joined: Fri May 29, 2015 10:36 am

Re: URGENT - Updater service cannot be started anymore

Dear Catalin,

Maybe an extra information for you.

In our previous release we used AI version 19.7, and experienced no problem with your Updater service. It can be started anytime, under the same conditions (e.g. same machines, same installation way).

In recent releases we use AI version 23.3, and the already release U0 has this bug, which is a big problem for us, as our users won't be able to upgrade from U0 to U1, because in U0 the service is not running and cannot be started.
Now we are about to release U1 this week, it would be extremely important to fix this problem in U1.

Please try to open the logfile with Process Monitor. You can download it from many places, and you can import the logfile with File menu -> Open.

Best regards,
Zsolt
Catalin
Posts: 7847
Joined: Wed Jun 13, 2018 7:49 am

Re: URGENT - Updater service cannot be started anymore

Hello Zsolt,

First of all, I am really sorry you're encountering such a breaking issue right when you're about to prepare for the release.

I have investigated the procmon log and I'm afraid I don't see much in there.

The Procmon trace shows the following for the executable: it starts, loads all its dependencies fine, reads its own INI, then goes looking for its Advanced Updater settings under Software\Caphyon\Advanced Updater\{5801DF19-493C-44A6-A21F-E7388A297204}\Settings (both the HKU\.DEFAULT and HKLM\...\WOW6432Node locations).

This is quite a strange issue, I admit, considering we haven't changed much regarding the updater between versions (the tool has pretty much stayed the same).

On top of that, the entirety of that support is via standard actions, which suggests no changes there either.

I have also tested this with version 23.3 and the updater service is created and started just fine.

Since now is outside the working hours and the weekend is around the corner, I will have to wait until Monday to check this with our dev team.

0xE0000020 is the return code we see in the first screenshot you provided.

Although I can not see this in the Updater Return Codes article, this specific error code seems to be in the range.

I will have to check with the dev to see exactly what that code means and go from there.

In the meantime, please provide a download link for the setup so I can run some tests on my end and see if I can reproduce this also.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Zsolt Kollarits
Posts: 409
Joined: Fri May 29, 2015 10:36 am

Re: URGENT - Updater service cannot be started anymore

Hi Catalin,

Thank you very much. In the meantime we figured out that we cannot start the Updater service, not even in our older releases, so it seems it was always like this.

Is this behavior normal? Now we started to be thinking about, whether it is your designed behavior?

Best regards,
Zsolt
Catalin
Posts: 7847
Joined: Wed Jun 13, 2018 7:49 am

Re: URGENT - Updater service cannot be started anymore

Hello Zsolt,

Thank you for your followup on this.

I just realized something here, as I was investigating this issue of yours.

Are you trying to manually start the updater service? Like from the Service Manager?

If so, please note that the updater service is not meant to work like that.

The service should start automatically when the Updater is launched on the target machine.

This is done to avoid the UAC request in case the user does not have admin rights - this would be the purpose of this.

This would be the intended flow is: user (or a scheduled task/logon trigger) launches the Updater executable --> the Updater triggers its companion service (registered with the same name as the Updater, started via /runservice) --> the service does the actual privileged work (e.g. running the MSI update silently with /qn) so a restricted/non-admin user isn't blocked by UAC.

That being said, could you please go to your installation folder, launch the Updater from there and let me know if the service starts then?

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

Return to “Common Problems”