This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Service control - option to ignore on failure?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 06, 2010
11:39 AM
Service control - option to ignore on failure?
Greetings!
I'm installing a set of services, some of which MAY require additional configuration within our installed application before they will start properly.
I have ServiceControl entries set for all of my services, but when it goes to start one of the ones requiring this post-install configuration, the installation halts with a 1920 error, indicating that the service failed to start, presenting only a Retry or Cancel option.
Assuming there is no way to add an "Ignore" button to this popup, can anyone think of alternatives to acheiving the desired behavior? I was thinking some sort of component Condition, but couldn't come up with a catch all (e.g. I was thinking !FeatureRequiringService=3 , but I'm thinking that could get the installation into a bad state where it would fail repeatedly on a Repair or Modify if the configuration work hadn't yet been completed.
Any info appreciated! Thanks much,
--jdavidi
I'm installing a set of services, some of which MAY require additional configuration within our installed application before they will start properly.
I have ServiceControl entries set for all of my services, but when it goes to start one of the ones requiring this post-install configuration, the installation halts with a 1920 error, indicating that the service failed to start, presenting only a Retry or Cancel option.
Assuming there is no way to add an "Ignore" button to this popup, can anyone think of alternatives to acheiving the desired behavior? I was thinking some sort of component Condition, but couldn't come up with a catch all (e.g. I was thinking !FeatureRequiringService=3 , but I'm thinking that could get the installation into a bad state where it would fail repeatedly on a Repair or Modify if the configuration work hadn't yet been completed.
Any info appreciated! Thanks much,
--jdavidi
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 06, 2010
01:32 PM
It's a kludge, but I could remove the control event for the one service and put an executable CA after StartServices that calls net start and ignores the exit code -- but I'm certainly open to cleaner options 🙂
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)