Severity propagation service is failing to start when starting from the service window or from the command prompt. We can see the following error messages on the EM console log:
CA-Unicenter NSM Severity Propagation_5_E: Cannot connect to the CAMDB. The Severity Propagation Engine cannot initialize. Terminating...
CA-Unicenter NSM Severity Propagation_110_I: Severity Propagation Engine terminatation initiated (pid:2992)
Severity Propagation creates a user account named SeverityPropagation during installation which it uses to obtain the COM interface, this user account requires local admin privilege with "Log on as Batch job" user right, if this user account is missing from the local admin group then severity propagation service will fail to start with the above error.