System Center Guide and Tutorial: showing

Tuesday, 12 April 2016

SCOM Management Server showing warning with "Event ID 1825 - A security package specific error occurred"

Today when i checked the SCOM management Server it was in Warning state.
When i open the health explorer i could see only "Failed to access event log" is selected and its in warning state with error in details "A security package specific error occurred".
When i tried to access the event log from the SCOM management server it failed with the same error.
so i decided to do a nslookup of the server and found that the reverse lookup is pointing to the alias of the server rather then the actual server name.
Once it was resolved things got health again.
So when you have this issue, its usually issue with the DNS entries which needs to be fixed

Tuesday, 20 January 2015

We recently had a issue where there is no SCOM agent on the server.But When we try to Install SCOM agent from Console its says there is already agent pending to be managed and doesn't allow to install.
Then when we check the pending agent state it shows up there ,but if i go and check the server there is no SCOM agent.
So we where puzzled how its coming in pending management. Then we reject in pending management it goes from there.But if i try to install agent again it comes in pending management.
So its stuck in pending management,So this time i rejected it and its gone from there.
Then i Ran the Command shell command

GET-SCOMPendingManagement | where {$_.AgentName -eq "FQDNServername"

And the server was showing pending in command shell but not in console.
To fix it you need to login to Operations Manager database server and run the below store procedue on query window on the operations manager database

p_AgentPendingActionDeletebyAgentName 'FQDNServername'