Part 2 : SCOM 2012 R2 HealthService Event Reference / HealthServiceExecutive


HealthServiceExecutive

EventID=101
Severity=Error Message=The Health Service encountered a fatal error from ESE indicating that the database was corrupt The error code was %1 The database will be deleted and re-created EventID=102 Severity=Error Message=Removing corrupt state directory “%1” failed with error code %2 The service will try to continue to run

EventID=103
Severity=Warning Message=A task to reset the health service store has been submitted The service store will be deleted and re-created

EventID=104
Severity=Error Message=The Health Service only supports running as the local system user account The service was configured to run under a different user account so it cannot start Please reset the service configuration back to the default setting

EventID=4500
Severity=Error Message=A module of type “%5” reported an unknown error which was running as part of rule “%2” running for instance “%3″ with id:”%4” in management group “%1” EventID=4501 Severity=Error Message=A module of type “%5” reported an error %6 which was running as part of rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4502
Severity=Error Message=A module of type “%5” reported an exception %6 which was running as part of rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4503
Severity=Error Message=A module reported an error %5 from a callback which was running as part of rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4504
Severity=Error Message=Sending data cross-process failed with error “%6” (%5) in rule “%2” running for instance “%3″ with id:”%4” in management group “%1″%n%n The rule will be unloaded

EventID=4505
Severity=Error Message=Sending data to module failed with error %5 in rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4506
Severity=Error Message=Data was dropped due to too much outstanding data in rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4507
Severity=Error Message=Creation of module with CLSID “%5” failed with error “%6” in rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4508
Severity=Error Message=Loading managed module type in assembly “%5” with type name “%6” failed with error “%7” %n %nThis may be because the type or assembly could not be found or the type does not have the MonitoringModuleAttribute %n %nWorkflow: %2 %nInstance: %3 %nInstance ID: %4 %nManagement Group: %1 %nFull Exception Text: %n

EventID=4509
Severity=Error Message=The constructor for the managed module type “%5” threw an exception This module was running in rule “%2” running for instance “%3″ with id:”%4” in management group “%1″%n %n The exception text is:%n

EventID=4510
Severity=Error Message=The Health Service encountered an error %5 causing the rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4511
Severity=Error Message=Initialization of a module of type “%5” (CLSID “%6”) failed with error code %7 causing the rule “%2” running for instance “%3″ with id:”%4” in management group “%1”

EventID=4512
Severity=Error Message=Converting data batch to XML failed with error “%6” (%5) in rule “%2” running for instance “%3″ with id:”%4” in management group “%1″%n %n The rule will be unloaded

EventID=4513
Severity=Error Message=The callback method %5 failed with exception “%6” in the module %7 %n %nWorkflow: %2 %nInstance: %3 %nInstance ID: %4 %nManagement Group: %1 %nFull Exception Text:%n

Source : Part 2 : SCOM 2012 R2 HealthService Event Reference / HealthServiceExecutive

Cengiz KUSKAYA

Comments (0)

Skip to main content