ServerHealth on CasServer Healthset RPS.ProxyResource MSExchangePowerShellFrontEndAppPool Status Unhealthy
Hi,
our cas-Server reports an Unhealthy Healthset:
get-healthreport -server casserver| where {$_.alertvalue -ne "healthy"} | ft -auto
Server State HealthSet AlertValue LastTransitionTime MonitorCount
casserver Online RPS.Proxy Unhealthy 28.10.2014 10:42:57 1
and
$issues = Get-HealthReport -server casserver | where {$_.alertvalue -ne "healthy"}
foreach ($line in $issues) {$line.entries | where {$_.alertvalue -ne "healthy"} | ft -auto}
Server State Name TargetResource HealthSetName AlertValue ServerComponent
casserver Online RPSProxyTestMonitor MSExchangePowerShellFrontEndAppPool RPS.Proxy Unhealthy RpsProxy
i can connect to OWA and ECP under https://localhost/owa and "https://casserver.domain.int/owa"
but i cant connect to https://localhost/powerShell/ and https://casserver.domain.int/powerShell
The Exchange Default Website and BackEnd have an SAN Cert with alle names in the cert:
CN = autodiscover.domain.int
DNS Name=autodiscover.domain.int
DNS Name=autodiscover
DNS Name=mail.domain.int
DNS Name=mail DNS Name=casserver.domain.int
DNS Name=casserver
DNS Name=mgmtcasserver.domain.int
DNS Name=cmgmtasserver
DNS Name=localhost
DNS Name=10.20.40.54
DNS Name=10.50.60.72
The PowerShell Directory Points to "D:\Exchange2013\ClientAccess\PowerShell"
Can anyone help?
Hi Joerg,
According to your description, I cannot understand what your problem is.
Could you please explain it in more detail?
Best regards,
Niko Cheng
TechNet Community Support
Similar Messages
-
Compliance HealthSet unhealthy
Hello,
Today at 8 AM our Exchange 2013 server compliance health set went into unhealthy state. I would like help understanding what this means and what kind of negative impacts this could have on the email server. I'm not sure where to go here but it
looks like out of the HealthSet 'Compliance' everything is Healthy except for ELCDumpsterWarnin...
What does this mean and where should I look next?
[PS] C:\Windows\system32>Get-ServerHealth -Identity 'EMAIL' -HealthSet 'Compliance'
Server State Name TargetResource HealthSetName AlertValue ServerComp
onent
EMAIL NotApplicable AuditLogSearchCom... Compliance Compliance Healthy None
EMAIL NotApplicable MailboxSearch.Inc... Compliance Compliance Healthy None
EMAIL NotApplicable MailboxSearch.RPC... Compliance Compliance Healthy None
EMAIL NotApplicable MaintenanceFailur... Compliance Healthy None
EMAIL NotApplicable MaintenanceTimeou... Compliance Healthy None
EMAIL NotApplicable JournanlingMonitor Compliance Compliance Healthy None
EMAIL NotApplicable ComplianceOutlook... Compliance Healthy None
EMAIL NotApplicable ComplianceOutlook... Compliance Healthy None
EMAIL NotApplicable AsyncSearchServic... Compliance Compliance Healthy None
EMAIL NotApplicable Hold.HoldErrors.M... Compliance Compliance Healthy None
EMAIL NotApplicable PermanentPolicyAp... Compliance Compliance Healthy None
EMAIL NotApplicable UnknownPolicyAppl... Compliance Compliance Healthy None
EMAIL NotApplicable ELCTransientMonitor Compliance Compliance Healthy None
EMAIL NotApplicable ELCPermanentMonitor Compliance Compliance Healthy None
EMAIL NotApplicable ELCMailboxSLAMonitor Compliance Compliance Healthy None
EMAIL NotApplicable ELCDumpsterWarnin... Compliance Compliance Unhealthy None
EMAIL NotApplicable ChildPolicyApplic... Compliance Compliance Healthy None
EMAIL NotApplicable ApplyPolicyErrorM... Compliance Compliance Healthy None
EMAIL NotApplicable RuleExecutionErro... Compliance Compliance Healthy None
EMAIL NotApplicable DarTaskErrorMonitor Compliance Compliance Healthy None
EMAIL NotApplicable RetryTimeoutDarTa... Compliance Compliance Healthy None
EMAIL NotApplicable JournalFilterAgen... Compliance Compliance Healthy NoneOk well the only thing I noticed is that out of my 4 databases, under limits, only DB1 was set to unlimited for Issue a warning at, prohibit send at, and prohibit send and recieve at. I think DB2, 3, and 4 were set to 4GB and 3.8GB (for the warning).
I made all 4 of my databases match. About 15 minutes later this compliance healthset went into a healthy state.
It's just difficult to grasp the health sets and determine why something goes unhealthy and what to do about it. There's no user interface into this besides some command lines and digging into event logs. -
Since we installed CU6 last thursday evening, we are now getting the below healthset alerts:
Alert: Health Set unhealthy
Source: SERVNAME - Compliance
Path: Servername.domain.com;servname.domain.com
Last modified by: System
Last modified time: 9/30/2014 9:33:22 AM Alert description: Hold errors. Exception Details: .
Probe Exception: 'Microsoft.Exchange.Data.Storage.DumpsterOperationException: Copy to dumpster failed. The error message is Move 1 item(s) to the dumpster folder RecoverableItemsDeletions failed on mailbox /o=Contoso/ou=CS/cn=Recipients/cn=finance/cn=JKorth,
which is on hold. This operation is from client Client=MSExchangeRPC and its result is PartiallySucceeded. ---> Microsoft.Exchange.Data.Storage.PartialCompletionException: Move/Copy messages failed. ---> Microsoft.Mapi.MapiExceptionPartialCompletion:
MapiExceptionPartialCompletion: Unable to copy message(s). (hr=0x40680, ec=0) Diagnostic context:
Is anyone else experiencing this? I've traversed all the logs on the servers that its happening on but cant find much to go on. Just that the process failed, but no reason as to why it failed. This started immediately after CU6 was installed.
RichHi Rich,
How about the Exchange 2013 CU6 workflow, does it work fine? If there is anything abnormal or some operations can't be performed, please give a response.
I suggest move JKorth's mailbox to another database and restart MSExchangeMailboxAssistants service for test.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support -
DAG Sporadic Entire Server DB Fail Over
Hi,
I have been having this issues for a while now, I have two physical exchange servers in a DAG, both on Exchange 2013 CU1. Randomly, every few days and various times, Server1 will fail all of it's databases over to Server2. I'll redistribute them, and again,
say Server2 will fail all databases to Server1. In short, both servers at times have failed their databases over.
I started with this: http://technet.microsoft.com/en-us/library/dd351258(v=exchg.150).aspx which led me to setup monitoring of the Microsoft-Exchange-ManagedAvailability logs. I can tell you that replication tests work fine, and the health of all the
databases are fine.
My monitoring turned up the following errors, in this example "EX0001" was the server that failed all of it's databases over to "EX0002". It seems pretty clear to me, that Exchange Managed Availability, is finding an issue with
EWS, attempting to restart the MSExchangeServicesApp pool and cannot due to "Throttling" so ti fails the DB's over, that's my best guess...the problem is I dont know how to fix this...I've run through troubleshooting EWS Healthset, nothing
really turns up... http://technet.microsoft.com/en-us/library/ms.exch.scom.ews.protocol(v=exchg.150).aspx
EX0001
1011
Microsoft-Exchange-ManagedAvailability
Recovery
Microsoft-Exchange-ManagedAvailability/RecoveryActionLogs
5/22/2014 7:06:43 AM
Warning (Info)
1520183
NT AUTHORITY\SYSTEM
RecycleApplicationPool-MSExchangeServicesAppPool-EWSSelfTestRestart: Throttling rejected the operation
EX0001
4
Microsoft-Exchange-ManagedAvailability
Monitoring
Microsoft-Exchange-ManagedAvailability/Monitoring
5/22/2014 7:17:27 AM
Error (Info)
8287
NT AUTHORITY\SYSTEM
The EWS.Protocol health set has detected a problem on EX0001 beginning at 5/22/2014 10:55:12 AM (UTC). The health manager is reporting that recycling the MSExchangeServicesAppPool
app pool has failed to restore health and it has tried to fail over active copies of local databases to a healthy server. Attempts to auto-recover from this condition have failed and requires Administrator attention. Details below: <b>MachineName:</b>
EX0001 <b>ServiceName:</b> EWS.Protocol <b>ResultName:</b> EWSSelfTestProbe/MSExchangeServicesAppPool <b>Error:</b> System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) <b>Exception:</b> System.Exception: System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.ThrowError(Object key, Object exceptiondata, String logDetails) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.RunEWSGenericProbe(CancellationToken cancellationToken) at Microsoft.Exchange.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken) at Microsoft.Exchange.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute() <b>ExecutionContext:</b> EWSGenericProbeError:Exception=System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon
<b>FailureContext:</b> <b>ResultType:</b> Failed <b>IsNotified:</b> False <b>DeploymentId:</b> 0 <b>RetryCount:</b> 0 <b>ExtensionXml:</b> <b>Version:</b> <b>StateAttribute1:</b>
EWS <b>StateAttribute2:</b> Unknown <b>StateAttribute3:</b> <b>StateAttribute4:</b> <b>StateAttribute5:</b> <b>StateAttribute6:</b> 0 <b>StateAttribute7:</b> 0 <b>StateAttribute8:</b>
0 <b>StateAttribute9:</b> 0 <b>StateAttribute10:</b> 0 <b>StateAttribute11:</b> <b>StateAttribute12:</b> <b>StateAttribute13:</b> <b>StateAttribute14:</b> <b>StateAttribute14:</b>
<b>StateAttribute16:</b> 0 <b>StateAttribute17:</b> 0 <b>StateAttribute18:</b> 0 <b>StateAttribute19:</b> 0 <b>StateAttribute20:</b> 120011 <b>StateAttribute21:</b> [000.000] EWSCommon
start: 5/22/2014 11:13:13 AM [000.000] Configuring EWScommon [000.000] Probe time limit: 120000ms, HTTP timeout: 59500ms, RetryCount: 1 [000.047] using authN: CAFE
[email protected] xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt
[000.047] using HTTP request timeout: 59500 ms [000.047] action iteration 0 [000.047] starting (total time left 119954 ms) [059.568] action threw Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The operation has timed out [064.584]
action iteration 1 [064.584] starting (total time left 55416 ms) [120.011] action wait timed out [120.011] action threw System.TimeoutException: iteration 1; 55.427003 seconds elapsed <b>StateAttribute22:</b> <b>StateAttribute23:</b>
<b>StateAttribute24:</b> <b>StateAttribute25:</b> <b>PoisonedCount:</b> 0 <b>ExecutionId:</b> 32395373 <b>ExecutionStartTime:</b> 5/22/2014 11:13:13 AM <b>ExecutionEndTime:</b> 5/22/2014
11:15:13 AM <b>ResultId:</b> 253233015 <b>SampleValue:</b> 0 ------------------------------------------------------------------------------- States of all monitors within the health set: Note: Data may be stale. To get current data,
run: Get-ServerHealth -Identity 'EX0001' -HealthSet 'EWS.Protocol' State Name TargetResource HealthSet AlertValue ServerComponent ----- ---- -------------- --------- ---------- --------------- NotApplicable EWSSelfTestMonitor MSExchangeServicesAppPool EWS.Protocol
Unhealthy None NotApplicable EWSDeepTestMonitor DG01DB15 EWS.Protocol Unhealthy None NotApplicable PrivateWorkingSetWarningThresholdExc... msexchangeservicesapppool EWS.Protocol Healthy None NotApplicable ProcessProcessorTimeErrorThresholdEx... msexchangeservicesapppool
EWS.Protocol Healthy None NotApplicable ExchangeCrashEventErrorThresholdExce... msexchangeservicesapppool EWS.Protocol Healthy None States of all health sets: Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX0001' State HealthSet
AlertValue LastTransitionTime MonitorCount ----- --------- ---------- ------------------ ------------ NotApplicable Autodiscover.Protocol Healthy 3/8/2014 12:46:17 AM 4 NotApplicable ActiveSync.Protocol Healthy 3/8/2014 1:15:35 AM 7 NotApplicable ActiveSync
Healthy 3/8/2014 2:08:15 AM 3 NotApplicable EDS Healthy 5/22/2014 5:19:41 AM 13 NotApplicable ECP Healthy 3/8/2014 1:15:27 AM 3 NotApplicable EventAssistants Healthy 5/22/2014 5:48:56 AM 28 NotApplicable EWS.Protocol Unhealthy 5/22/2014 7:07:12 AM 5 NotApplicable
FIPS Healthy 5/21/2014 10:24:01 PM 18 NotApplicable AD Healthy 2/23/2014 10:42:29 PM 10 NotApplicable OWA.Protocol.Dep Healthy 5/22/2014 5:19:40 AM 1 NotApplicable Monitoring Unhealthy 5/22/2014 5:35:31 AM 9 Online HubTransport Unhealthy 5/22/2014 5:19:43
AM 138 NotApplicable DataProtection Healthy 5/22/2014 7:08:02 AM 201 NotApplicable AntiSpam Healthy 5/22/2014 5:19:40 AM 4 NotApplicable Network Healthy 5/21/2014 10:36:54 PM 1 NotApplicable OWA.Protocol Healthy 3/8/2014 1:15:34 AM 5 NotApplicable MailboxMigration
Healthy 3/8/2014 12:46:18 AM 4 NotApplicable MRS Healthy 3/8/2014 12:44:35 AM 9 NotApplicable MailboxTransport Healthy 5/22/2014 5:19:41 AM 57 NotApplicable PublicFolders Healthy 5/21/2014 10:44:15 PM 4 NotApplicable RPS Healthy 2/23/2014 11:38:33 PM 1 NotApplicable
Outlook.Protocol Healthy 4/22/2014 11:04:18 AM 3 NotApplicable UserThrottling Healthy 5/22/2014 5:51:13 AM 7 NotApplicable SiteMailbox Healthy 3/8/2014 2:10:53 AM 3 NotApplicable UM.Protocol Healthy 5/22/2014 5:19:41 AM 17 NotApplicable Store Healthy 5/22/2014
5:19:43 AM 225 NotApplicable MSExchangeCertificateDeplo... Disabled 1/1/0001 12:00:00 AM 2 NotApplicable DAL Healthy 8/2/2013 12:59:03 AM 16 NotApplicable Search Healthy 5/22/2014 5:37:18 AM 269 Online EWS.Proxy Healthy 5/5/2014 1:34:08 AM 1 Online RPS.Proxy
Healthy 5/5/2014 1:34:38 AM 13 Online OAB.Proxy Healthy 5/5/2014 1:34:37 AM 1 Online ECP.Proxy Healthy 5/5/2014 1:34:17 AM 4 Online OWA.Proxy Healthy 5/5/2014 1:34:25 AM 2 Online Outlook.Proxy Healthy 5/5/2014 1:34:08 AM 1 Online Autodiscover.Proxy Healthy
5/5/2014 1:34:08 AM 1 Online ActiveSync.Proxy Healthy 5/5/2014 1:34:35 AM 1 Online RWS.Proxy Healthy 5/5/2014 1:34:18 AM 10 NotApplicable Autodiscover Healthy 5/21/2014 10:24:01 PM 2 Online FrontendTransport Healthy 5/15/2014 12:49:31 AM 11 NotApplicable EWS
Unhealthy 5/22/2014 7:06:01 AM 2 NotApplicable OWA Healthy 2/23/2014 11:37:56 PM 1 NotApplicable Outlook Healthy 3/8/2014 12:45:14 AM 5 Online UM.CallRouter Healthy 5/22/2014 5:19:41 AM 7 NotApplicable RemoteMonitoring Healthy 8/2/2013 12:58:03 AM 1 NotApplicable
POP.Protocol Healthy 5/20/2014 9:22:12 AM 5 NotApplicable IMAP.Protocol Healthy 5/20/2014 9:22:21 AM 5 Online POP.Proxy Healthy 3/7/2014 1:31:10 PM 1 Online IMAP.Proxy Healthy 3/7/2014 1:31:10 PM 1 NotApplicable IMAP Healthy 5/20/2014 9:23:32 AM 2 NotApplicable
POP Healthy 5/20/2014 9:17:18 AM 2 NotApplicable Antimalware Healthy 5/15/2014 8:33:13 AM 8 NotApplicable FfoQuarantine Healthy 8/2/2013 12:58:20 AM 1 Online Transport Healthy 5/22/2014 5:38:00 AM 9 NotApplicable Security Healthy 3/8/2014 12:46:09 AM 3 NotApplicable
Datamining Healthy 3/8/2014 12:45:44 AM 3 NotApplicable Provisioning Healthy 3/8/2014 12:45:40 AM 3 NotApplicable ProcessIsolation Healthy 3/8/2014 12:47:05 AM 12 NotApplicable TransportSync Healthy 3/8/2014 12:45:37 AM 3 NotApplicable MessageTracing Healthy
3/8/2014 12:44:56 AM 3 NotApplicable CentralAdmin Healthy 3/8/2014 12:45:12 AM 3 NotApplicable OAB Healthy 8/2/2013 1:02:27 AM 3 NotApplicable Calendaring Healthy 8/2/2013 1:02:07 AM 3 NotApplicable PushNotifications.Protocol Healthy 2/23/2014 10:46:17 PM
3 NotApplicable Ediscovery.Protocol Healthy 5/21/2014 10:38:16 PM 1 NotApplicable HDPhoto Healthy 5/6/2014 9:36:25 AM 1 NotApplicable Clustering Healthy 3/8/2014 12:45:34 AM 4 NotApplicable DiskController Healthy 4/22/2014 2:51:30 AM 1 NotApplicable MailboxSpace
Healthy 5/22/2014 6:16:51 AM 96 NotApplicable FreeBusy Healthy 5/22/2014 5:32:54 AM 1 Note: Subsequent detected alerts are suppressed until the health set is healthy again.Hi,
Based on the error message, throttling rejected the operation. I recommend you use the Get-ThrottlingPolicy | fl cmdlet to view EWS settings in throttling policy.
You can modify the default throttling policy and set the basic settings for EWS. Then restart the Microsoft Exchange Throttling service and recycle the MSExchangeServicesAppPool to check the result.
For more information about the EWS throttling, you can refer to the following articles.
EWS throttling in Exchange
http://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
EWS Best Practices: Understand Throttling Policies
http://blogs.msdn.com/b/mstehle/archive/2010/11/09/ews-best-practices-understand-throttling-policies.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support -
Managed Availability MapiExceptionMultiMailboxSearchFailed
Hello Everyone,
Have a fresh Exchange 2013 SP1 install setup and before we start to make any changes towards coexistence we would like to know how to resolve the below alerts on our 4 mailbox servers.
First Event:
Probe: EdiscoveryDeepTestProbe/Mailbox Database 2031363269
Latency: 0ms
Error: MapiExceptionMultiMailboxSearchFailed: Multi Mailbox Keyword Stats Search failed. (hr=0x80004005, ec=2802)
Diagnostic context:
Lid: 1494 ---- Remote Context Beg ----
Lid: 55392 StoreEc: 0xAF2
Lid: 32864 StoreEc: 0xAF2
Lid: 42621 StoreEc: 0xAF2
Lid: 1750 ---- Remote Context End ----
Lid: 63080
Lid: 38504 StoreEc: 0xAF2
Lid: 58984
Lid: 34408 StoreEc: 0xAF2
Details:
Log:
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'NCITSMBX02' -HealthSet 'Ediscovery.Protocol'
State Name
TargetResource HealthSet
AlertValue ServerComponent
NotApplicable EdiscoveryDeepTestMonitor
Ediscovery.Protocol Healthy None
Second Event:
Search has unhealthy copy status for mounted database 'Mailbox Database 2031363269'. The last probe error was:
Search catalog is in 'FailedAndSuspended' state for mounted database 'Mailbox Database 2031363269'. Failover has been tried already but did not solve the problem.
Status of all copies of the database among servers:
Copy: 'Mailbox Database 2031363269\NCITSMBX02', Database Status: 'Mounted', Content Index Status: 'FailedAndSuspended', Error Message: 'The content index is corrupted.'.
Please let me know if you need anymore information. Thanks for any assistance!Hi Gulab,
Thanks for the response. These are standalone servers (total of 4 mailbox servers) with no DAG.
These errors are happening on all databases (which on on the servers right now).
Error 1:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: Microsoft-Exchange-ManagedAvailability
Date: 6/12/2014 9:38:04 AM
Event ID: 4
Task Category: Monitoring
Level: Error
Keywords:
User: SYSTEM
Computer: NCITSMBX02.domain.local
Description:
Probe: EdiscoveryDeepTestProbe/Mailbox Database 2031363269
Latency: 0ms
Error: MapiExceptionMultiMailboxSearchFailed: Multi Mailbox Keyword Stats Search failed. (hr=0x80004005, ec=2802)
Diagnostic context:
Lid: 1494 ---- Remote Context Beg ----
Lid: 55392 StoreEc: 0xAF2
Lid: 32864 StoreEc: 0xAF2
Lid: 42621 StoreEc: 0xAF2
Lid: 1750 ---- Remote Context End ----
Lid: 63080
Lid: 38504 StoreEc: 0xAF2
Lid: 58984
Lid: 34408 StoreEc: 0xAF2
Details:
Log:
Note: Subsequent detected alerts are suppressed until the health set is healthy again.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-06-12T13:38:04.712079000Z" />
<EventRecordID>830</EventRecordID>
<Correlation />
<Execution ProcessID="11740" ThreadID="5864" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>NCITSMBX02.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>Ediscovery.Protocol</HealthSet>
<Subject>Ediscovery.Protocol health set unhealthy (EdiscoveryDeepTestMonitor) - EdiscoveryDeepTestMonitor is failing on NCITSMBX02</Subject>
<Message>Probe: EdiscoveryDeepTestProbe/Mailbox Database 2031363269
Latency: 0ms
Error: MapiExceptionMultiMailboxSearchFailed: Multi Mailbox Keyword Stats Search failed. (hr=0x80004005, ec=2802)
Diagnostic context:
Lid: 1494 ---- Remote Context Beg ----
Lid: 55392 StoreEc: 0xAF2
Lid: 32864 StoreEc: 0xAF2
Lid: 42621 StoreEc: 0xAF2
Lid: 1750 ---- Remote Context End ----
Lid: 63080
Lid: 38504 StoreEc: 0xAF2
Lid: 58984
Lid: 34408 StoreEc: 0xAF2
Details:
Log:
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'NCITSMBX02' -HealthSet 'Ediscovery.Protocol'
State Name
TargetResource HealthSet
AlertValue ServerComponent
NotApplicable EdiscoveryDeepTestMonitor
Ediscovery.Protocol Healthy None
States of all health sets:
Note: Subsequent detected alerts are suppressed until the health set is healthy again.</Message>
<Monitor>EdiscoveryDeepTestMonitor</Monitor>
</EventXML>
</UserData>
</Event>
Event 2:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: Microsoft-Exchange-ManagedAvailability
Date: 6/12/2014 9:22:20 AM
Event ID: 4
Task Category: Monitoring
Level: Error
Keywords:
User: SYSTEM
Computer: NCITSMBX02.domain.local
Description:
Search has unhealthy copy status for mounted database 'Mailbox Database 2031363269'. The last probe error was:
Search catalog is in 'FailedAndSuspended' state for mounted database 'Mailbox Database 2031363269'. Failover has been tried already but did not solve the problem.
Status of all copies of the database among servers:
Copy: 'Mailbox Database 2031363269\NCITSMBX02', Database Status: 'Mounted', Content Index Status: 'FailedAndSuspended', Error Message: 'The content index is corrupted.'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-06-12T13:22:20.783351100Z" />
<EventRecordID>829</EventRecordID>
<Correlation ActivityID="{BACB36F3-F55B-49E8-ACEF-0D549F2154DE}" />
<Execution ProcessID="11740" ThreadID="6988" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>NCITSMBX02.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>Search</HealthSet>
<Subject>E15: Search has unhealthy copy status for mounted database 'Mailbox Database 2031363269'</Subject>
<Message>Search has unhealthy copy status for mounted database 'Mailbox Database 2031363269'. The last probe error was:
Search catalog is in 'FailedAndSuspended' state for mounted database 'Mailbox Database 2031363269'. Failover has been tried already but did not solve the problem.
Status of all copies of the database among servers:
Copy: 'Mailbox Database 2031363269\NCITSMBX02', Database Status: 'Mounted', Content Index Status: 'FailedAndSuspended', Error Message: 'The content index is corrupted.'.
</Message>
<Monitor>SearchMountedCopyStatusMonitor/Mailbox Database 2031363269</Monitor>
</EventXML>
</UserData>
</Event> -
Hello,
I'm getting several times per day the following alert in the Event Viewer of both my Mailbox Role servers which then raise an alert in SCOM 2012:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: ManagedAvailability
Event ID: 4
Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate.
I'm not able to find information about what is being monitored and how to get rid of this events.
Any help appreciated.
Thank you in advance.
Raffaele ZamunerHi Amit,
here's the output from the EMS and the Event Viewer:
[PS] C:\Windows\system32>Get-ServerHealth [ServerName] | ?{$_.alertvalue -ne "Healthy" -and $_.alertvalue -ne "Disabled"}
Server State Name TargetResource
HealthSetName AlertValue ServerComp
onent
[ServerName] NotApplicable ScanTimeMeanMonitor FIPS
Unhealthy None
[ServerName] NotApplicable MaintenanceFailur... DAL
Unknown None
[ServerName] NotApplicable DatabaseLogicalPh... FINIT MailboxSpace Repairing None
[ServerName] NotApplicable DatabaseLogicalPh... MailboxSpace
Unhealthy None
[ServerName] Online Total.Shadow.Queu...
HubTransport Unhealthy HubTran...
[ServerName] NotApplicable MailboxDeliveryAv... MailboxTrans... Unhealthy
None
[ServerName] NotApplicable DatabaseLogicalPh... DB1 MailboxSpace Repairing None
[ServerName] NotApplicable DatabaseLogicalPh... MCS1 MailboxSpace Repairing None
[PS] C:\Windows\system32>get-serverhealth -Server [ServerName] -HealthSet AMScanTimeou
[PS] C:\Windows\system32>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-06-03T07:23:16.626852900Z" />
<EventRecordID>1753</EventRecordID>
<Correlation />
<Execution ProcessID="1860" ThreadID="21496" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>[ServerName].finit.local</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>FIPS</HealthSet>
<Subject>FIPS health set unhealthy (ScanTimeMeanMonitor) - High Mean Scan Time</Subject>
<Message>Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate. ------------------------------------------------------------------------------- States of all monitors within the health set: Note: Data may be stale.
To get current data, run: Get-ServerHealth -Identity '[ServerName]' -HealthSet 'FIPS' State Name TargetResource HealthSet AlertValue ServerComponent ----- ---- -------------- --------- ---------- --------------- NotApplicable ScanProcessesRunningMonitor FIPS
Healthy None NotApplicable ScanProcessBelowMinimumMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutUrgentMonitor FIPS Healthy None NotApplicable ScanRequestQueueTimeoutUrgentMonitor FIPS
Healthy None NotApplicable RecoveryQueueTimeoutUrgentMonitor FIPS Healthy None NotApplicable ScanTimeMeanMonitor FIPS Healthy None NotApplicable ScanRequestErrorRatioMonitor FIPS Healthy None NotApplicable ScanRequestErrorsMonitor FIPS Healthy None NotApplicable
TextExtractionErrorsMonitor FIPS Healthy None NotApplicable ObsoleteEngineInUseEventMonitor FIPS FIPS Healthy None NotApplicable MaintenanceFailureMonitor.FIPS FIPS Healthy None NotApplicable EngineNotEnabledForUpdatesEventMonitor FIPS FIPS Healthy None NotApplicable
EUSTerminationEventMonitor FIPS FIPS Healthy None NotApplicable EUSUnableToStartEventMonitor FIPS FIPS Healthy None NotApplicable ADFilteringSettingsWatcherStartFaile... FIPS FIPS Healthy None NotApplicable ScanningProcessRepeatedlyCrashingMon... FIPS FIPS
Healthy None NotApplicable FilteringManagementServiceDownMonitor FIPS Healthy None NotApplicable PrivateWorkingSetWarning.fms fms FIPS Healthy None NotApplicable PrivateWorkingSetError.fms fms FIPS Healthy None NotApplicable ProcessProcessorTimeWarning.fms
fms FIPS Healthy None NotApplicable ProcessProcessorTimeError.fms fms FIPS Healthy None NotApplicable ExchangeCrashEventError.fms fms FIPS Healthy None NotApplicable LongRunningWatsonWarning.fms fms FIPS Healthy None NotApplicable LongRunningWerMgrWarning.fms
fms FIPS Healthy None NotApplicable MicrosoftFailedUpdatesMonitor FIPS Healthy None NotApplicable MicrosoftEngineErrorsMonitor FIPS Healthy None NotApplicable MSClassificationEngineErrorsMonitor FIPS Healthy None States of all health sets: Note: Data may be
stale. To get current data, run: Get-HealthReport -Identity '[ServerName]' State HealthSet AlertValue LastTransitionTime MonitorCount ----- --------- ---------- ------------------ ------------ NotApplicable ActiveSync.Protocol Healthy 03/06/2014 05.04.35 9
NotApplicable Autodiscover.Protocol Healthy 03/06/2014 01.18.16 9 NotApplicable ActiveSync Healthy 03/06/2014 08.24.19 1 NotApplicable Antimalware Unhealthy 03/06/2014 09.18.14 11 NotApplicable ECP Healthy 03/06/2014 08.40.07 5 NotApplicable Ediscovery.Protocol
Healthy 03/06/2014 08.55.21 1 NotApplicable AD Healthy 03/06/2014 07.46.15 19 NotApplicable EDS Healthy 03/06/2014 08.52.30 90 NotApplicable EventAssistants Healthy 03/06/2014 09.21.03 15 NotApplicable EWS.Protocol Healthy 03/06/2014 09.15.04 11 NotApplicable
FEP Healthy 02/06/2014 09.04.40 2 NotApplicable FIPS Healthy 03/06/2014 09.15.34 28 NotApplicable Monitoring Healthy 03/06/2014 07.53.12 17 NotApplicable MailboxMigration Healthy 02/06/2014 14.03.19 3 Online UM.CallRouter Healthy 03/06/2014 04.44.11 8 NotApplicable
UM.Protocol Healthy 03/06/2014 05.05.45 22 NotApplicable OAB Healthy 03/06/2014 09.22.26 8 Online HubTransport Unhealthy 03/06/2014 09.22.35 133 NotApplicable EAS Healthy 02/05/2014 10.33.27 1 NotApplicable Autodiscover Healthy 03/06/2014 05.56.59 1 NotApplicable
DataProtection Healthy 03/06/2014 09.18.11 66 NotApplicable FreeBusy Healthy 02/05/2014 10.30.56 1 NotApplicable Clustering Healthy 03/06/2014 08.21.27 5 NotApplicable BitlockerDeployment Healthy 02/06/2014 22.00.36 1 NotApplicable ClientAccess.Proxy Healthy
02/06/2014 14.20.31 1 NotApplicable Compliance Healthy 02/05/2014 10.29.01 1 NotApplicable EWS Healthy 01/06/2014 12.57.38 1 NotApplicable FfoRws Healthy 01/06/2014 09.15.31 1 NotApplicable Places Healthy 03/06/2014 01.16.29 1 Online Transport Healthy 03/06/2014
08.23.33 10 NotApplicable RemoteMonitoring Healthy 02/06/2014 15.11.34 4 NotApplicable Search Healthy 03/06/2014 07.04.56 140 NotApplicable Inference Healthy 01/06/2014 23.57.09 1 NotApplicable OWA Healthy 03/06/2014 09.16.39 2 NotApplicable MailboxSpace Repairing
03/06/2014 09.22.02 17 NotApplicable MRS Healthy 03/06/2014 09.20.58 19 NotApplicable MessageTracing Healthy 03/06/2014 07.03.30 8 NotApplicable Network Healthy 03/06/2014 09.09.30 2 NotApplicable Calendaring Healthy 03/06/2014 09.19.16 8 NotApplicable PeopleConnect
Healthy 02/06/2014 14.10.08 1 NotApplicable IMAP Healthy 03/06/2014 08.10.29 1 NotApplicable POP Healthy 03/06/2014 05.54.04 1 NotApplicable ProcessIsolation Healthy 03/06/2014 07.39.59 22 NotApplicable Provisioning Healthy 03/06/2014 08.35.16 8 NotApplicable
Psws Healthy 03/06/2014 08.51.44 15 NotApplicable PublicFolders Healthy 03/06/2014 09.21.54 5 NotApplicable Outlook Healthy 03/06/2014 05.56.00 1 NotApplicable RPS Healthy 03/06/2014 08.22.48 1 NotApplicable RWS Healthy 03/06/2014 08.11.44 2 NotApplicable
Security Healthy 03/06/2014 08.11.33 8 NotApplicable SiteMailbox Healthy 03/06/2014 09.07.10 4 NotApplicable Store Healthy 03/06/2014 09.19.09 110 NotApplicable TransportSync Healthy 03/06/2014 08.11.56 8 NotApplicable UserThrottling Healthy 03/06/2014 09.21.49
8 NotApplicable FfoWebService Healthy 03/06/2014 07.07.43 1 NotApplicable DAL Healthy 03/06/2014 08.08.02 12 NotApplicable FfoWebstore Healthy 03/06/2014 07.07.33 1 NotApplicable AntiSpam Healthy 03/06/2014 06.02.52 8 NotApplicable OWA.Protocol.Dep Healthy
30/05/2014 17.45.35 1 NotApplicable MigrationMonitor Healthy 03/06/2014 08.33.07 3 NotApplicable MailboxTransport Unhealthy 03/06/2014 09.05.01 63 NotApplicable MSExchangeCertificateDeplo... Disabled 01/01/0001 01.00.00 2 NotApplicable OWA.Protocol Healthy
03/06/2014 07.33.09 9 NotApplicable Outlook.Protocol Healthy 02/06/2014 18.07.34 11 NotApplicable RPS.Protocol Healthy 02/05/2014 10.33.10 2 NotApplicable IMAP.Protocol Healthy 03/06/2014 07.31.55 7 NotApplicable Datamining Healthy 03/06/2014 05.06.42 7 NotApplicable
POP.Protocol Healthy 01/06/2014 19.02.12 7 Online FrontendTransport Healthy 02/06/2014 09.06.30 7 NotApplicable CentralAdmin Healthy 03/06/2014 07.37.18 7 Online ECP.Proxy Healthy 03/06/2014 06.30.43 7 Online RPS.Proxy Healthy 03/06/2014 09.22.16 28 NotApplicable
PushNotifications.Protocol Healthy 03/06/2014 08.34.46 7 Online RWS.Proxy Healthy 02/06/2014 22.55.09 7 Online Outlook.Proxy Healthy 03/06/2014 07.51.37 7 Online OutlookMapi.Proxy Healthy 03/06/2014 08.09.14 7 Note: Subsequent detected alerts are suppressed
until the health set is healthy again.</Message>
<Monitor>ScanTimeMeanMonitor</Monitor>
</EventXML>
</UserData>
</Event>
Raffaele Zamuner -
Good day ,
Running Get-ServerHealth on Exchange 2013 Version 15.0 (Build 775.38) mailbox server show the following "Unhealthy" healthsets
Name AlertValue
MaintenanceFailureMonitor.FEP Unhealthy
OutlookRpcDeepTestMonitor Unhealthy
MicrosoftFailedUpdatesMonitor Unhealthy
OutlookRpcSelfTestMonitor Unhealthy
I've tried tracing the source and searching the internet with no luck !
any idea ?
regards
Best Regards Bisher ShbibSeems to be everything back to its first status, actually there is only one new UnHealthy HealthSet which is "ECP"
this is the health report for all server
Server State HealthSet AlertValue LastTransitionTime MonitorCount
CAS01 NotApplicable ECP Unhealthy 6/17/2014 9:36:00 AM 1
CAS01 NotApplicable FEP Unhealthy 6/17/2014 9:31:31 AM 1
CAS01 NotApplicable Network Unhealthy 6/17/2014 4:11:47 AM 2
Server State HealthSet AlertValue LastTransitionTime MonitorCount
CAS03 NotApplicable FEP Unhealthy 6/17/2014 9:31:50 AM 1
CAS03 NotApplicable Network Unhealthy 6/16/2014 9:19:05 AM 2
Server State HealthSet AlertValue LastTransitionTime MonitorCount
CAS02 NotApplicable ECP Unhealthy 6/17/2014 9:31:48 AM 1
CAS02 NotApplicable FEP Unhealthy 6/17/2014 9:32:28 AM 1
CAS02 NotApplicable Network Unhealthy 6/17/2014 4:25:09 AM 2
Server State HealthSet AlertValue LastTransitionTime MonitorCount
MBX01 NotApplicable FIPS Unhealthy 6/17/2014 10:42:53 PM 28
MBX01 NotApplicable FEP Unhealthy 6/17/2014 9:34:14 AM 1
MBX01 NotApplicable MailboxSpace Repairing 6/17/2014 9:39:04 AM 35
MBX01 NotApplicable Outlook.Protocol Unhealthy 6/17/2014 9:30:46 AM 11Server State HealthSet AlertValue LastTransitionTime MonitorCount
MBX02 NotApplicable FEP Unhealthy 6/17/2014 9:31:31 AM 1
MBX02 NotApplicable MailboxSpace Repairing 6/17/2014 9:38:53 AM 35
MBX02 NotApplicable Outlook.Protocol Unhealthy 6/17/2014 9:29:31 AM 11
I think the most important one is Outlook.Protocol HealthSet , Other HealthSets can be ignored or overried
Any thoughts ?
Best Regards Bisher Shbib -
Exchange 2013 CU3 Databases only activate on one mailbox server
Hi, guys
I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will be activated on the mailbox
server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
This caused the database activated on another server.
And I got the message from SCOM, like this:
Alert: Health Set unhealthy
Source: test-mbx - Outlook.Protocol
Path: test-mbx.contoso.local;test-mbx.contoso.local
Last modified by: System
Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
Latency: 00:00:00.0320000
ActivityContext:
Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log: Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 11/12/2013
5:15:25 AM
- TaskFinished = 11/12/2013
5:15:25 AM
- ErrorDetails =
- RespondingRpcClientAccessServerVersion
= 15.0.712.4012
Latency = 00:00:00.0303884
- ActivityContext =
EMSMDB.Connect() completed successfully.
EMSMDB.DoRpc(Logon)
Task produced output:
- TaskStarted = 11/12/2013
5:15:25 AM
- TaskFinished = 11/12/2013
5:15:25 AM
- Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
- ErrorDetails =
- Latency = 00:00:00.0018801
- ActivityContext =
EMSMDB.DoRpc(Logon) failed.
Task produced output:
- TaskStarted = 11/12/2013 5:15:25 AM
- TaskFinished = 11/12/2013 5:15:25 AM
- Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
State Name
TargetResource HealthSet
AlertValue ServerComponent
NotApplicable OutlookMapiHttpDeepTestMonitor
Outlook.Protocol Unhealthy None
NotApplicable OutlookRpcDeepTestMonitor
Outlook.Protocol Healthy None
NotApplicable OutlookRpcSelfTestMonitor
Outlook.Protocol Healthy None
NotApplicable OutlookMapiHttpSelfTestMonitor Outlook.Protocol
Healthy None
NotApplicable PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
NotApplicable LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol Healthy
None
This test is a cause that mailbox databases in DAG is doing failover to another server
Log Name: Application
Source: MSExchangeRepl
Date: 12.11.2013 4:49:46
Event ID: 3169
Task Category: Service
Level: Information
Keywords: Classic
User: N/A
Computer: test-mbx-2
Description:
(Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="16388">3169</EventID>
<Level>4</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
<EventRecordID>1606248</EventRecordID>
<Channel>Application</Channel>
<Computer>test-mbx-2.contoso.local</Computer>
<Security />
</System>
<EventData>
<Data>DB-01</Data>
<Data>test-mbx.contoso.local</Data>
<Data>test-mbx-1.contoso.local</Data>
<Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
</EventData>
</Event>
I don't know why, anyone know what's the problem?
Thank you.
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.comHi,
After deleting all the health mailboxes and restart
the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
[PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
rtvalue -AutoSize
Server state Name AlertValue
MAILBOX1 OutlookRpcDeepTestMonitor Healthy
MAILBOX1 OutlookMapiHttpDeepTestMonitor Unhealthy
MAILBOX1 OutlookRpcSelfTestMonitor Healthy
MAILBOX1 OutlookMapiHttpSelfTestMonitor Healthy
MAILBOX1 PrivateWorkingSetWarning....cclientaccess.service Healthy
MAILBOX1 PrivateWorkingSetError....rpcclientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeWarning....ientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeError....clientaccess.service Healthy
MAILBOX1 ExchangeCrashEventError....pcclientaccess.service Healthy
MAILBOX1 LongRunningWatsonWarning....cclientaccess.service Healthy
MAILBOX1 LongRunningWerMgrWarning....cclientaccess.service Healthy
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com -
Performance Counter monitors stay unhealthy even when values drop below thresholds
I'm investigating some (SCOM 2012) alerts on our Exchange 2013 (SP1) environment:
Malware filtering is taking too long (90th percentile)
Mailbox Transport Submission is not keeping up with the work...
Queue Alert: Internal Aggregate Delivery Queue (Normal Priority) exceeds threshold
The total number of messages in shadow queues exceeds 1500
All the monitors are Performance Counter based monitors. When I investigate those performance counters (found via the Crimson Channels in the Eventlogs ../ActiveMonitoring/Monitordefinition) all affected counters have already dropped below threshold values
but the associated Health Sets stay unhealthy
IE: Get-ServerHealth -Identity '<Server>' -HealthSet '<HealthSet>' still reports Total.Shadow.Queue.Length.Above.Threshold.Monitor as UnHealthy while perfmon reports values way below 1500 for that particular server.
How to (re)evaluate the monitors ?For investigation purposes I've added some perfmoncounters in SCOM
Another server now alerts 'Total number of messages in shadow queues exceeds 1500'. On the specific server the treshold never reached 1500; it was about 5 at the time the alert fired ?!?
Now it seems the alerts fire for no reason and cannot be reset (I want Managed Availability to reset the alert, not scom)
The XML of Eventlog\Applications and Serviices/Microsoft/Exchange/ActiveMonitoring/MonitorDefinition/
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Exchange-ActiveMonitoring" Guid="{ECD64F52-A3BC-47B8-B681-A11B7A1C8770}" />
<EventID>7</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-07-08T12:08:40.460212000Z" />
<EventRecordID>15316181</EventRecordID>
<Correlation />
<Execution ProcessID="38980" ThreadID="30424" />
<Channel>Microsoft-Exchange-ActiveMonitoring/MonitorDefinition</Channel>
<Computer>XXXX</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<Id>577</Id>
<AssemblyPath>C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Office.Datacenter.ActiveMonitoringLocal.dll</AssemblyPath>
<TypeName>Microsoft.Office.Datacenter.ActiveMonitoring.OverallConsecutiveSampleValueAboveThresholdMonitor</TypeName>
<Name>Total.Shadow.Queue.Length.Above.Threshold.Monitor</Name>
<WorkItemVersion>[null]</WorkItemVersion>
<ServiceName>HubTransport</ServiceName>
<DeploymentId>0</DeploymentId>
<ExecutionLocation>[null]</ExecutionLocation>
<CreatedTime>2014-07-08T12:08:40.4602120Z</CreatedTime>
<Enabled>1</Enabled>
<TargetPartition>[null]</TargetPartition>
<TargetGroup>[null]</TargetGroup>
<TargetResource />
<TargetExtension>[null]</TargetExtension>
<TargetVersion>[null]</TargetVersion>
<RecurrenceIntervalSeconds>0</RecurrenceIntervalSeconds>
<TimeoutSeconds>30</TimeoutSeconds>
<StartTime>2014-07-08T12:08:40.4602120Z</StartTime>
<UpdateTime>2014-07-08T12:04:53.7722193Z</UpdateTime>
<MaxRetryAttempts>0</MaxRetryAttempts>
<ExtensionAttributes>[null]</ExtensionAttributes>
<SampleMask>EDS/Performance Counter/MSExchangeTransport Shadow Redundancy Host Info\Shadow Queue Length\_total</SampleMask>
<MonitoringIntervalSeconds>600</MonitoringIntervalSeconds>
<MinimumErrorCount>0</MinimumErrorCount>
<MonitoringThreshold>1500</MonitoringThreshold>
<SecondaryMonitoringThreshold>1</SecondaryMonitoringThreshold>
<ServicePriority>2</ServicePriority>
<ServiceSeverity>0</ServiceSeverity>
<IsHaImpacting>0</IsHaImpacting>
<CreatedById>50</CreatedById>
<InsufficientSamplesIntervalSeconds>28800</InsufficientSamplesIntervalSeconds>
<StateAttribute1Mask>[null]</StateAttribute1Mask>
<FailureCategoryMask>0</FailureCategoryMask>
<ComponentName>ServiceComponents/HubTransport/High</ComponentName>
<StateTransitionsXml>[null]</StateTransitionsXml>
<AllowCorrelationToMonitor>0</AllowCorrelationToMonitor>
<ScenarioDescription>[null]</ScenarioDescription>
<SourceScope>[null]</SourceScope>
<TargetScopes>[null]</TargetScopes>
<Version>65536</Version>
</EventXML>
</UserData>
</Event> -
Hi,
I am currently running a 2013 CU2 DAG with 2 database and 2 cas servers. SCOM is reporting the following but i can find very little info on it;
Alert: Health Set unhealthy
Source: <server name> - Outlook.Protocol
Last modified by: System
Last modified time: 4/2/2014 3:49:58 PM
Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/<database name> has failed against <server name> proxying to <server name> for HealthMailboxb63d235bb56b428ebf56ea594d3ca0c7@CEOSMTPServer.
Latency: 00:00:00.0520000
ActivityContext: I32:ADS.C[Apollo]=1;F:ADS.AL[Apollo]=3.3585;I32:ADR.C[Apollo]=1;F:ADR.AL[Apollo]=3.0093;I32:ADS.C[Razor]=2;F:ADS.AL[Razor]=2.0185
Outline: [50] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log: Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 2/04/2014 3:49:25 PM
- TaskFinished = 2/04/2014 3:49:25 PM
- ErrorDetails =
- RespondingRpcClientAccessServerVersion = 15.0.712.4012
- Latency = 00:00:00.0505291
- ActivityContext = I32:ADS.C[Apollo]=1;F:ADS.AL[Apollo]=3.3585;I32:ADR.C[Apollo]=1;F:ADR.AL[Apollo]=3.0093;I32:ADS.C[Razor]=2;F:ADS.AL[Razor]=2.0185
EMSMDB.Connect() completed successfully.
EMSMDB.DoRpc(Logon)
Task produced output:
- TaskStarted = 2/04/2014 3:49:25 PM
- TaskFinished = 2/04/2014 3:49:25 PM
- Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
- ErrorDetails =
- Latency = 00:00:00.0010381
- ActivityContext = I32:ADS.C[Apollo]=1;F:ADS.AL[Apollo]=3.3585;I32:ADR.C[Apollo]=1;F:ADR.AL[Apollo]=3.0093;I32:ADS.C[Razor]=2
Any help would be greatly appreciated.
ThanksHi,
Please run the following command and post the output:
Get-ServerHealth -Identity Servername -HealthSet Outlook.Protocol
In addition, I recommend you run "test-mapiconnectivity" and check event viewer on exchange server.
http://technet.microsoft.com/en-us/library/bb123681(v=exchg.150).aspx
Use the Test-MapiConnectivity cmdlet to verify server functionality by logging on to the mailbox that you specify. If you don't specify a mailbox, the cmdlet logs on to the SystemMailbox on the database that you specify.
Thanks.
Niko Cheng
TechNet Community Support -
How to trigger unread emails for a given period ?
Hello All,
I kindly need your help on the following. I have a mailbox that receives huge number of emails per day , I`m processing those all unread emails every one minute using a third party tool and make them read after successfull processing , my concern is
that I want to receive any alerts if there are unread emails after 5 minutes for example. Because this will mean that the emails are not processing hence the scenario has stopped running.
Hopefully I`m clear enough.
Best Regards,
Haytham FekryYou should use time-script monitor which run every 5 minutes and return unhealthy if an unread email was found in inbox.
The script as
Set olApp=CreateObject("Outlook.Application")
Set olMAPI=olApp.GetNameSpace("MAPI")
Set oFolder = olMAPI.GetDefaultFolder(6)
Set allEmails = oFolder.Items
dim oAPI, oBag
Dim Status
set oAPI=CreateObject("MOM.SCriptAPI")
set oBag=oAPI.CreatePropertyBag()
Status="Healthy"
For Each email In oFolder.Items
If email.Unread = True Then
Status="UnHealthy"
End If
Next
Call oBag.AddValue("State", Status)
Call oAPI.Return(oBag)
Roger -
Hi, all
I have Exchange Server 2013 and SCOM 2012 installed. I have imported Exchange Server 2013 Management Pack to SCOM 2012. Now I have a question that when there is a service not healthy, I can find the red alert in my alert view with the Exchange 2013 server,
but after the service is healthy automatically, the red alert is still there. I can only make it become green healthy status after reseting the healthset status in the healthset explorer.
Does anyone know how to make the server become green healthy status automatically after the monitor is healthy?
Thank you.
NileHi,
How many Exchange Servers do you have? Does this issue only occur on one Exchange Server?
Please check the application log on the problematic Exchange server and see whether there are any related event error.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support -
Hello everyone,
I was hoping some of you could help me out a bit with the new monitors in Exchange 2013.
Especially after updating to CU6 we are getting a lot of warnings from SCOM with different HealthSets that show as unhealthy. These are usually “OK” again when we log on to the server and run Get-ServerHealth or Get-HealthReport. The most common healthset is
Compliance, but also get warnings from MailboxTransport and ActiveSync.
If we do manage to log on before the healthset returns to healthy again, like in the example below, we can drill down a bit. We are however very unsure about what to do with this information. Perhaps we should change the threshold, but how do we find out exactly
what this monitor is reporting on? We know it has something to do with Mapi Submit, and that the threshold is 8, but not much more than that?
Get-ServerHealth SERVER | where {($_.healthsetname -eq "mailboxtransport") -and ($_.alertvalue -eq "unhealthy")} | ft name,alertvalue -auto
Name AlertValue
Mapi.Submit.Monitor Unhealthy
(Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/MonitorDefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like "Mapi.Submit.Monitor"}
auto-ns2 : http://schemas.microsoft.com/win/2004/08/events
xmlns : myNs
Id : 266
AssemblyPath : D:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Office.Datacenter.ActiveMonitoringLocal.dll
TypeName : Microsoft.Office.Datacenter.ActiveMonitoring.OverallXFailuresMonitor
Name : Mapi.Submit.Monitor
WorkItemVersion : [null]
ServiceName : MailboxTransport
DeploymentId : 0
ExecutionLocation : [null]
CreatedTime : 2014-11-20T08:51:03.5576888Z
Enabled : 1
TargetPartition : [null]
TargetGroup : [null]
TargetResource : MailboxTransport
TargetExtension : [null]
TargetVersion : [null]
RecurrenceIntervalSeconds : 0
TimeoutSeconds : 30
StartTime : 2014-11-20T08:51:03.5576888Z
UpdateTime : 2014-11-20T08:42:58.9416436Z
MaxRetryAttempts : 0
ExtensionAttributes : [null]
SampleMask : Mapi.Submit.Probe
MonitoringIntervalSeconds : 3600
MinimumErrorCount : 0
MonitoringThreshold : 8
SecondaryMonitoringThreshold : 0
MonitoringSamplesThreshold : 100
ServicePriority : 2
ServiceSeverity : 0
IsHaImpacting : 0
CreatedById : 57
InsufficientSamplesIntervalSeconds : 28800
StateAttribute1Mask : [null]
FailureCategoryMask : 0
ComponentName : ServiceComponents/MailboxTransport/High
StateTransitionsXml : <StateTransitions>
<Transition ToState="Unrecoverable" TimeoutInSeconds="0" />
</StateTransitions>
AllowCorrelationToMonitor : 0
ScenarioDescription : [null]
SourceScope : [null]
TargetScopes : [null]
HaScope : Server
Version : 65536
We have an Exchange 2007 server coexisting in the environment, but it is not in use and will be decommissioned.
ServerRole Edition AdminDisplayVersion
Mailbox, ClientAccess, HubTransport Standard Version 8.3 (Build 83.6)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)Thanks Belinda.
We had a look in the log you mentioned, and found some events that appear to be related.
Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed.
This could indicate that the mailbox submissions are taking too long or not progressing at all.
SequenceNumber: 635515592255510017
Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635515592255510017. First Run? = False. Previous mail submission to store
was successful. Results - # of previous results: 0. Could Not Find stages that ran. Previous SendMail failure - Mail submitted to Store during the previous run never reached SendAsCheck.
This may indicate a latency from Store to Submission Service. Investigating. Found lower SA latency. Indicates an issue in Submission service.
Investigate. In SendMail - NotificationID=00000044-0000-0000-0000-0000659c9601 Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail
failure.
CheckPreviousRunMail exception details:
Current SendMail exception details:
MailWasSentInLastRun (0(no)/1(yes)): 1
CheckMailSuccess(0(no)/1(yes)): 0
SendMailSuccess(0(no)/1(yes)/2(no-noMDBs)/3(no-noActiveMDBs)/4(no-ignorableException)): 1
PreviousMailLatencies: <[email protected]>,,2014-11-20T08:37:58.817Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.811|SA=0.343|MTSSDMO=0.426|MTSSDPL=0.002|MTSSDSS=0.008|MTSSDS=0.031|MTSS=0.466;;<[email protected]>,,2014-11-20T08:32:58.772Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.702|SA=0.203|MTSSDMO=0.451|MTSSDPL=0.003|MTSSDSS=0.007|MTSSDS=0.047|MTSS=0.500;;<[email protected]>,,2014-11-20T08:27:58.664Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=1.170|SA=0.530|MTSSDMO=0.548|MTSSDPL=0.002|MTSSDSS=0.035|MTSSDS=0.078|MTSS=0.647;;
GetPreviousMailLatencyFailures:
(The following are applicable if the mail was actually sent)
MailSentAt: 20.11.2014 08:42:58
TimeInSendingToStore: 62,3989
Sent Mail Result Details:
(InternetMessageId:<[email protected]>;
ItemEntryId:0 0 0 0 2E 57 BD C1 1C 4B 5C 47 9E 54 6E B8 B2 C5 75 38 7 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 0 0 1 B 0 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 18 1A CD F1 0 0 )
Properties of Sending mail
(Subject:00000044-0000-0000-0000-0000659c9601-MapiSubmitLAMProbe;
Sender:[email protected];
MbxGuid:340b204b-c716-4dfe-bbe1-cf09b5c73934;
MdbGuid:2a6b9801-1647-4378-bc11-6ff342d22fcf;
Recipient:[email protected];
Body and MessageClass:MessageClass:IPM.Note.MapiSubmitLAMProbe;MessageBody:This is a Probe Mapi message that's Submitted from Store to Mailbox transport Submission service to Hub transport service;
DoNotDeliver, DropMessageInHub and DeleteAfterSent:DoNotDeliver:True;DropMessageInHub:True;DeleteAfterSubmit:True;)
Probe Exception: 'System.ApplicationException: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.PerformProbeFinalAction(Boolean potentialForAlertBasedOnPreviousRun, Boolean potentialForAlertBasedOnCurrentRun, Exception previousRunVerificationException,
Exception currentRunException, DateTime timeMessageSentToStore)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWorkInternal(CancellationToken cancellationToken)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Probe Result Name: 'Mapi.Submit.Probe'
Probe Result Type: 'Failed'
Monitor Total Value: '0'
Monitor Total Sample Count: '12'
Monitor Total Failed Count: '12'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '16.11.2014 21:40:10' -
Use SNMP to monitor the power supply status of stacked switches
Does anybody know how to use SNMP to monitor the status of the internal power supplies of a group of stacked Cisco 3750 switches?
The switch stack has three 3750-48PS-E switches inter-connected by Cisco StackWise cable. IOS ver 12.1(19)EAlc. A single IP address is used to identify the switch stack. Every time I poll the OID chassisPs1Status (1.3.6.1.4.1.9.5.1.2.4.0 in CISCO-STACK-MIB), I only got the status for the Master switch of the switch stack. Is there any way to poll the power supply status of other switches in the switch stack?
Thanks a lot!Sorry to refresh such an old topic - but I am stuck with exactly this: Monitoring power supplies of a stacked Cisco Catalyst 3750-E.
I'm using the exact same OID's as described, but the problem is, the information shown on the SNMP output is not correct.
This morning, a power supply of the first switch failed and switched to RPS. Here the information I got on SNMP:
snmpwalk -v 2c -c public 192.168.1.50 1.3.6.1.4.1.9.9.13.1
SNMPv2-SMI::enterprises.9.9.13.1.1.0 = INTEGER: 13
SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.1006 = STRING: "SW#1, Sensor#1, GREEN "
SNMPv2-SMI::enterprises.9.9.13.1.3.1.2.2006 = STRING: "SW#2, Sensor#1, GREEN "
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.1006 = Gauge32: 41
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.2006 = Gauge32: 40
SNMPv2-SMI::enterprises.9.9.13.1.3.1.4.1006 = INTEGER: 59
SNMPv2-SMI::enterprises.9.9.13.1.3.1.4.2006 = INTEGER: 59
SNMPv2-SMI::enterprises.9.9.13.1.3.1.5.1006 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.13.1.3.1.5.2006 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.13.1.3.1.6.1006 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.3.1.6.2006 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.4.1.2.1060 = STRING: "Switch#1, Fan#1"
SNMPv2-SMI::enterprises.9.9.13.1.4.1.2.2059 = STRING: "Switch#2, Fan#1"
SNMPv2-SMI::enterprises.9.9.13.1.4.1.3.1060 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.4.1.3.2059 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1059 = STRING: "Sw1, PS1 Normal, RPS NotExist"
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2060 = STRING: "Sw2, PS1 Normal, RPS NotExist"
SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.1059 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.2060 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.1059 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.13.1.5.1.4.2060 = INTEGER: 2
As you see, both PS1 (for both switches) are appearing normal. It doesn't even recognize RPS:
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1059 = STRING: "Sw1, PS1 Normal, RPS NotExist"
SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2060 = STRING: "Sw2, PS1 Normal, RPS NotExist"
The first switch's power supply died and now the cable is disconnected. LED's of the power supply are out. And still: The switch happily announces by SNMP it's power supplies are up.
Is this a known bug? If yes, has it been fixed?
Model WS-C3750E-48TD
Firmware 12.2(37)SE1
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;} -
Exchange 2013 Get-ServerHealth NotApplicable
Hi All,
I have a new installation of Exchange 2013. SCOM monitoring in place.
I'v noticed that a lot of errors showing on SCOM regarding the HealtSet is showing unhealthy.
But what is strange to me is that when I run Get-ServerHealth I see that the HealtSets that are showing as unhealthy are also in state
NotApplicable.
What does NotApplicable mean, and why is it event in unhealthy state if its not applicable?
Thanks,
ZarkoHi,
There is no official document explaining the state "NotApplicable" currently.
To troubleshoot health set issue, here is a related blog for your reference.
http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx
Besides, please check if there is any related events logged for further analysis.
Best regards,
Belinda Ma
TechNet Community Support
Maybe you are looking for
-
Is there a way to create a "read only" inbox in mac mail?
I am wondering if there is a way to set up a read only inbox...I would like to receive email from a specific address but block or not have the option to send from that address.
-
Restore Mackintosh formatted ipod using windows vista
Upon attempting to restore ipod using latest Itunes, I am informed that "Itunes could not contactthe Ipod software update server because you are not connected to the internet" - there is no difficulty with my internet connection. Has anyone else had
-
I have an installer that needs to drop a file within an already installed bundle. Using the GUI PackageMaker I drop the file at the level of the bundle. I then use a script to move my file within the bundle and assign the proper rights. If I run the
-
Firefox on iMac 27" screen - menu on one side, window on other
Love the 27 inch screen! When I open Firefox, however, the window opens in the middle of the screen, and the menu is on the far left. I want the menu to be over the application. It feels weird having to scroll left in order to get to Bookmarks. I
-
What version of Adobe Media Server would fit our needs?
Hello. We are considering doing HTTP video streaming on our intranet. We have approximately 500 employees and would want to be able to stream approximately 10 - 50 one-way connections at one time. What version of Adobe Media Server would you recommen