Part 9 : SCOM 2012 R2 HealthService Event Reference / DiscoveryManager


DiscoveryManager

EventID=10000
Severity=Warning Message=A scheduled discovery task was not started because the previous task for that discovery was still executing %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group name: %1

EventID=10001
Severity=Warning Message=An error occurred starting a discovery task %nError Code: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group name: %2 EventID=10002 Severity=Warning Message=Unable to write discovery data for discovery The discovery task will be run again at its next scheduled time %nError Code: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group name: %2

EventID=10003
Severity=Warning Message=Non-empty incremental data submitted and will be dropped %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group name: %1

EventID=10004
Severity=Warning Message=Discovery manager has detected an unsupported topology On demand discovery is being disabled and the health service will be restarted in legacy mode

EventID=10005
Severity=Warning Message=An unexpected error has occurred in a discovery task %nError: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group name: %2

EventID=10006
Severity=Warning Message=Discovery task has timed out %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group name: %1

EventID=10007
Severity=Warning Message=Discovery task has been canceled unexpectedly %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group name: %1

EventID=10008
Severity=Warning Message=Discovery task has been suspended unexpectedly %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group name: %1

EventID=11350
Severity=Error Message=Discovery failed to initialize due to invalid schedule configuration %n%nInvalid Configuration: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group: %2

EventID=11351
Severity=Error Message=Discovery failed to initialize due to invalid schedule configuration %n%nRejected Item: %1 %n%nRejected Value: %2 %n%nDiscovery name: %4 %nInstance name: %5 %nManagement group: %3

EventID=11352
Severity=Error Message=Discovery failed to initialize because the recurring interval can not be greater than the full re-sync interval for the schedule %n%nRecurring Interval Length (seconds): %1 %n%nFull Re-Sync Interval Length (seconds): %2 %n%nDiscovery name: %4 %nInstance name: %5 %nManagement group: %3

EventID=11353
Severity=Error Message=Discovery failed to initialize because the maximum number of schedule windows has been reached %n%nNumber of windows: %1 %n%nMaximum number of windows allowed: %2 %n%nDiscovery name: %4 %nInstance name: %5 %nManagement group: %3

EventID=11354
Severity=Error Message=Discovery failed to initialize because there is no schedule window specified %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11355
Severity=Error Message=Discovery failed to initialize because some schedule window has a negative start %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11356
Severity=Error Message=Discovery failed to initialize because some schedule window has a non-positive length of time %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11357
Severity=Error Message=Discovery failed to initialize because some schedule windows overlap with each other %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11358
Severity=Error Message=Discovery failed to initialize because the last and first schedule windows overlap %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11359
Severity=Error Message=Discovery failed to initialize because the first schedule window is after the full interval %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11360
Severity=Error Message=Discovery failed to initialize because the number of excluded dates in the schedule is greater than the maximum allowed %n%nNumber of excluded dates: %1 %n%nMaximum number allowed: %2 %n%nDiscovery name: %4 %nInstance name: %5 %nManagement group: %3

EventID=11361
Severity=Error Message=Discovery failed to initialize because the exclude date interval in the schedule failed to parse using the MM/dd format %n%nDay of the year in error: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group: %2

EventID=11362
Severity=Error Message=Discovery failed to initialize because the specified schedule is not recognized as a weekly or simple recurring one %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11363
Severity=Error Message=Discovery failed to initialize because the specified schedule interval number is out of range %n%nInterval: %1 %n%nMinimum Unit Number: %2 %n%nMaximum Unit Number: %3 %n%nDiscovery name: %5 %nInstance name: %6 %nManagement group: %4

EventID=11364
everity=Error Message=Discovery failed to initialize because the specified schedule interval is greater than the maximum allowed %n%nInterval (seconds): %1 %n%nMaximum (seconds): %2 %n%nDiscovery name: %4 %nInstance name: %5 %nManagement group: %3

EventID=11365
Severity=Error Message=Discovery failed to initialize because the specified schedule contains an invalid multiple days interval The start and end mask validation failed Make sure to choose only one day of the week for each, and that they differ from each other %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11366
Severity=Error Message=Discovery failed to initialize because some schedule window has no day of the week set %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11367
Severity=Error Message=Discovery failed to initialize because some “hour in the day” in the schedule could not be parsed on the HH:mm format %n%nHour in the day: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group: %2

EventID=11368
Severity=Error Message=Discovery failed to initialize because in a single day window, the start hour is greater than the end hour %n%nDiscovery name: %2 %nInstance name: %3 %nManagement group: %1

EventID=11369
Severity=Error Message=Discovery failed to initialize because some value in its schedule configuration is too long %n%nValue: %1 %n%nDiscovery name: %3 %nInstance name: %4 %nManagement group: %2

EventID=11370
Severity=Error Message=Discovery failed to initialize because the specified schedule spread initialization interval number is out of range %n%nInterval: %1 %n%nMinimum Unit Number: %2 %n%nMaximum Unit Number: %3 %n%nDiscovery name: %5 %nInstance name: %6 %nManagement group: %4

EventID=11371
Severity=Error Message=Discovery failed to initialize because the specified schedule spread initialization interval is greater than the maximum allowed %n%nInterval (seconds): %1 %n%nMaximum (seconds): %2 %n%nDiscovery name: %4 %nInstance name: %5 %nManagement group: %3

Source : Part 9 : SCOM 2012 R2 HealthService Event Reference / DiscoveryManager

Cengiz KUSKAYA

Comments (0)

Skip to main content