Event IDs
Useful event IDs - not just SCOM stuff.
ID | Log | Source | Level | Description | Explanation |
26 | System | Application Popup | Information | Application popup: MOMCertImport.exe - Application Error : The application was unable to start correctly (0xc000007b). Click OK to close the application. | If you run MOMCertImport on a gateway install but haven't installed the gateway component yet, you'll get this error. |
1201 | Operations Manager | HealthService | Information | Example: New Management Pack with id:"Microsoft.Intune.ConfigurationManager.Monitoring", version:"2024.3.19.0" received. | When the agent has successfully downloaded a management pack. |
1217 | Operations Manager | HealthService | Information | The Microsoft Monitoring Agent running on computer name is suspended for the following reason: "ConfigMgr 5.00.9088.1025 - SMS_MaintenanceTaskRequests - GUID" | When a ConfigMgr task sequence suspends monitoring. |
4221 | Operations Manager | SQL Server Discovery MP Windows | Error | Unable to execute query 'SELECT ServiceName, PropertyName, PropertyNumValue, PropertyStrValue FROM SqlServiceAdvancedProperty WHERE (PropertyName = 'ISWOW64' OR PropertyName = 'LANGUAGE' OR PropertyName = 'INSTANCEID' OR PropertyName = 'SPLEVEL' OR PropertyName = 'INSTALLPATH' OR PropertyName = 'ERRORREPORTING') AND SqlServiceType = 1' for the path '\\COMPUTER\root\Microsoft\SqlServer\ComputerManagement13'. 32 bit: False. Error code: -2147217392. Error message: Invalid class Source: Microsoft.SQLServer.Module4.Helper | Still investigating but it breaks SQL discovery. Check this article. |
7000 | System | Service Control Manager | Error | Example:
|
When services have a problem starting. |
7002 | Operations Manager | HealthService | Error | The Health Service could not log on the RunAs account name for management group name because it has not been granted the Allow log on locally right. | If SCOM service accounts don't have this right, you'll see this event. |
7005 | Operations Manager | HealthService | Error | The Health Service cannot verify the future validity of the RunAs account name for management group name. The error is Logon failure: the user has not been granted the requested logon type at this computer.(1385L). | |
7017 | Operations Manager | HealthService | Error | The health service blocked access to the windows credential NT AUTHORITY\SYSTEM because it is not authorized on management group name. You can run the HSLockdown tool to change which credentials are authorized. | This is logged on domain controllers only. You need to run hslockdown.exe tool to allow NT AUTHORITY\SYSTEM access to the HealthService. |
7022 | Operations Manager | HealthService | Error | The Health Service has downloaded secure configuration for management group name, and processing the configuration failed with error code Keyset does not exist(0x80090016). | The HealthService has a problem, see this article. |
20053 | Operations Manager | OpsMgr Connector | Information | The OpsMgr Connector has loaded the specified authentication certificate successfully. | The HealthService has loaded the certificate successfully. |
21006 | Operations Manager | OpsMgr Connector | Error | The OpsMgr Connector could not connect to name:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination. | This is a fairly common error when agents can't connect to a gateway or management server. I'm adding it here because of this weird issue. |
21019 | Operations Manager | OpsMgr Connector | Information | OpsMgr has returned to communicating with its primary host name. | When an agent successfully connects to a MS/GW. |
Comments
Post a Comment