mirco's.net

Latest Updates: operations RSS

• 

  SCOM Agent Trouble

  Mirco 13:16 on Thursday, 28. August 2008 | View Comments Permalink | Reply
  Tags: -2130771964, agent (2), console, error (4), google (4), install, manager (2), msi, operations, restart, scom (4), service (2), solution, system center (2), troubleshooting, uninstall

  Two weeks ago I installed the KB954049 on our Operations Manager servers. This “allows” me to update all of our 1500 agents, that are currently deployed.

  Four days, some Alerts form the IDS and multiple retries later there are still 60 agents left and refusing every attempt to be updated to version 6.0.6278.32. I’m still not sure why a domain administrator gets an “Access Denied” when trying to initiate a remote installation but I will figure this out, eventually.

  Today I noticed something new. Several, already updated Agents are grayed out on the status view. The servers are up an running, according to ping. A short look at the Computer Management shows the Agent is running too, but when I try to restart the service I’m prompted with some error message and the ID: -2130771964.

  Unfortunately Google isn’t a great help finding this error. There are only a handful results that focus on installing agents, but I have trouble restarting the service.

  My next thought was to try the Change/Repair option in “Add/Remove Software”, which stopped with the same Error code as restarting the service. Somebody must have been very creative in defining error codes for these agents.

  OK, if I can’t repair it, maybe I can uninstall it… and it worked, with the slight limitation that the uninstaller was unable to remove the installation folder.

  The next step was redistributing the Agent from the OpsMgr console, which went through with no errors at all.

   

  Reply Click here to cancel reply.

  Name (required)

  Email (required)

  Web Site

   
• 

  Getting the 100 biggest Agent Queues out of your Operations Manager Database

  Mirco 16:00 on Tuesday, 22. July 2008 | View Comments Permalink | Reply
  Tags: 2007 (3), agent (2), center, database, datawarehouse, manager (2), microsoft (10), operations, ops (2), opsmgr (2), query, queue, scom (4), sql (2), system (2), systemcenter, usage

  Getting a decent overview of you Operations Manager Agents sometimes is a bit hard. There’s a nice graph to display the “Send Queue % Usage” but you have to click through every agent status to find the interesting ones. Most likely the ones with a high percentage status.

  Another way, although with less current data would be to query your Data Warehouse with the following statement

  SELECT     TOP (100) vManagedEntity.Path,
                       vPerformanceRule.CounterName,
                       Perf.vPerfHourly.DateTime,
                       Perf.vPerfHourly.AverageValue AS Avg,
                       Perf.vPerfHourly.MinValue AS Min,
                       Perf.vPerfHourly.MaxValue AS Max
  FROM       Perf.vPerfHourly
  INNER JOIN vManagedEntity ON Perf.vPerfHourly.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId
  INNER JOIN vPerformanceRuleInstance ON Perf.vPerfHourly.PerformanceRuleInstanceRowId = vPerformanceRuleInstance.PerformanceRuleInstanceRowId
  INNER JOIN vPerformanceRule ON vPerformanceRuleInstance.RuleRowId = vPerformanceRule.RuleRowId
  WHERE      (vPerformanceRule.CounterName LIKE N'%send queue % used')
  ORDER BY   Perf.vPerfHourly.DateTime DESC,
             Avg DESC

  This query returns the 100 Queue with the highest fill rate. Note, that data in the Data Warehouse DB can be several hours behind the Operations Database.