Health service should not generate data about this managed object ( Microsoft.JEE.ApplicationServer.Instance ) [aka SCOM Discovery of JEE Application Server (Tomcat/JBoss/WebLogic/WebSphere) fails]
A new feature of SCOM 2012 is the support for discovery and monitoring of JEE Application Servers (Tomcat/JBoss/WebLogic/WebSphere). For the discovery process to work properly, the Agent Proxy must be enabled for each Agent computer.
Failure to do will result critical alerts within the SCOM Console Agent proxy not enabled. The alert description will be similar to:
The agent was not able to submit data on behalf of another computer because agent proxy is not enabled. Details:Health service (scxomd-2k3-01.contoso.com ) should not generate data about this managed object ( Microsoft.JEE.ApplicationServer.Instance ).
Also, in the event log of the management server there will be a warning followed by an error. The warning description will be similar to:
Data Access Layer rejected retry on SqlError:
Request: p_ManagedEntityInsert -- (BaseManagedEntityId=3f5f7310-9367-c21f-df91-2427a0084a28), (TypedManagedEntityId=3f5f7310-9367-c21f-df91-2427a0084a28), (ManagedTypeId=4638fb4f-1601-575d-b44f-2d633aae44b9), (FullName=Microsoft.JEE.ApplicationServer.Instance:AppSrv01-scxom-2k3-01Node01Cell-scxom-2k3-01Node01.scxom-2k3-01.contoso.com), (Path=), (Name=AppSrv01-scxom-2k3-01Node01Cell-scxom-2k3-01Node01.scxom-2k3-01.contoso.com), (TopLevelHostEntityId=3f5f7310-9367-c21f-df91-2427a0084a28), (DiscoverySourceId=663d6ca0-feae-b4c0-e838-6bb2a74bf4fe), (HealthServiceEntityId=e18a4bef-6258-57f9-48d7-654e7d3ae27b), (PerformHealthServiceCheck=True), (TimeGenerated=10/5/2011 1:08:28 AM), (IsOptimistic=False), (LifetimeRelationshipId=), (LastModified=1/1/1753 12:00:00 AM), (TypedInstanceInserted=False), (ChangeId=), (RETURN_VALUE=1)
Class: 16
Number: 777980008
Message: Health service ( scxom-2k3-01.contoso.com ) should not generate data about this managed object ( Microsoft.JEE.ApplicationServer.Instance ).
To resolve this issue, the Agent Proxy should be enabled. For the agent machine in question, perform the following steps.
- Go to the Administration space in the Operations Manager Console
- Find the agent in the Agent Managed view
- Open Properties for that agent
- In the Security tab, check the Allow this agent to act as a proxy option
- Click OK
Note: the solution steps can also be found in the Alert Details pane in the SCOM Console.
Comments
- Anonymous
January 01, 2003
I know this is an old post, but I thought I'd mention that Kevin Green has a great one-liner PowerShell command to do it in one swipe:
Get-SCOMAgent | where {$_.ProxyingEnabled.Value -eq $False} | Enable-SCOMAgentProxy
http://kevingreeneitblog.blogspot.com/2012/01/scom-enable-agent-proxy-setting-for-all.html