Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 10830 Source: Health Service Modules
|Source: Health Service Modules|
An alert couldn't be inserted to the database. This could have happened because of one of the following reasons:
- Alert is stale. The alert is generated by an MP recently deleted.
- Database connectivity problems or database running out of space.
- Alert received is not valid.
The following details should help to further diagnose:
Details: RuleId:b0219962-69d5-fccb-f863-c6ae03379355. HealthServiceId:176d6b53-5dba-40a4-d22a-09b069d1ba24. Health service ( 176D6B53-5DBA-40A4-D22A-09B069D1BA24 ) should not generate data about this managed type ( 0BCA7808-7999-6426-1C70-537193522A50 ) object Id ( (null) )..
|English: Request a translation of the event description in plain English.|
You need to enable proxy for the agent mentioned in the alert. See:
EV100281 (OpsMgr 2007: DataAccessLayer Event ID 33333) and EV100282 (Agent Proxy alerts - finding the right machine to enable agent proxy on using a custom report) - e.g. to identify HelthService name from SCOM PowerShell:
Get-MonitoringObject -Id 176D6B53-5DBA-40A4-D22A-09B069D1BA24
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated