These Events are common when troubleshooting problems related to Health Service certificates i System Center Operations Manager 2007:
21021 – Could not load Certificate
Check if certificate exists and the Health Service has permissions to read it.
20052 – Certificate not loaded (name does not match)
Make sure Issued To match the actual computername.
20053 – Certificate loaded
The certificate is loaded – and everything should be working.
Creating an EventLog entry using PowerShell is shown below:
Write-EventLog -LogName 'Application' -Source 'MyEventSource' -EventID 1000 -EntryType Warning -Message "This is a test of writing to the Event Log using PowerShell."
Note: The Event Source needs to be created before writing entries to the Event Log. (See this post for further info: Create Event Source with PowerShell)
To create a Event Source in PowerShell use this:
$Source = "MyEventSource"
if ([System.Diagnostics.EventLog]::SourceExists($Source) -eq $false {
[System.Diagnostics.EventLog]::CreateEventSource($Source, "Application")
}
Get more info on CreateEventSource method here : http://msdn.microsoft.com/en-us/library/2awhba7a.aspx
In PowerShell 2.0 this is even simpler:
$Source = "MyEventSource"
New-EventLog -LogName Application -Source $Source
To determine when Windows was started search for Event ID 6005 in the System Event Log. The entry should look like this:
Log Name: System Source: EventLog Event ID: 6005 User: N/A Computer: computername Description: The Event log service was started.
After installing agent event 21006 is shown in EventLog:
Log Name: Operations Manager
Source: OpsMgr Connector
Date: 16-12-2010 14:13:56
Event ID: 21006
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SCOM.domain.local
Description: The OpsMgr Connector could not connect to SCOM.domain.local :5723.
The error code is 11004L(The requested name is valid, but no data
of the requested type was found.). 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 because the agent is unable to connect to Management Server. When connection fails no data will be sent to the Management Server, and typically no errors indicating connection failed will show up at the Management Server event log.
Verify agent can resolve Management Server adress and no extra characters(space) are present in the name specified during Agent installation.
In the picture above the agent is trying to connect to a Management Server which has a space before and after the FQDN. The extra spaces are easily overlooked in Event Properties.