Conditioned Service Operation - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

tolo1984
Posts: 34
Joined: Tue Jul 26, 2011 9:47 am

Conditioned Service Operation

Hi,

We have an issue with an upgrading of a previous version not installed with Windows Installer techonologies.

So our new Advanced Installer based wizard, detects if that previous version was installed and makes some special actions.

The only problem is with a service we DON'T want to run install and run in that special case.

We are a bit annoyed because that services is attached to a component NOT installed if we are upgrading that old version.
But the service is launched anyway by the installer, failing, of course.


Maybe we are doing something wrong... i can't understand that a service operation attached to a NOT installed component, is run anyway.
Any suggestion to solve this?

Other workaround that we thought is to somehow set the "Install" state property to false, if this is possible.
But we would need to perform the copy of the files o one of the component...


thank you for your help.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Conditioned Service Operation

Hello,

Usually a control operation is placed in the service.EXE component. Indeed if the component is not installed, the service it refers to shouldn't attempt to start it either.
I am not sure why this is happening. Can you please send us the .AIP ( project file ) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”