SCOM Health Service Watcher / Server Availability...

Good morning all,
I'm reasonably new to SCOM reporting and have only recently started to take a close look at how this could be performing for my company. I understand that SCOM reporting is a vast and complex beast and have also read quite a lot of questions posted in forums
that are not a million miles away from what I'm about to ask (although not quite the same).
I'm looking to produce a report that reports upon the reachability / actual uptime of each monitored server. I've selected my date range and added the health service watcher for each of my servers, indicated what I consider an outage to be (unplanned maintenance
and monitoring unavailable) and produced the report. The result is confusing me. For around 2/3's of our monitored infrastructure I'm viewing what I expected to see... around 99% uptime with the "health Service Heartbeat Failure" and "Computer
Not Reachable" monitors having detected some downtime (power cycles following application of Windows updates). However, around a 1/3 of our infrastructure isn't reporting any downtime what-so-ever, nothing detected by the "health Service Heartbeat
Failure" and "Computer Not Reachable" monitors which is inaccurate as these servers have been power cycled following Windows updates applications.
If anyone could shed any light on what is occurring here it would be greatly appreciated.
Thank you in advance for anyone taking the time to read this post.
Cheers.
M Tipler

Hi,
As far as I know, the heartbeat interval for agents is 60 secs by defalt, and the management server allow 3 times of missed heartbeat. So although some agents have been rebooted due to updates, the management server may not fire heatbeat alert for them.
It is suggested to run SQL query to get all heartbeat failure on all agents:
SELECT
TOP
[AlertName]
,[BaseManagedEntity].DisplayName
FROM [OperationsManager].[dbo].[Alert]
JOIN [OperationsManager].[dbo].[BaseManagedEntity]
ON [ALERT].BaseManagedEntityId=[BaseManagedEntity].BaseManagedEntityId
WHERE [ALERT].AlertName
= 'Microsoft.SystemCenter.HealthService.Heartbeat'
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Similar Messages

Where does the data of health service watcher node gets stored in OperationsManagerDB/DW ?

Hi,
We have integrated SCOM 2007 R2 to some third party tool which takes the data of health service as the component from OperationsManagerDB/DW and shows the availability of each server in graphical format. But we have noticed that due to some issues with health
service, the availability gets affected. Hence, we have thought to add the data of health service watcher node as a component in that tool than
health service only. But we are unable to get the exact location of health service watcher in OperationsManagerDB/DW.
Could anyone please help me with the location of health service watcher node data in
OperationsManagerDB/DW.
What is the table name where the data of health service watcher node gets collected in OperationsManagerDB/DW.
Thanks in anticipation.

Hi,
A watcher node is an agent that runs monitors and rules that test an application or feature on another computer.
A watcher node can either be the agent with the application or feature installed, or it can be a separate agent. If the watcher node is a separate computer, in addition to ensuring that the application or feature is healthy, the watcher node can validate
that clients can connect to it and test such additional features as security, network availability, and firewalls.
I think according to applications monitored, watcher node is configured differentlly, the below article is talking about lync watcher node, you may want to check it:
http://technet.microsoft.com/en-us/library/jj204943.aspx
Regards,
Yan Li
Regards, Yan Li

Health Service in which the location monitoring object is contained is not available

Hello,
When i am trying to discover new machines I am getting this error:
Health Service 'OPMGRRMS1.xxx.xxx.xxx.xxx' in which the location monitoring object is contained is not available
All services have been restarted successfully without error... on the RMS Server.
- System Center Data Access
- System Center Management
- System Center Management Configuration
- System Event Notification Service
but still having the error...
Date: 10/27/2009 10:14:00 AM
Application: System Center Operations Manager 2007 R2
Application Version: 6.1.7221.0
Severity: Error
Message:
Microsoft.EnterpriseManagement.Common.LocationMonitoringObjectNotAvailableException: Health Service 'OPMGRRMS1.ad.medctr.ucla.edu' in which the location monitoring object is contained is not available. Make sure that the computer hosting the Health Service is available and verify that the Health Service is running.
at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleSubmitTaskIndigoExceptions(Exception ex)
at Microsoft.EnterpriseManagement.DataAbstractionLayer.AdministrationOperations.LaunchDiscovery(Guid batchId, List`1 jobDefinitions)
at Microsoft.EnterpriseManagement.Administration.ManagementServer.BeginExecuteWindowsDiscovery(IList`1 discoveryConfigurations, AsyncCallback callback, Object state)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Administration.DiscoveryProgress.<>c__DisplayClass7.<SubmitTask>b__3(Object , ConsoleJobEventArgs )
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
DW works (Datawarehouse) I restarted the System Center Management successfully
MS works (2nd Management Server) I restarted the System Center Management successfully
ACS works (Audit Control Server) cannot access the reporting server but I restarted the System Center Management successfully
RMS DB 48 % Free
DW DB 18% Free
ACS DB 13% Free
I can ping the RMS Server what other test could I do?
I removed the new items:
Delete the six modules of Windows Failover Clustering Management Pack (SCOM Console > Administration > Management Packs > Right Click delete on it)
Uninstall System Center Operations Manager 2007 R2 Authoring Resource Kit (Add/Remove Programs)
Uninstall System Center Operations Manager 2007 R2 Authoring Console (Add/Remove Programs)
Reboot the RMS Server
SAME ERROR!!!
Any idea
Thanks,
Dom
Altiris Support / System Center Configuration Manager Support

Hi Marius,
In the Operations Manager Log I have some errors:
Log Name: Operations Manager
Source: HealthService
Date: 10/28/2009 10:15:06 PM
Event ID: 4506
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad.medctr.ucla.edu
Description:
Data was dropped due to too much outstanding data in rule "Microsoft.SQLServer.2008.LoginsPerSecCollection" running for instance "MSSQLSERVER" with id:"{24345584-0FD5-0FAB-2293-D4C82BEDB086}" in management group "SCOM-MED".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="HealthService" />
<EventID Qualifiers="49152">4506</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-29T05:15:06.000Z" />
<EventRecordID>4126486</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>OPMGRRMS1.ad.medctr.ucla.edu</Computer>
<Security />
</System>
<EventData>
<Data>SCOM-MED</Data>
<Data>Microsoft.SQLServer.2008.LoginsPerSecCollection</Data>
<Data>MSSQLSERVER</Data>
<Data>{24345584-0FD5-0FAB-2293-D4C82BEDB086}</Data>
</EventData>
</Event>
Log Name: Operations Manager
Source: HealthService
Date: 10/28/2009 10:15:50 PM
Event ID: 1107
Task Category: Health Service
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad.medctr.ucla.edu
Description:
Account for RunAs profile in workflow "Microsoft.SystemCenter.DataWarehouse.CollectEntityHealthStateChange", running for instance "OPMGRRMS1.ad.medctr.ucla.edu" with id:"{DF927679-EAC0-B8EC-F8CC-F0031A36AD4F}" is not defined. Workflow will not be loaded. Please associate an account with the profile. Management group "SCOM-MED"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="HealthService" />
<EventID Qualifiers="49152">1107</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-29T05:15:50.000Z" />
<EventRecordID>4126487</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>OPMGRRMS1.ad.medctr.ucla.edu</Computer>
<Security />
</System>
<EventData>
<Data>SCOM-MED</Data>
<Data>{DF927679-EAC0-B8EC-F8CC-F0031A36AD4F}</Data>
<Data>OPMGRRMS1.ad.medctr.ucla.edu</Data>
<Data>Microsoft.SystemCenter.DataWarehouse.CollectEntityHealthStateChange</Data>
</EventData>
</Event>
Log Name: Operations Manager
Source: HealthService
Date: 10/28/2009 10:15:50 PM
Event ID: 1107
Task Category: Health Service
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad.medctr.ucla.edu
Description:
Account for RunAs profile in workflow "Microsoft.SystemCenter.DataWarehouse.CollectEventData", running for instance "OPMGRRMS1.ad.medctr.ucla.edu" with id:"{DF927679-EAC0-B8EC-F8CC-F0031A36AD4F}" is not defined. Workflow will not be loaded. Please associate an account with the profile. Management group "SCOM-MED"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="HealthService" />
<EventID Qualifiers="49152">1107</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-29T05:15:50.000Z" />
<EventRecordID>4126488</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>OPMGRRMS1.ad.medctr.ucla.edu</Computer>
<Security />
</System>
<EventData>
<Data>SCOM-MED</Data>
<Data>{DF927679-EAC0-B8EC-F8CC-F0031A36AD4F}</Data>
<Data>OPMGRRMS1.ad.medctr.ucla.edu</Data>
<Data>Microsoft.SystemCenter.DataWarehouse.CollectEventData</Data>
</EventData>
</Event>
Log Name: Operations Manager
Source: HealthService
Date: 10/28/2009 10:15:50 PM
Event ID: 1107
Task Category: Health Service
Level: Error
Keywords: Classic
User: N/A
Computer: OPMGRRMS1.ad.medctr.ucla.edu
Description:
Account for RunAs profile in workflow "Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData", running for instance "OPMGRRMS1.ad.medctr.ucla.edu" with id:"{DF927679-EAC0-B8EC-F8CC-F0031A36AD4F}" is not defined. Workflow will not be loaded. Please associate an account with the profile. Management group "SCOM-MED"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="HealthService" />
<EventID Qualifiers="49152">1107</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-29T05:15:50.000Z" />
<EventRecordID>4126489</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>OPMGRRMS1.ad.medctr.ucla.edu</Computer>
<Security />
</System>
<EventData>
<Data>SCOM-MED</Data>
<Data>{DF927679-EAC0-B8EC-F8CC-F0031A36AD4F}</Data>
<Data>OPMGRRMS1.ad.medctr.ucla.edu</Data>
<Data>Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData</Data>
</EventData>
</Event>
these errors are recurrent...
the RMS is doing yoyo between Green as healthy and grayed out under Monitoring > Windows Computers or Administration > Device Management > Management Servers (2-3 minutes green then grayed out) there is no event in the Windows Event Log as System Center Management service remains running...
This MP for the Data Warehouse Internal Library has been removed and restored two weeks agao with Premier Support as the RMS was already fleaky and doing gray-green...
I have tried again but I will need to check again as it seems these errors are pointing to the Data Warehouse Library and not only the Data Warehouse Internal Library Management Pack. The main problem with this is that the Data Warehouse Library is [b]94[/b] Management Packs which depends on this Data Warehouse Library in our environment so if I need to remove this one it is almost a complete reinstallation of 50% of our MPs :(
Heartbeat failures: The Heartbeat State view ( Health Service Watcher (Agent) - All) is giving me 10 Critical and 1 Warning
[b]Any way to delete All MPs and restore them at once?[/b]
I have an issue trying deleting "Notifications Internal Library":
The User does not have sufficient permissions to perform the operation"
I am using my own account which is supposed to have all accesses.
I tried the hotfix 938510 but it does not seem to apply to SCOM R2
Thanks
Dom
Altiris Support / System Center Configuration Manager Support

Health Service's "Availability" task

I have a question about the following thread:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/e05085ea-2e58-4418-8c5f-2a8a89b16b05/rms-components-what-they-do-and-how-they-do-it?forum=operationsmanagerdeployment
What exactly is the Health Service's "Availability" task. What does that mean?
And what does the Health Service on a SCOM 2007 R2 MS (non-RMS) do?
Thanx in advance.
Regards,
Chris

Hi,
Regarding the Health Service, here is a blog to introduce each component and its function. It doesn’t mention availability.
http://blogs.technet.com/b/jonathanalmquist/archive/2010/01/11/health-service-heartbeat-failure-diagnostics-and-recoveries.aspx
The Health Service has the same function on both RMS and MS. RMS is the first management server installed in a management group. In brief, the RMS is the focal point for administering the management group configuration, administering and communicating with
agents, and communicating with the Operations Manager database and other databases in the management group. There is no difference on Health Service.
Niki Han
TechNet Community Support

TF400893: Team Foundation Server services are not available.

Hi Gang
Am getting
TF400893: Team Foundation Server services are not available. This is most likely caused by a network error. Please check your connection and try again.
consistently when trying to access TFS2012 Web Access. I'm on the same domain as the server and able to login however as soon as I try and access a query it asks me to log in again and then presents me with the above message.
Any thoughts am trying to get as many ports open as possible however security's pretty tight here.
Regards

Hi,
Thanks for your feedback!
I recommend you install TFS Power Tools and run a Team Foundation Server Complete Health Check and see if it helps.
TFS 2012 Power Tools download address:http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f
Hope it helps!
Best Regards,
Cathy Kong
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Problem about Calling SQLplus Web Service on Aspen Watch Server

Hi all,
We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
                                                                                Server A / Server B / Error, if applicable
.Net Framework installed on MII server:                                 1.1, 2.0 /      1.1, 2.0
.Net Binding:                                                                          1.1 /               2.0
IIS version on MII server:                                                 6 /                 6
From MII server broser to Server A web service:                 Yes /      Yes
From MII server browser to Server B web service:                 No /     No /      Return on web "The test form is only available for requests from the local machine"
From localhost browser to Server A web service:                 n/a //     Yes
From localhost browser to Server B web service:                 Yes //     n/a
From PC browser to Server B web service:                                No /        Yes /     Return on web "The test form is only available for requests from the local machine"
Credentials required to run web service:                                 No /     Yes /
The following are the SOAP generated:
Server A
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string" />
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpGet">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpGetIn" />
<wsdl:output message="tns:ExecuteSQLHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpPost">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpPostIn" />
<wsdl:output message="tns:ExecuteSQLHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
<http:binding verb="GET" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<http:urlEncoded />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
<http:binding verb="POST" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Server B
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
Best regards,
Lawrence
Edited by: UMeng Lai on Feb 6, 2009 4:07 PM

Hi all,
We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
                                                                                Server A / Server B / Error, if applicable
.Net Framework installed on MII server:                                 1.1, 2.0 /      1.1, 2.0
.Net Binding:                                                                          1.1 /               2.0
IIS version on MII server:                                                 6 /                 6
From MII server broser to Server A web service:                 Yes /      Yes
From MII server browser to Server B web service:                 No /     No /      Return on web "The test form is only available for requests from the local machine"
From localhost browser to Server A web service:                 n/a //     Yes
From localhost browser to Server B web service:                 Yes //     n/a
From PC browser to Server B web service:                                No /        Yes /     Return on web "The test form is only available for requests from the local machine"
Credentials required to run web service:                                 No /     Yes /
The following are the SOAP generated:
Server A
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string" />
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpGetOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostIn">
<wsdl:part name="command" type="s:string" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLHttpPostOut">
<wsdl:part name="Body" element="tns:string" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpGet">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpGetIn" />
<wsdl:output message="tns:ExecuteSQLHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:portType name="SQLplusWebServiceHttpPost">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLHttpPostIn" />
<wsdl:output message="tns:ExecuteSQLHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
<http:binding verb="GET" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<http:urlEncoded />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
<http:binding verb="POST" />
- <wsdl:operation name="ExecuteSQL">
<http:operation location="/ExecuteSQL" />
- <wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
- <wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
<http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Server B
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
- <s:element name="ExecuteSQL">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ExecuteSQLResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
- <wsdl:message name="ExecuteSQLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQL" />
</wsdl:message>
- <wsdl:message name="ExecuteSQLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
</wsdl:message>
- <wsdl:portType name="SQLplusWebServiceSoap">
- <wsdl:operation name="ExecuteSQL">
<wsdl:input message="tns:ExecuteSQLSoapIn" />
<wsdl:output message="tns:ExecuteSQLSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="ExecuteSQL">
<soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
- <wsdl:input>
<soap12:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap12:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="SQLplusWebService">
- <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
<soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
- <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
<soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
Best regards,
Lawrence
Edited by: UMeng Lai on Feb 6, 2009 4:07 PM

The Security Token Service is not available -- SP Server on Windows 7

I just installed SharePoint Server 2010 on a Windows 7 workstation with the aim of setting up a development environment.
Installed all the prerequisites, then SP, everything seemed to go smoothly.
However, the Health Analyzer is warning my that "the Security Token Service is not available". It says that the "Administrator should try to restart the Security Token Service"
I looked under Services for my computer and also looked in IIS, did not see any thing that referenced security tokens. Where would I find the security token service?
Thanks.

No.
In Central Admin>Application Management>Manage Service Applications I see the
Security Token Service Application is running. But the health analyzer is still saying that
The Security Token Service is not available.
Any advice on resolving this would be greatly appreciated.

Health Service Heartbeat Failure Alert for Generated when one Management Server Down,

Hi,
I have Two Management Server, every one manage about 100 server, when one Management Server goes down unexpected, I receive 100 Alert for 100 Server Health Service Heartbeat Failure.
My Question, why when the Management Server down, it send that all Managed agent Health Service Heartbeat Failure?
Is there a way to change this?

SCOM 2012 agent will autofailover when primary server is down. You can check the failover management server by using the following powershell cmdlet:
#Verify Failover for Agents reporting to MS1
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
$Agents | sort | foreach {
Write-Host "";
"Agent :: " + $_.Name;
"--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
"--Failover MS :: " + ($managementServer.ComputerName);
Write-Host "";
http://www.systemcentercentral.com/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr/

SCOM 2012 UR2 - Flush health service state causes infinite agent resets

Appearing on several of our 2008R2 servers from our SCOM 2012 UR2 environment, set up with several management servers:
If I select a monitored servers agent in the Operator Console and click the task
Flush health service state and cache, the selected agent will restart as intended.
However, it will restart again every 2-3 minutes forever ever after, unless you stop the agent service and delete the health service cache folder on the monitored server.
This is visible via the eventlog:
event 103, Healthservice. A task to reset the health service store has been submitted. The service store will be deleted and re-created.
This was never the case with our SCOM2007R2 setup and started appearing with 2012.
Have anyone seen this before? Any ideas?
Regards / Jon

Might save someone some time....
Stopping the agent, removing the "Health Service State" directory + restarting doesn't appear to help. I did this *and* deleted some agents from the console (then re-added them. We turned auto approve off) and it appears
it might have fixed it. I'll know more in the morning if this actually does the trick besides doing a full uninstall/reinstall of the agent.
If you don't know what agents are constantly restarting, search all management servers for *many* file transfers (Event ID 2110 in Ops manager event log) all to the same Instance/GUID. Execute this powershell on a managemnt server: "get-SCOMClassInstance
-Id <GUID>" to get the affected agent. Alternatively, make a SCOM rule to catch event 103 and look for many repeats from the same server/agent:
Event Type: Warning
Event Source: HealthService
Event Category: Health Service
Event ID: 103
Description:
A task to reset the health service store has been submitted. The service store will be deleted and re-created.

SCOM 2012 - Event ID 6024 (Launching Restart Health Service. Health Service exceeded Process\Handle Count or Private Bytes threshhold.)

I am getting event ID 6024 (LaunchRestartHealthService.js : Launching Restart Health Service. Health Service exceeded Process\Handle Count or Private Bytes threshhold.) within an interval ranging from 12-17 minutes.
I am using SCOM (2012 SP1 and 2012 R2) on Windows Server (2008 R2 / 2012 / 2012 R2).
This issue is occurring only on agent managed computer (acting as proxy and discover managed objects on other computers setting is enabled) which i am using for monitoring my device. All discovery scripts (powershell) and monitors are targeted on this agent
managed computer.
There are total 80 discoveries and 900 monitors. 55 discoveries and 550 monitors are enabled by default and rest all are disabled.
I am seeing event id 6024 frequently only on agent managed computer. Can anyone help me to resolve this issue.
Thanks,
Mukul

To fix issue 6024, you can follow below steps:
1. Open SCOM console. Go to Monitors -> Agent -> Entity Health -> Performance -> Health Service Performance -> Health Service State.
2. Double click Health Service Handle Count Threshold monitor and go to Overrides page.
3. Click Override -> For a specific object of Class: Agent. Select the affected SCOM agent QMXServer.
4. Check on the parameter Agent Performance Monitor Type - Threshold. Change the default value 2000 to an appropriate value, like 4000. You can check the Health service handle count alert in SCOM console to get the value when the alert is generated. You
can also launch the health explorer against QMXServer to check the value when the monitor state is changed from healthy to critical.
Also you can refer below links
http://blogs.technet.com/b/omx/archive/2013/10/17/health-service-restarts-on-service-manager-servers-with-scom-agents.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

[Forum FAQ] Troubleshooting error "The specified SQL server instance is not valid" when installing SCOM reporting service

Symptom
If you have failed to install SCOM reporting service, you may encounter below error when you reinstall it:
“The specified SQL server instance is not valid”.
(Figure 1)
Figure 1.
Reason
This issue may be caused by multiple reasons, for example the reasons in Figure 1.
However, you may find that SSRS and Report Server website are configured correctly and no SSL or proxy Server is used. In these scenario, you can open the log file under path
to find the root reason:
C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles
Later, you will find the error as below:
ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDisabledException: , Microsoft.ReportingServices.Library.ReportServerDisabledException:
The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException
(0x80090016): Keyset does not exist (Exception from HRESULT: 0x80090016)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ReencryptSymmetricKey(Byte[] symKeyBlob, Byte[] pPublicKeyBlob)
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
--- End of inner exception stack trace ---;
Solution
According to the error message, you can delete encrypted content by following the steps below:
Open SQL Reporting Services Configuration Manager.
Select “Encryption Keys”.
Click “Delete” to delete all encrypted content. (Figure 2)
Figure 2.
After that, we can install SCOM reporting service again, after successfully install reporting service, we should see the SCOM operation console as below:
Figure 3.
In addition, you may also encounter other errors when installing SCOM reporting service, and the troubleshooting steps may be different. However, we can also check SQL reporting
service logs to find the root reason.
Here are some articles that would be helpful for SCOM reporting service installation and troubleshooting:
How to Install the Operations Manager Reporting Server
http://technet.microsoft.com/en-us/library/hh298611.aspx
Unable to install SCOM 2012 Reporting Services
http://blogs.technet.com/b/mdegre/archive/2013/05/27/unable-to-install-scom-2012-reporting-services.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hello,
I'm afraid you must use a dedicated instance of SQL Server for each site(SCOM/SCCM). Some similar issues were disscussed on this forum:
SCCM and SCOM - SQL Server
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/bfa14da9-4692-4c64-a107-e085c967d259
SCOM, SCCM, SQL on same server?
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/b5373aa7-5233-4b1f-9b39-b86e481e04d5
Thanks,
Yog Li
TechNet Community Support

The Security Token Service is not available error on dedicated Distributed Cache server

I have an error on a dedicated Distributed Cache server stating that the Security Token Service is not available. I was under the impression that when Distributed Cache was running on a dedicated server that the only service that should be enabled
is Distributed Cache.
The token service is working as expected on all other servers but this one. Does this service need to be started or should I just ignore this error message?
Jennifer Knight (MCITP, MCPD)

as per my little experience with 2013, if STS is working fine on Web server then I am sure that sharepoint will be fine...Distributed cache stores the ST issued by STS. NO need to worry about this error.
Login
Token Cache
DistributedLogonTokenCache
This
cache stores the security token issued by a Secure Token Service for use by any web server in the server farm. Any web server that receives a request for resources can access the security token from the cache, authenticate the user, and provide access to the
resources requested.
I would say check the ULS logs and get more details about the error why its not working on that server.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Manages Exchange server health Service is NOT starting after installing EDGE role using Exchange2013 SP1+CU5 setup

I used Exchange 2013 SP1+CU5 to install Edge role on Windows server 2012 R2 workgroup machine
then after installation the service "Exchange server health Service" was not starting automatically or manually with the following error "Error 1075: The dependency service does not exist or has been marked for deletion"
and in the Event Viewer I have this error:
Event Id: 7003
The Microsoft Exchange Health Manager service depends on the following service: MSExchangeADTopology. This service might not be installed.
please advice

The Exchange 2013 Edge Role has a reduced set of services compare to a CAS or MBX server role:
Active Directory Web Services
Microsoft Exchange ADAM
Microsoft Exchange Anti-spam Update
Microsoft Exchange Diagnostics
Microsoft Exchange Credential Service
Microsoft Exchange Health Manager
Microsoft Exchange Service Host
Microsoft Exchange Transport
Microsoft Exchange Transport Log Search
The above one was from Exchange 2013 Sp1. Not sure whether Microsoft Exchange Health Manager service has been replaced from CU5.
Just restart the edge server once again and ensure that you are able to see this service again in services console.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

How is called the Services "OpsMgr Health Service" in the SCOM 2012 and Client machine?

Hi,
Can anybody tell me how is called the Services of OpsMgr Health Service in the SCOM 2012?
I have installed the agent of scom2012 on my client computer. But I dont find any agent called "OpsMgr Health Service" on the Client machine?
Regards

Hi
If you look in the services.msc window then it is listed as the System Center Management Service. This is the display name.
The actual service name is HealthService
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
The Ayman answer is god, It is called "Microsoft Monitoring Agent"

Event IDs 508,509 and 510 (Health Service ESE Store) on SCOM agents

Hi Team,
Many of my SCOM agents are getting the Event IDs 508,509 and 510 on them.
HealthService (2944) Health Service Store: A request to write to the file "C:\Program Files\System Center Operations Manager\Agent\Health Service State\Health Service Store\edb.log" at offset 1485312 (0x000000000016aa00) for 512 (0x00000200)
bytes succeeded, but took an abnormally long time (60 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Because of these events I keep getting "Health Service Heartbeat Failure" Alerts in SCOM whenever these events occur on the agents. After a couple of minutes these alerts get auto resolved and closed.
Has anyone faced a similar issue and let me know what should be done here to solve the issue.
Thanks,
S K Agrawal

I am still not able to resolve the issue. But I came to know that the servers that had this issue were having some issue with the blade servers they all were hosted on and probably this is the issue they got these Event IDs.
I am closing this as a faulty hardware issue on the servers.
Thanks, S K Agrawal

SCOM Health Service Watcher / Server Availability...

Similar Messages

Maybe you are looking for