SCMU Fails to start when one or more instances have a corrupt configuration file.

[ramonsmits]

Symptoms

SCMU fails to start when one of the instances has a corrupt configuration file with the following details:

SCMU should not fail to start because of this. It should show an error at the instance with the corrupt configuration file.

Who's affected

All supported users of Service Control Management Utility.

Root cause

Corrupted XML files not gracefully handled.

Confirmed workarounds

SCMU will not work until the XML file is manually fixed.

Original bug report

SCMU fails to start when one of the instances has a corrupt configuration file with the following details:

SCMU should not fail to start because of this. It should show an error at the instance with the corrupt configuration file.

Workaround

• Revert to a backup config file that works or fix existing config file.
• If an instance other than the misconfigured one needs to be managed, the powershell module can be used.