We are using Advanced Installer 20.4 to package and distribute a service. Our installation and update process uses the Advanced Installer Update service to update silently across approximately 600 remote servers belonging to our customers (servers we don't manage).
The service is written in .Net Framework 4.8 (not sure if that's relevant) and during our testing, it updates successfully.
However, in the field we are receiving reports of issues that either stop the update from applying to about 10% of our customer's servers, or in rare cases (1% or so) even uninstall the previous version of the service including the update server. As you can imagine, this is proving both confusing and frustrating. Its made more complicated by the fact that its often difficult to reproduce these errors in our test environments.
What we're attempting to do is the following:
- If an existing installation of our service is present, stop the service (so that there are no open file handles, thus forcing a reboot)
- Copy the new files for our service (exe and dll files)
- Install or Update our service in the Windows Service Manager to reference the new exe
- Start our service
So our questions are:
- Is this the most appropriate way to do a service install and update?
- If it is, is there a way to ensure an update occurs without a server reboot?
- If the update fails, are we doing the right things in the aip to ensure a successful rollback?
FOLLOW US
Get the latest news in Application Packaging