commands when updater is a service

[codemonk3y]

I have installed the updater as a service, but now none of the commands seem to work.

I was using updater.exe /checknow -nofreqcheck -justdownload . Now that it's a service I changed it to /silent -nofreqcheck -justdownload , but it does not seem to do anything. Running /justcheck returns 0, so I does see the updates, but I can't get any other commands to work. I tried running the commands in a command prompt, but nothing works. How do I send calls to the updater now that it's a service?

I do have the updater setup to execute manually.

Also, from a command prompt if I run /checknow I get the error Access is denied

Thanks,
Scott

[codemonk3y]

It's failing b/c it's on a win7 machine and for some reason the access is denied for the updated to copy the files to my application directory.

What do I need to do so the service has permission to download to my application folder? I have the download folder set to app folder \ updates, so it fails to create the updates folder.

[codemonk3y]

When my update runs it reinstalls the updater as a server and gives me a prompt the service needing to be closed. I have the install set to Limit to basic user interface. Is there a way to suppress this message and just close the service so it can continue with the install?

Thanks,
Scott

[Daniel]

Hello Scott,

What do I need to do so the service has permission to download to my application folder? I have the download folder set to app folder \ updates, so it fails to create the updates folder.

In order to achieve what you want you can proceed as is explained in our "Call Updater in non-admin user" thread. Let us know if this helps, otherwise please give us more details about your scenario.

When my update runs it reinstalls the updater as a server and gives me a prompt the service needing to be closed. I have the install set to Limit to basic user interface. Is there a way to suppress this message and just close the service so it can continue with the install?

I'm afraid this happens due to a Windows Installer limitation. However, we already have added an improvement for this issue in our next version (10.1) of Advanced Installer which is in testing phase and should be released until the end of this week. So, starting with next version of AI this issue should not appear for installation package built using AI 10.1. If you need a sooner fix for this please send us an e-mail to support at advancedinstaller dot com.

All the best,
Daniel