I'm experiencing a couple of issues with my Advanced Installer projects regarding service management during upgrades. Here are the details:
Unexpected Execution of DeleteServices:
Although I've removed the DeleteServices action from the table editor section under InstallExecuteSequence in my Advanced Installer project, it continues to execute during the installation process. Below is a snippet from the log indicating its execution:
Code: Select all
SI (s) (6C:98) [11:09:09:770]: Doing action: StopServices
Action start 11:09:09: StopServices.
Action ended 11:09:09: StopServices. Return value 1.
MSI (s) (6C:98) [11:09:09:786]: Doing action: DeleteServices
Action start 11:09:09: DeleteServices.
Action ended 11:09:09: DeleteServices. Return value 1.I have added the condition "(VersionNT) AND (NOT Installed)" to the InstallServices action in the InstallExecuteSequence table. The purpose of this condition is to ensure that services are installed only during new installations and bypassed during upgrades.
Reason for Setup:
I am aiming to preserve existing service configurations, especially the "Log On As" settings, during upgrades to avoid altering configurations unnecessarily.
Additionally, I'm facing a similar challenge in another installer project related to IIS configurations. During upgrades, I want to maintain the existing IIS settings and avoid resetting them to default values.
Steps Taken:
- Removed DeleteServices.
- Set conditions for InstallServices for new installations only.
- Ensured builders are updated with the latest changes.
- Verified custom actions that might overlap.
Despite these steps, I'm encountering unexpected behaviors and seek guidance on how to resolve these issues effectively.
Any insights or suggestions on resolving these two challenges would be greatly appreciated.
I'm using Advanced Installer 19.3
FOLLOW US
Get the latest news in Application Packaging