Share via

Agent Pending Actions can get out of synch between the Console, and the database

  • Article

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    January 29, 2009
    Thanks.  This helped me out.  I had to resort to the SQL Query.

  • Anonymous
    May 19, 2009
    I couldn't get the query to run (SQL 2008), but I was able to edit the top 200 rows and manually delete the entry. Great Post.

  • Anonymous
    May 20, 2009
    SQL Query worked for me. Thanks. Took me 2 days to find this!!

  • Anonymous
    June 11, 2009
    EXCELLENT POST! It solved my problem i have had for a while now. Thanks alot for a great blog.

  • Anonymous
    March 09, 2011
    Great post this. I resolved the issue with the SQL query.

  • Anonymous
    October 04, 2011
    we had this problem after a failed push and then a manuall installation of the agent. we managed to approve it by changing the 'reject' command to approve-agentPendingAction as: get-agentPendingAction | where {$_.AgentName -eq "servername.domain.com"} | approve-agentPendingAction now it shows upp and is healty with the managed agents. Cheers!

  • Anonymous
    December 17, 2013
    it's the fix i needed. Tried cache clearing on the console, multiple paths to agent re install but only this database entry delete using the stored procedure fixed it.Many thanks

  • Anonymous
    May 12, 2014
    Kevin: On SCOM 2012 SP1 and Forward powershell command update.PS C:|> Get-SCOMPendingManagement | Where-Object {$_.AgentName -eq "Hostname,com"} | Deny-SCOMPendingmanagement.

  • Anonymous
    September 15, 2014
    Thanks Kevin
    Am looking into a solution for last 1 month, Your SQL query save me.

  • Anonymous
    October 31, 2014
    Here are some more links from my private collections. This links are very usefull to administrate, configure

  • Anonymous
    December 17, 2014
    The comment has been removed

  • Anonymous
    June 05, 2015
    This blog helped me out today. Thanks for sharing :)

  • Anonymous
    November 23, 2015
    i have received alerts for some linux server agents that heartbeat failed in scom 2012 R2.So how to verify what happened to those agents?what might have happened?what would be the resolution . These agents are successfully installed few months back . The failing messages of these agents is like "The System is not responding to heartbeats."Could you please help me out here.

  • Anonymous
    January 27, 2016
    Thanks for sharing the good info, the below command helped me to approve the agent from pending management
    (get-agentPendingAction | where {$_.AgentName -eq "CAKITAPGPC1.corp.riotinto.org"}|Approve-AgentPendingAction)

  • Anonymous
    February 18, 2016
    Yes, try to delete the pending action on Db tabel "agentpendingaction". It's work. Thks for sharing

  • Anonymous
    June 13, 2018
    If you have a LOT of Agent Pending Actions, and you just want to clear them all:DECLARE @AgentName nvarchar(MAX)WHILE EXISTS(SELECT TOP(1) AgentName FROM AgentPendingAction)BEGIN SET @AgentName = (SELECT TOP(1) AgentName FROM AgentPendingAction) SELECT @AgentName EXEC p_AgentPendingActionDeleteByAgentName @AgentNameEND