Conditional Service File - WixUtil ServiceConfig primary key violation

[mballou-bt]

I have a project that installs a different service EXE based on a condition for the same service name. The install originally used MsiServiceConfigFailureActions. I tried updating it to use WixUtil:ServiceConfig, however that tries to use the "Name" instead of the "Id", as the primary key which conflicts. I need the service name to be the same, since users may script starting/stopping the service which uses that name.

Is this a limitation, or is there a better way to setup the conditional service?

Example:

<Component Condition="ENABLEX=1">
	<File Id="ServiceX.exe" Source="ServiceX.exe"></File>
	<ServiceInstall Id="ServiceX" Name="myservice" DisplayName="My Service" Type="ownProcess" Start="auto" ErrorControl="normal">
		<util:ServiceConfig FirstFailureActionType="restart" SecondFailureActionType="none" ThirdFailureActionType="none" RestartServiceDelayInSeconds="60" />
	</ServiceInstall>
</Component>

<Component Condition="ENABLEX&lt;&gt;1">
	<File Id="ServiceY.exe" Source="ServiceY.exe"></File>
	<ServiceInstall Id="ServiceY" Name="myservice" DisplayName="My Service" Type="ownProcess" Start="auto" ErrorControl="normal">
		<util:ServiceConfig FirstFailureActionType="restart" SecondFailureActionType="none" ThirdFailureActionType="none" RestartServiceDelayInSeconds="60" />
	</ServiceInstall>
</Component>

[bevanweiss]

You could have a third component which is installed in either condition, with it's own Registry keypath, and have it just do the util:ServiceConfig, such that there's only a single instance of it.

You tried using the ServiceConfigFailuresActions element right?
https://docs.firegiant.com/wix/schema/wxs/serviceconfigfailureactions/

[mballou-bt]

Thank you. The 3rd component method worked. I didnt realize I could nest the util:ServiceConfig directly under the Component.

The schema does have this note about doing that though:
"Nesting a ServiceConfig element under a component element will result in an already installed service to be configured. If the service does not exist prior to the install of the MSI package, the install will fail."

The install did work and configured the Failure Actions correctly despite the schema message.

I was using the ServiceConfigFailureActions, but since the Wix document said it doesn't always work, I was just switching to ServiceConfig.

[bevanweiss]

That warning might just be non-ideal wording. In the context of a CustomAction, it's more likely to mean "If the service does not exist prior to the custom action execution, the install will fail".
The ServiceConfig is normally scheduled after ServiceInstall, so things should 'just work'.. although given they're separate Components, you'd want to have a little caution around the Component Lifecycle.. and when it's going to be modified, since it might not match with the associated Service File.