OnPremisesSmtpClientSubmissionMonitor unhealthy

Hi
I ran "get-healthreport" and got an unhealthy "Frontend Transport". I found out the problem is the monitor "OnPremisesSmtpClientSubmissionMonitor". I found this event:
The client submission probe failed 3 times over 15 minutes.
Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
Probe Exception: 'System.Exception: Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.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()'
Failure Context: 'Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
Execution Context: ''
Probe Result Name: 'OnPremisesSmtpClientSubmission'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '3/13/2015 11:56:16 AM'
But I can telnet the port 487 on 127.0.0.1 and the last run seems to be fine. I have restarted the Frontend transport service with no luck. The state is still "Unhealthy".
RunspaceId : b49aab67-784f-464f-9c60-4b07fcde8f6e
Server : srvexchange01
CurrentHealthSetState : Online
Name : OnPremisesSmtpClientSubmissionMonitor
TargetResource :
HealthSetName : FrontendTransport
HealthGroupName : ServiceComponents
AlertValue : Unhealthy
FirstAlertObservedTime : 13.03.2015 12:56:16
Description :
IsHaImpacting : False
RecurranceInterval : 450
DefinitionCreatedTime : 17.03.2015 14:47:56
HealthSetDescription :
ServerComponentName : FrontendTransport
LastTransitionTime : 13.03.2015 12:56:16
LastExecutionTime : 17.03.2015 15:49:53
LastExecutionResult : Succeeded
ResultId : 1671349
WorkItemId : 70
IsStale : False
Error :
Exception :
IsNotified : False
LastFailedProbeId : 37
LastFailedProbeResultId : 835260
ServicePriority : 2
Identity : FrontendTransport\OnPremisesSmtpClientSubmissionMonitor\
IsValid : True
ObjectState : New

Hello,
Please try:
Add-GlobalMonitoringOverride -Identity "FrontendTransport\OnPremisesInboundProxy" -PropertyName Enabled -PropertyValue 0 -ApplyVersion "15.0.xxx.xx" -ItemType
Monitor
The
ApplyVersion here is your current Exchange version.
Thanks,
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

Similar Messages

FrontendTransport health set unhealthy (OnPremisesSmtpClientSubmissionMonitor)

FrontendTransport health set unhealthy (OnPremisesSmtpClientSubmissionMonitor) - The client submission probe failed 3 times over 15 minutes.
Seems like these alerts have started comming for some of the servers, where mailbox and CAS role is installed together. when i cehcked the queue, all seems to be fine. Performed the below mentioned steps, but the issue didn't fixed:
1. invoke-monitoringprobe" command doesn't work.
2. Have restarted "health manager service" didn't work.
Still the alert value is in uhealthy state, have anyone come across the same issue, if so, can you share what are the steps that we have take?
Your answers are much appreciated!

Hi,
Please check the Monitor Result and Probe Result in the following path and see if there is any related message.
Event Viewer\Applications and Services Logs\Microsoft\Exchange\ActiveMonitoring\ProbeResult( or MonitorResult).
Based on your description, everthing works well except this alert. However, there is a way to hide the alert by overriding the monitor using the command below:
Add-GlobalMonitoringOverride -Identity "FrontendTransport\OnPremisesSmtpClientSubmissionMonitor" -PropertyName Enabled -PropertyValue 0 -ItemType Monitor -ApplyVersion "version"
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Office Web Apps - "Could not find trace string in ULS logs" unhealthy?

I have reviewed everything I could find on unhealthy WAC clusters as my problem seems unrelated to certificate or missing components. I've already digested
http://www.wictorwilen.se/office-web-apps-server-2013---machines-are-always-reported-as-unhealthy (Thanks Wictor).
The particular configuration is an Office Web Apps 2013 ([X-OfficeVersion, 15.0.4551.1005]), running on top of Windows Server 2012, configured for http access (SSL offloaded NLB cluster) and finally linked to Exchange 2013, Lync 2013 and SharePoint
2013. Everything works as expected from client side after setting IIS ARR to handle all reverse proxy bits.
FarmOU :
InternalURL : https://officeapps.fqdn/
ExternalURL : https://officeapps.fqdn/
AllowHTTP : True
SSLOffloaded : True
CertificateName :
EditingEnabled : True
LogLocation : C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS
LogRetentionInDays : 7
LogVerbosity : Unexpected
Proxy :
CacheLocation : C:\ProgramData\Microsoft\OfficeWebApps\Working\d
MaxMemoryCacheSizeInMB : 75
DocumentInfoCacheSize : 5000
CacheSizeInGB : 15
ClipartEnabled : False
TranslationEnabled : False
MaxTranslationCharacterCount : 125000
TranslationServiceAppId :
TranslationServiceAddress :
RenderingLocalCacheLocation : C:\ProgramData\Microsoft\OfficeWebApps\Working\waccache
RecycleActiveProcessCount : 5
AllowCEIP : False
ExcelRequestDurationMax : 300
ExcelSessionTimeout : 450
ExcelWorkbookSizeMax : 50
ExcelPrivateBytesMax : -1
ExcelConnectionLifetime : 1800
ExcelExternalDataCacheLifetime : 300
ExcelAllowExternalData : True
ExcelWarnOnDataRefresh : True
OpenFromUrlEnabled : False
OpenFromUncEnabled : True
OpenFromUrlThrottlingEnabled : True
PicturePasteDisabled : True
RemovePersonalInformationFromLogs : False
AllowHttpSecureStoreConnections : False
Machines : {WAC15PD-02, WAC15PD-01}
The problem however is an incessant logging on the WAC cluster nodes of event 1204,2204 followed almost immediately by 1004,2004. This repeats every 4min or so...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">1204</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:37.000000000Z" />
<EventRecordID>3043246</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage>
<ComponentOwner>ServicesInfrastructure</ComponentOwner>
</HealthReport></Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">2204</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:37.000000000Z" />
<EventRecordID>3043247</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported status: Could not find trace string in ULS logs in
C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage> <ComponentOwner>ServicesInfrastructure</ComponentOwner>
</HealthReport></Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">1004</EventID>
<Level>2</Level>
<Task>10002</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:39.000000000Z" />
<EventRecordID>3043266</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
</EventData>
</Event>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Office Web Apps Monitoring" />
<EventID
Qualifiers="0">2004</EventID>
<Level>2</Level>
<Task>10002</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2014-02-04T20:49:39.000000000Z" />
<EventRecordID>3043267</EventRecordID>
<Channel>Microsoft Office Web Apps</Channel>
<Computer>wac15pd-01.fqdn</Computer>
<Security
/>
</System>
- <EventData>
<Data><?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>AgentManagerWatchdog reported status for
AgentManagerWatchdog in category 'Recent Watchdog Reports'. Reported status: Machine health is Unhealthy</HealthMessage> </HealthReport></Data>
</EventData>
</Event>
Further exploration of ULS log files (C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS) did not yield particularly much, except the following;
02/04/2014 20:48:04.48 UlsControllerWatchdog.exe (0x1244) 0x0F60 Services Infrastructure Uls Controller Watchdog ajbam Assert
We're about to trace a string for category MsoSpUlsControllerWatchdog at level Info and we expect to find in the log later, but it appears that the category has been throttled. We will never be able to find the string and this watchdog will always fail.
StackTrace: at Microsoft.Office.Web.UlsControllerWatchdog.Program.CheckServiceInstance(ServiceInstance serviceInstance) at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.GetHealthResults(WatchdogExecutionContext
context, ServiceInstance si) at Microsoft.Office.Web.Common.WatchdogHelperThreadManager.WatchingThreadMethod(Object o) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback
callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Ru... 345fbec5-e958-4f1f-bf56-d65c1c0d472a
02/04/2014 20:48:04.48* UlsControllerWatchdog.exe (0x1244) 0x0F60 Services Infrastructure Uls Controller Watchdog ajbam Assert
...n(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch() 345fbec5-e958-4f1f-bf56-d65c1c0d472a
02/04/2014 20:48:05.52 UlsControllerWatchdog.exe (0x1244) 0x0F60 Services Infrastructure Services Infrastructure Health adhog Unexpected Health report
by UlsControllerWatchdog: Agent: UlsController, eventId: 1204, eventType: Error, categoryId: 1, eventMessage: <?xml version="1.0" encoding="utf-16"?> <HealthReport xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <HealthMessage>UlsControllerWatchdog reported status for UlsController in category 'Verify Trace Logging'. Reported
status: Could not find trace string in ULS logs in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS.</HealthMessage> <ComponentOwner>ServicesInfrastructure</ComponentOwner> </HealthReport> 345fbec5-e958-4f1f-bf56-d65c1c0d472a
02/04/2014 20:48:05.52 UlsControllerWatchdog.exe (0x1244) 0x0F60 Services Infrastructure Services Infrastructure Health adhoh Unexpected Health report
by UlsControllerWatchdog (persistent): Agent: UlsController, eventId: 2204, eventType: Error, categoryId: 1 345fbec5-e958-4f1f-bf56-d65c1c0d472a
I suspect these might be related, but can't seem to find any logical explanation why this should cause the Get-OfficeWebAppsMachine to report HealthStatus of Unhealthy. If related, is there a way to disable this check or remove throttling in a safe
way? Alternatively if this is some coding issue (I've not found any other blog/QA dealing with this particularly) it would be nice to get confirmation of this and potentially a fix/solution.
Any help would be greatly appreciated. Thank you!

Hi ChristiaanB,
You get this ULS error because you change the log verbosity of the OWA farm. I wrote an article for this on my blog : OWA unhealthy uls issue
Regards,
Wes

IPod stops syncing about 20/50gbs in, and makes unhealthy sounds.

Well, here's the story. I'm sorry in advance that it's such a huge post.
I haven't used my iPod classic for about 8 or so months now, and it's just been chillin in my drawer, turned off. Yesterday, I decided to plug it in to update it with all of the new music it's missed over the past 8 months. Once I plugged it in it froze for a bit, and iTunes said something was wrong with it, so it needed to be restored. Now, you should know, I've had this iPod since December 31, 2007. I have kept it in pristine condition, no scratches, marks, it basically looks brand new, and I've never dropped it.
So on to my actual issue: Once I started syncing the music, it basically got to approximately the 2500th track, and stopped syncing. When I would plug it in to sync the rest, iTunes would freeze, and I couldn't do anything until I just unplugged the iPod. Once I unplug the iPod, iTunes tells me that I don't have enough priviledges to access the disk, or something along those lines. Well, the issue was worse before, because before during this started my iPod just wouldn't respond and my system would hang and iTunes wouldn't force quit even though it said it did.
Now I restored it under Windows, and put it in manual mode, went to my Mac and same thing happens except this time..... all of my music that got on the iPod is now displayed as OTHER and it doesn't show up on the iPod. I think, maybe thats just a OS issue, since its restored under windows now. I restore it under OS X again. But this time it's more manageable because it doesn't try syncing automatically. Every time I have tried to sync it for the second time, it stops at the 13th-16th song and then I hear an unhealthy mechanism sound coming from the iPod. I've checked if it was a faulty wire, since I have 2, and both have the same problem. Also, when I plug it out after it pulls some of these shenanigans, it shows the OK to disconnect screen, and once the bar reaches the end the iPod resets itself, and makes some more strange sounds in the process.
Well, that's my story. I'm freaking out because I leave for Germany tomorrow, and now I won't even get to listen to my iPod on the plane.
Is there anything I can do? Are there any diagnostic tools I can use to tell if my iPod is dying or not? Any help would be sincerely appreciated. Obviously, my iPod isn't under warranty with Apple anymore, but I have a repair plan with RadioShack. It takes like 3 weeks though, so that's really out of the question in terms of action I can take right now.

Try to put your ipod into disk mode and run disk utiliy to see if there are any corrupt files on the HD.
http://support.apple.com/kb/HT1363
Reformating it and restoring it again would be another option.
Restoring: http://support.apple.com/kb/HT1339
Looking at the date, you might be on your plane already, good luck anyway

How to back up an unhealthy hard drive

My MacBook pro will start up but it will not boot up, I've tried many different things and they have all failed. I took my MacBook to a computer store and they told me that my hard drive is unhealthy and needs to be repaired. Is there any way of getting my data off of my hard drive ?

Get a properly formatted external drive and connect it to the computer. Then do this:
Clone Mavericks, Lion/Mountain Lion using Restore Option of Disk Utility
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
     1. Select Disk Utility from the main menu then press the Continue
         button.
     2. Select the destination volume from the left side list.
     3. Click on the Restore tab in the DU main window.
     4. Select the destination volume from the left side list and drag it
         to the Destination entry field.
     5. Select the source volume from the left side list and drag it to
         the Source entry field.
     6. Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.
No guarantee this will work, but if the drive is accessible you may get luck and have a backup.

MSI GTX 970 4G making unhealthy noises

I've recently upgraded my computer a bit, and recently my graphics card has been making some rather unhealthy-sounding high-pitched whining noises whenever I play games. It's definitely not the fans, because I checked with my case part-open to listen, ...

Quote from: TZBC on 06-January-15, 10:05:14I think this guide is for older AMD motherboards.
For newer one, don't forget to set “Board SATA RAID ROM” from Legacy ROM to “UEFI DRIVER” after STEP 2.
[img]http://i.imgur.co...

Help with Autodiscover.Proxy Unhealthy state.

Hello, I am trying to diagnose unhealthy systems in Exchange 2013. Here is my command and output. Lets start with the first one, Autodiscover.Proxy.
[PS] C:\Windows\system32>Get-HealthReport -Server email| where {$_.alertvalue -ne "Healthy" }
Server State HealthSet AlertValue LastTransitionTime MonitorCount
email Offline Autodiscover.Proxy Unhealthy 11/19/2014 10:52... 1
email Online HubTransport Unhealthy 11/24/2014 6:38:... 96
email Online FrontendTransport Unhealthy 9/25/2014 9:28:3... 12
email NotApplicable MSExchangeCertif... Disabled 1/1/0001 12:00:0... 2
I go to follow this article here: http://technet.microsoft.com/en-us/library/ms.exch.scom.autodiscover.proxy%28v=exchg.150%29.aspx
But the issue is that Invoke-MonitoringProbe does not return anything of value to me. Can you help me analyze this output?
[PS] C:\Windows\system32>Invoke-MonitoringProbe Autodiscover.Proxy\AutoDiscoverProxyTestProbe -Server email | Format-Lis
t
RunspaceId : bfa8f7cf-cc0b-4395-b3c8-75ab16fc227c
Server : email
MonitorIdentity : Autodiscover.Proxy\AutoDiscoverProxyTestProbe
RequestId : d677ac2a-43fa-4147-b806-b2f433c5a6e3
ExecutionStartTime : 11/25/2014 3:23:33 PM
ExecutionEndTime : 11/25/2014 3:23:33 PM
Error : Unknown app pool name:
Exception : System.InvalidOperationException: Unknown app pool name:
at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeLocalProbe.DoWork(Cancellati
onToken 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()
PoisonedCount : 0
ExecutionId : 60170839
SampleValue : 0
ExecutionContext : Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms
FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : d677ac2a43fa4147b806b2f433c5a6e3-AutoDiscoverProxyTestProbe
IsNotified : False
ResultId : 27004887
ServiceName : InvokeNow
StateAttribute1 :
StateAttribute2 :
StateAttribute3 :
StateAttribute4 :
StateAttribute5 :
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 :
StateAttribute12 :
StateAttribute13 :
StateAttribute14 :
StateAttribute15 :
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 :
StateAttribute22 :
StateAttribute23 :
StateAttribute24 :
StateAttribute25 :
Identity : 956989c13cc44e6faf102491a8d7a11b
IsValid : True
ObjectState : New
I'm not seeing any issue right now with Autodiscover but I don't want a larger issue to show up in the near future.

Ok, I guess we can do that. A new health set came up today Unhealthy. Its Compliance and in a NotApplicable state. I will try to determine the impact of this and start a different thread on that if I can't figure that one out.
Otherwise I don't see any problem with mail.
More info, not sure if I posted this, but if this helps, the Event Viewer states this:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring Source: Microsoft-Exchange-ManagedAvailability Date: 12/23/2014 7:03:08 AM Event ID: 4 Task Category: Monitoring Level: Error Keywords: User: SYSTEM Computer: email.domain.com Description: The Autodiscover.Proxy
health set has detected a problem on EMAIL beginning at 12/22/2014 3:01:12 PM (UTC). The health manager is reporting that recycling the MSExchangeAutodiscoverAppPool app pool has failed to restore health and it has requested the protocol be marked offline.
Attempts to auto-recover from this condition have failed and administrator attention is required.
Details below: MachineName: EMAIL
ServiceName: Autodiscover.Proxy
ResultName: AutodiscoverProxyTestProbe/MSExchangeAutodiscoverAppPool
Error: The remote server returned an error: (500) Internal Server Error.
Exception: System.ApplicationException: The remote server returned an error: (500) Internal Server Error. at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeLocalProbe.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() </startexecuting>
<startexecuting>ExecutionContext: Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms FailedResponse after 0 milliseconds. The remote server returned an error: (500) Internal Server Error.
[000.000] Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms [000.000] Starting HTTP request task [000.000] Waiting 59000 ms [000.000] Issuing GET against https://autodiscover.domain.com/AutoDiscover/ [000.000] Awaiting
GET response [000.000] Performing SSL validation [000.000] Failed with exception: The remote server returned an error: (500) Internal Server Error. </startexecuting>
<startexecuting>FailureContext:</startexecuting>
<startexecuting></startexecuting>ResultType: Failed
IsNotified: False
DeploymentId: 0
RetryCount: 0
ExtensionXml:
StateAttribute1: No response headers available.
StateAttribute2: [email protected] cfj>M!T@O-;XNkj+=u8[SL#f8Oby*S:(&Bg@GTal_=R@3YXtGi=%Vj832L_AE|l>Jhy18K/an^cNHv7i*3-8d*9?#FQa8u!IUoAai-mr(&PG|ZALs2&?6hI2N]9NKK][
StateAttribute3:
StateAttribute4:
StateAttribute5:
StateAttribute6: 0
StateAttribute7: 0
StateAttribute8: 0
StateAttribute9: 0
StateAttribute10: 0
StateAttribute11:
StateAttribute12:
StateAttribute13:
StateAttribute14:
StateAttribute14:
StateAttribute16: 0
StateAttribute17: 0
StateAttribute18: 0
StateAttribute19: 0
StateAttribute20: 0
StateAttribute21:
StateAttribute22:
StateAttribute23:
StateAttribute24:
StateAttribute25:
PoisonedCount: 0
Client Access Array: Client Access Array name could not be retrieved.
ExecutionId: 30334093
ExecutionStartTime: 12/23/2014 12:03:08 PM
ExecutionEndTime: 12/23/2014 12:03:08 PM
ResultId: 32263287
SampleValue: 0 Event Xml:
<event style="font-size:0.75em;line-height:1.5;" xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><system><provider guid="{C424A887-A89F-455F-8319-960917152221}" name="Microsoft-Exchange-ManagedAvailability"><eventid>4</eventid>
<version>0</version> <level>2</level> <task>2</task> <opcode>0</opcode> <keywords>0x8000000000000000</keywords> <timecreated systemtime="2014-12-23T12:03:08.889029200Z"><eventrecordid>7753</eventrecordid>
<correlation activityid="{ED377619-21A3-44A7-9444-751CDE95B0A1}"><execution processid="4204" threadid="14216"><channel>Microsoft-Exchange-ManagedAvailability/Monitoring</channel> <computer>email.domain.com</computer>
<security userid="S-1-5-18"></security></execution></correlation></timecreated></provider></system> <userdata><eventxml xmlns="myNs" xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events"><healthset>Autodiscover.Proxy</healthset>
<subject>Exchange Server Alert: The Autodiscover.Proxy health set is unhealthy.</subject> <message>The Autodiscover.Proxy health set has detected a problem on EMAIL beginning at 12/22/2014 3:01:12 PM (UTC). The health manager is reporting
that recycling the MSExchangeAutodiscoverAppPool app pool has failed to restore health and it has requested the protocol be marked offline. Attempts to auto-recover from this condition have failed and administrator attention is required. Details below: MachineName:
EMAIL ServiceName: Autodiscover.Proxy ResultName: AutodiscoverProxyTestProbe/MSExchangeAutodiscoverAppPool Error: The remote server returned an error: (500) Internal Server Error. Exception:
System.ApplicationException: The remote server returned an error: (500) Internal Server Error. at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeLocalProbe.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() ExecutionContext: Probe Absolute Timeout=60000ms, Timeout Value=60000ms,
Calculated HttpRequest Timeout=59000ms FailedResponse after 0 milliseconds. The remote server returned an error: (500) Internal Server Error. [000.000] Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms [000.000]
Starting HTTP request task [000.000] Waiting 59000 ms [000.000] Issuing GET against https://autodiscover.domain.com/AutoDiscover/ [000.000] Awaiting GET response [000.000] Performing SSL validation [000.000] Failed with exception: The remote server returned
an error: (500) Internal Server Error. FailureContext: ResultType: Failed IsNotified: False DeploymentId: 0 RetryCount: 0 ExtensionXml: StateAttribute1:
No response headers available. StateAttribute2: [email protected] cfj>M!T@O-;XNkj+=u8[SL#f8Oby*S:(&Bg@GTal_=R@3YXtGi=%Vj832L_AE|l>Jhy18K/an^cNHv7i*3-8d*9?#FQa8u!IUoAai-mr(&PG|ZALs2&?6hI2N]9NKK][
StateAttribute3: StateAttribute4: StateAttribute5: StateAttribute6: 0 StateAttribute7: 0 StateAttribute8: 0 StateAttribute9:
0 StateAttribute10: 0 StateAttribute11: StateAttribute12: StateAttribute13: StateAttribute14: StateAttribute14: StateAttribute16:
0 StateAttribute17: 0 StateAttribute18: 0 StateAttribute19: 0 StateAttribute20: 0 StateAttribute21: StateAttribute22: StateAttribute23:
StateAttribute24: StateAttribute25: PoisonedCount: 0 Client Access Array: Client Access Array name could not be retrieved. ExecutionId: 30334093 ExecutionStartTime:
12/23/2014 12:03:08 PM ExecutionEndTime: 12/23/2014 12:03:08 PM ResultId: 32263287 SampleValue: 0</message> <monitor>AutodiscoverProxyTestMonitor/MSExchangeAutodiscoverAppPool</monitor></eventxml></userdata></event>

Alert: Health Set unhealthy - Clustering

We have SCOM 2012 R2 setup to monitor our Exchange 2013 CU5 enviroment and we have gotten this error message about our Clustering going in to an unhealthy state a couple of times. We have checked the FSW and everything seems OK on its end. I
cannot find much out there on this message, so any help would be greatly appreciated:
Alert: Health Set unhealthy
Source: EXCHANGE04 - Clustering
Path: EXCHANGE04.company.com;EXCHANGE04.company.com
Last modified by: System
Last modified time: 8/24/2014 1:36:35 PM Alert description: The Cluster Group has not been healthy for 7200 minutes. The most recent probe failure message is: Check 'Microsoft.Exchange.Monitoring.QuorumGroupCheck' thrown an Exception!
Exception - Microsoft.Exchange.Monitoring.ReplicationCheckFailedException: QuorumGroup has failed. Specific error is: Quorum resource 'Cluster Group' is not online on server 'exchange06'. Database availability group 'exchDAG' might not be reachable or may have
lost redundancy. Error:
  File Share Witness (\\FSW01.company.com\exchDAG.company.com): Offline is offline. Please verify that the Cluster service is running on the server.
   at Microsoft.Exchange.Monitoring.ReplicationCheck.Fail(LocalizedString error)
   at Microsoft.Exchange.Monitoring.QuorumGroupCheck.RunCheck()
   at Microsoft.Exchange.Monitoring.DagMemberCheck.InternalRun()
   at Microsoft.Exchange.Monitoring.ReplicationCheck.Run()
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.HighAvailability.Probes.ReplicationHealthChecksProbeBase.RunReplicationCheck(Type checkType) Check 'Microsoft.Exchange.Monitoring.QuorumGroupCheck' did not Pass!
Detail Message - Quorum resource 'Cluster Group' is not online on server 'exchange06'. Database availability group 'exchDAG' might not be reachable or may have lost redundancy. Error:
  File Share Witness (\\FSW01.company.com\exchDAG.company.com): Offline is offline. Please verify that the Cluster service is running on the server.
To add some additional information, when I look in Failover cluster manager this is what I see. I know when we setup the servers the correct FSW information was being displayed.

Hi,
According to the error message, "Offline is offline. Please verify that the Cluster service is running on the server.",
I suggest double check whether the Cluster service is running as well. If not, please restart the service manually to verify whether this issue exists.
Please also refer the blog below to double check whether the FSW online:
Verifying the file share witness server / directory in use for Exchange 2010
http://blogs.technet.com/b/timmcmic/archive/2012/03/12/verifying-the-file-share-witness-server-directory-in-use-for-exchange-2010.aspx
If there is nothing abnormal on the Exchange server, it seems an issue on the SCOM side. Please contact SCOM Forum for help so that you can get more professional suggestions. For your convenience:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=systemcenteroperationsmanager
Thanks
Mavis
Mavis Huang
TechNet Community Support

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>

Best Practice Analyzer Results: Health Report Error EDS AlertValue Unhealthy.

I ran the Microsoft Office 365 Best Practices Analyzer Beta 1.0 and I get the following error:
C:\windows\system32>Get-healthreport -rollupgroup
servername.. then I got lots of results.. I narrow it to the following!
PSComputerName          : kaneex13.kanecpas.local
RunspaceId              : 85204a86-04f3-4779-9cad-3092ebfe3435
PSShowComputerName      : False
Server                  : kaneex13.kanecpas.local
CurrentHealthSetState   : NotApplicable
Name                    : MaintenanceFailureMonitor.EDS
TargetResource          :
HealthSetName           : EDS
HealthGroupName         : ServiceComponents
AlertValue              : Unhealthy
FirstAlertObservedTime : 2/6/2015 9:12:57 AM
Description             :
IsHaImpacting           : False
RecurranceInterval      : 300
DefinitionCreatedTime   : 2/6/2015 8:58:03 AM
HealthSetDescription    :
ServerComponentName     : None
LastTransitionTime      : 2/6/2015 9:12:57 AM
LastExecutionTime       : 2/6/2015 12:38:00 PM
LastExecutionResult     : Succeeded
ResultId                : 57636932
WorkItemId              : 94
IsStale                 : False
Error                   :
Exception               :
IsNotified              : False
LastFailedProbeId       : -301690410
LastFailedProbeResultId : 351526122
ServicePriority         : 0
Identity                : EDS\MaintenanceFailureMonitor.EDS\
IsValid                 : True
ObjectState             : New
I try to fix it and this is my findings!!
https://technet.microsoft.com/en-us/library/ms.exch.scom.eds(v=exchg.150).aspx
I'm running Exchange 2013 on Server 2012

Hi,
Based on my research, it’s a known issue that there will be 1006 error in the application log after we install a new Exchange 2013 server:
http://social.technet.microsoft.com/Forums/en-US/5ab1a91a-ccd4-49fb-a451-159592fc85d4/msexchangediagnostics-error-1006-logical-to-physical-size-ratio-free-megabytes?forum=exchangesvradmin
And it can be resolved by setting the value of DriveSpaceTrigger to false:
http://windowsitpro.com/blog/case-erroneous-disk-space-checker
In your case, we can firstly try to restart the MS Exchange Diagnostics Service.
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

SearchCatalogAvailabilityMonitor showing unhealthy for all database on DAG member mailbox server

Hi All
Help me to resolve server (all database) search catalogue availability monitor.
I am facing a search catalogue "Unknown" issue for newly created copy database and also on same mailbox server
"SearchCatalogAvailabilityMonitor" showing unhealthy for all database.
For the newly created copy database I tried to reseed / update search index catalogue by using below PowerShell command but it stopped with below mentioned error.
[PS] C:\Windows\system32>Update-MailboxDatabaseCopy -Identity DBTest\MBX1 -CatalogOnly
Confirm
Are you sure you want to perform this action?
Seeding database copy "DBTest\MBX1".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y
Confirm
The mailbox database copy 'DBTest\MBX1' has failed to update from server . Do you want to clean up that update
request now? Seeding cannot be requested for the same database copy until the failed request has been cleaned up by the
server, which should automatically happen within 15 minutes.
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y
WARNING: Seeding of content index catalog for database 'DBTest' failed. Please verify that the Microsoft Search
(Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There
was no endpoint listening at
net.tcp://localhost:3863/Management/SeedingAgent-64310690-DEA4-47E1-9860-E8B2AC4E292A12/Single that could accept the
message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more
details..
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Identity DBTest
Name
Status          CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
              Length    Length
State
DBTest\MBX2                              Mounted
0        0                                  Healthy
DBTest\MBX1                              Healthy
0         0           2/8/2015 3:09:49 PM    Unknown
DBTest\DRMBX1                            Healthy
0         0           2/8/2015 3:09:49 PM    Healthy
Same time
Result of get-serverhealth -server MBX1, also please note all database (Copy) search is in unhealthy condition and newly created copydatabase have no entry for "SearchCatalogAvailabilityMonitor".
Name
TargetResource
HealthSetName
AlertValue
SearchCatalogAvailabilityMonitor
DB01
Search
Unhealthy
SearchCatalogAvailabilityMonitor
DB06
Search
Unhealthy
Reg
Aditya

Hi Deepak
My both exchange servers on hyper V and there should not be resource problems.
However I have already rebooted server. but it wont help.
Mean while I get success to make search component healthy on my problematic server by below command but still content index folder is not coming automatically.
[PS] C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer>.\installconfig.ps1 -action I –dataFolder "C:\program files\Microsoft\Exchange Server\V15\bin\search\ceres\hostcontroller\data"
Configuring Search Foundation for Exchange....
Successfully configured Search Foundation for Exchange
By running this command these are in health state now.
Name
TargetResource
HealthSetName
AlertValue
SearchCatalogAvailabilityMonitor
DB01
Search
healthy
SearchCatalogAvailabilityMonitor
DB06
Search
healthy
Reg
Aditya

Custom Logical Disk monitor incorrectly flapping between healthy and unhealthy

One of the clients Ops Mgr 2012 SP1 UR8 environments I am supporting has had some custom logical disk monitoring setup; there are 5 groups dynamically populated by logical drives depending on their size (1st group has small drives up to the last group with
very large drives). There is a 'Warning' and 'Critical' Monitor setup per server OS version, the Monitors are not Enabled. There are Overrides applied to each group to enable the Monitor and apply a threshold - different threshold for each group.
During some BAU tuning I could see that some of the above Monitors were appearing as Top-Talking alerts. Further investigation showed that alerts were being triggered by drives that momentarily dropped below the applied threshold. I re-created the Monitors
from 'Simple Threshold' to 'Consecutive Samples' and set the 'Number of Samples' to 6 @ 3 minute intervals.
What I am seeing is that alerts from the above Monitors are still appearing as Top Talkers. When I check the Health Explorer of repeating alerts I can see the disk space is staying the same, below the applied threshold but the health is turning healthy then
back to unhealthy. I have confirmed each noisy Object has the expected threshold as per its dynamic group allocation and have also confirmed the drives are not fluctuating above and below the threshold. One thing I have noticed is that some drives Performance
View is patchy - lots of dotted lines between the coloured lines.
Its almost like the Monitor moves a Logical Disk Object into unhealthy state in the correct (and expected) manner, then it somehow picks up an incorrect threshold which is below the current usage level. This moves it into a healthy state only for the
whole process to repeat. For example: Drive X: on a server is very large, the Group that it sits in has a threshold of 102400MB, its current usage is ~stable at 45500MB. Looking in Health Explorer I can see 3:01pm green state/ 45573 last sampled value/ # of
samples 1 | 3:16pm yellow state/ 45573/ 6 samples | 3:34pm green state/ 45572/ 1 samples | 3:49pm yellow state/ 45571/ 6 samples | 4:01pm green state/ 45425/ 1 sample etc etc.
I'm scratching my head on this one and would appreciate any suggestions or assistance.
Thanks
BT

Thanks for the reply. It is not just one server / drive this is happening on. I am seeing it on everything; once they go into an unhealthy state they periodically go healthy and back again with no change in disk free space. Just to elaborate on how it is
setup; a Monitor has been created for each OS version (2003, 2008 and 2012) and a separate Monitor for Warning and Critical so 6 Monitors in total. Looking at the Warning Monitors; they are created with a threshold of 5120MB for 6 samples and set to disabled.
The following groups have been created and the following thresholds added:
Group 1 (less than 60GB size): override added to enable. This group will then pick up the 5120MB threshold.
Group 2 (60 – 250GB size): override added to enable and override added for 10240MB threshold
Group 3 (250 – 500GB size): override added to enable and override added for 20480MB threshold
Group 4 (500 – 1TB size): override added to enable and override added for 51200MB threshold
Group 5 (>1TB size): override added to enable and override added for 102400MB threshold
One drive I was looking at was in Group 2 (threshold of 10240MB), it was staying at approx. 8500MB but periodically going into healthy state then after 10mins (6 polls @ 2min intervals) back to unhealthy. This process repeats once or twice per day.
I am wondering if the Object is somehow picking up the threshold of the Monitor (5120MB) then going back to its correct overridden threshold. I have setup some test groups and monitors in a lab and will review the results over the coming days.
When the monitors were setup as 'Simple Threshold' this worked fine but were noisy due to drives spiking downwards. It was only when I re-wrote them as 'Consecutive Samples over Threshold' Monitors that this issue has started occurring.
Thanks

HubTransport and FrontendTransport marked as Unhealthy. How to diagnose and resolve?

I am trying to do an Exchange 2007 to 2013 migration. Before doing all the final repointing of DNS and proxying clients, I just want to make sure that the new Exchange 2013 is healthy. So I run a Get-HealthReport and it shows both the Online
states of HubTransport and FrontendTransport as Unhealthy.
In the event logs under Microsoft>Exchange>ManagedAvailability>Monitoring I see Error events for them about the client submission probe failed x times over 15 minutes. No connection because the target machine actively refused it 127.0.0.1:587.
There was also another one that said Unable to relay. For the Hub Transport it does not give as detailed information. It just says The HubAvailibilityProbe has failed 5 or more times in 15 minutes. Last failing server: ".
So it would sound like a connectivity problem, so with TELNET I tried to connect to port 25 and I get this:
telnet 127.0.0.1 25
421 4.3.2 Service not available
BUT if I put the hostname instead of 127.0.0.1, I get the 220 EMAIL.domain.com Microsoft ESMTP MAIL Service ready.
I tried temporarily disabling the windows firewall and its the same problem. I know SMTP is running because from another machine I can telnet to the mail server on port 25 and I get the SMTP banner.
So for me it seems like the Managed Availability is trying to use the IP address of 127.0.0.1 and that fails fundamentally for me when I try that in the command line, so no wonder why its marking the FrontendTransport as unhealthy. How can I resolve
this? I would think a resolution would be either somehow allow 127.0.0.1 access to relay which I DID put in my Frontend Transport receive connector, but it made no difference. Or the other option is somehow configure the probe to use the
hostname instead of 127.0.0.1.
As far as the HubTransport being unhealthy, I have a feeling its the same type of issue, but I am not seeing as detailed information in this path of the Event Viewer.

Bump....
No issues with mail flow but still getting this in the MOnitoring log from Managed Availability.
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: Microsoft-Exchange-ManagedAvailability
Date: 12/8/2014 11:11:29 AM
Event ID: 4
Task Category: Monitoring
Level: Error
Keywords:
User: SYSTEM
Computer: email.domain.com
Description:
The inbound proxy probe failed 3 times over 15 minutes.
Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Probe Exception: 'System.Exception: Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.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()'
Failure Context: 'Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Execution Context: ''
Probe Result Name: 'OnPremisesInboundProxy'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '9/25/2014 1:27:15 PM'
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-12-08T16:11:29.045528200Z" />
<EventRecordID>7358</EventRecordID>
<Correlation />
<Execution ProcessID="7604" ThreadID="1800" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>email.domain.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>FrontendTransport</HealthSet>
<Subject>The inbound proxy probe failed 3 times over 15 minutes.</Subject>
<Message>The inbound proxy probe failed 3 times over 15 minutes.
Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Probe Exception: 'System.Exception: Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.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()'
Failure Context: 'Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Execution Context: ''
Probe Result Name: 'OnPremisesInboundProxy'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '9/25/2014 1:27:15 PM'
</Message>
<Monitor>OnPremisesInboundProxyMonitor</Monitor>
</EventXML>
</UserData>
</Event>

Exchange 2013 CU2, Alert for OWA Health set unhealthy from SCOM 2012

I am facing issue in Exchange 2013 CU2, I got this alert from SCOM 2012 atleast 5-6 times a day, OWA health set is unhealthy, I have done all the steps mentioned in this web link. Authentication type for OWA Virtual directory is integrated windows and Basic.
I have 2 CAS servers, and this alert generated from both of them.
http://technet.microsoft.com/en-us/library/ms.exch.scom.OWA(EXCHG.150).aspx?v=15.0.712.24
Alert: Health Set unhealthy
Source: EX-CAS - OWA
Path: EX-CAS;EX-CAS
Last modified by: System
Last modified time: 1/5/2014 8:15:08 PM
Alert description: Outlook Web Access logon is failing on ClientAccess server EX-CAS.
Availability has dropped to 0%. You can find protocol level traces for the failures on C:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\OWA\ClientAccessProbe.
Incident start time: 1/6/2014 4:05:08 AM
Last failed result:
Failing Component - Owa
Failure Reason - CafeFailure
Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Failure source: Owa
Failure reason: CafeFailure
Failing component:Owa
Exception hint: CafeErrorPage: CafeFailure Unauthorized Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
---> Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseExceptionAnalyzer.Analyze(TestId currentTestStep, HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, Action`1 trackingDelegate)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.AnalyzeResponse[T](HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndSend[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse, Boolean fireResponseReceivedEvent)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndGet[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
   at Microsoft.Exchange.Net.MonitoringWebClient.Authenticate.AuthenticationResponseReceived(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
   at Microsoft.Exchange.Net.MonitoringWebClient.Owa.OwaLogin.AuthenticationCompleted(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Bool
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'EX-CAS' -HealthSet 'OWA'
State
Name
TargetResource                     HealthSet
AlertValue     ServerComponent
NotApplicable       OwaCtpMonitor
OWA
Unhealthy      None
States of all health sets:
Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX-CAS'
State
HealthSet
AlertValue     LastTransitionTime
MonitorCount
NotApplicable       ActiveSync
Healthy        1/3/2014 5:21:13 AM
2
NotApplicable       AD
Healthy        11/24/2013 6:54:18 AM
10
NotApplicable       ECP
Healthy        1/5/2014 3:03:05 AM
1
Online
Autodiscover.Proxy
Healthy        11/20/2013 10:06:37 AM
1
NotApplicable       Autodiscover
Healthy        1/3/2014 10:18:17 PM
2
Online
ActiveSync.Proxy
Healthy        11/20/2013 10:06:37 AM
1
Online
ECP.Proxy
    Healthy
11/21/2013 6:16:08 PM    4
Online
EWS.Proxy
Healthy        11/20/2013 10:06:37 AM
1
Online
OutlookMapi.Proxy
Healthy        11/24/2013 6:54:28 AM
4
Online
OAB.Proxy
Healthy        11/19/2013 7:14:34 PM
1
Online
OWA.Proxy
Healthy        11/20/2013 10:06:37 AM
2
NotApplicable       EDS
Healthy        1/3/2014 5:19:56 AM
10
Online
RPS.Proxy
Healthy        1/3/2014 5:21:27 AM
13
Online
RWS.Proxy                     Healthy
1/3/2014 5:20:09 AM      10
Online
Outlook.Proxy
Healthy        1/3/2014 5:21:12 AM
4
NotApplicable       EWS
Healthy        1/3/2014 10:18:17 PM
2
Online
FrontendTransport
Healthy        1/5/2014 3:47:09 AM
11
Online
HubTransport
Healthy        1/5/2014 3:47:09 AM
29
NotApplicable       Monitoring
Unhealthy      1/5/2014 4:05:57 AM
9
NotApplicable       DataProtection
Healthy        1/3/2014 5:25:42 AM
1
NotApplicable       Network                       Healthy
1/4/2014 1:51:16 PM      1
NotApplicable       OWA
Unhealthy      1/5/2014 8:05:08 PM
1
NotApplicable       FIPS
Healthy        1/3/2014 5:21:12 AM
3
Online
Transport
Healthy        1/5/2014 4:11:00 AM
9
NotApplicable       RPS
Healthy        11/20/2013 10:07:12 AM
2
NotApplicable       Compliance
Healthy        11/20/2013 10:08:10 AM
2
NotApplicable       Outlook
Healthy        11/21/2013 6:12:54 PM
2
Online
UM.CallRouter
Healthy        1/5/2014 3:47:10 AM
7
NotApplicable       UserThrottling
Healthy        1/5/2014 4:16:42 AM
7
NotApplicable       Search
                Healthy
11/24/2013 6:55:06 AM    9
NotApplicable       AntiSpam
Healthy        1/3/2014 5:16:43 AM
3
NotApplicable       Security
Healthy        1/3/2014 5:19:28 AM
3
NotApplicable       IMAP.Protocol
Healthy        1/3/2014 5:21:14 AM
3
NotApplicable       Datamining
Healthy        1/3/2014 5:18:34 AM
3
NotApplicable       Provisioning
Healthy        1/3/2014 5:19:56 AM
3
NotApplicable       POP.Protocol
Healthy        1/3/2014 5:20:44 AM
3
NotApplicable       Outlook.Protocol
Healthy        1/3/2014 5:19:46 AM
3
NotApplicable       ProcessIsolation
Healthy        1/3/2014 5:19:26 AM
9
NotApplicable       Store
Healthy       1/3/2014 5:20:38 AM
6
NotApplicable       TransportSync
Healthy        11/24/2013 6:53:09 AM
3
NotApplicable       MailboxTransport
Healthy        1/3/2014 5:21:11 AM
6
NotApplicable       EventAssistants
Healthy        11/21/2013 6:22:01 PM
2
NotApplicable       MRS
Healthy        1/3/2014 5:20:29 AM
3
NotApplicable       MessageTracing
Healthy        1/3/2014 5:18:15 AM
3
NotApplicable       CentralAdmin
Healthy        1/3/2014 5:17:25 AM
3
NotApplicable       UM.Protocol
Healthy        1/3/2014 5:17:08 AM
3
NotApplicable       Autodiscover.Protocol
Healthy        1/3/2014 5:17:13 AM
3
NotApplicable       OAB
Healthy        1/3/2014 5:20:51 AM
3
NotApplicable       OWA.Protocol
Healthy        1/3/2014 5:20:52 AM
3
NotApplicable       Calendaring
Healthy        11/24/2013 6:56:59 AM
3
NotApplicable       PushNotifications.Protocol
Healthy        11/21/2013 6:16:05 PM
3
NotApplicable       EWS.Protocol
Healthy        1/3/2014 5:19:07 AM
3
NotApplicable       ActiveSync.Protocol
         Healthy
1/3/2014 5:20:16 AM      3
NotApplicable       RemoteMonitoring
Healthy        1/5/2014 3:47:09 AM
3
Any solution for this alert, how to rectify it, but OWA is running perfect for all users.

Hi,
Sorry for the late reply.
Do we have Exchange 2010 coexistence?
If it is the case, I know the following known issue:
Release Notes for Exchange 2013
http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx
Please note the "Exchange 2010 coexistence" session.
If it is not related to our problem, please check the IIS log.
If there is any detailed error code, like 401.1, 401.2, please let me know.
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Compliance HealthSet unhealthy

Hello,
Today at 8 AM our Exchange 2013 server compliance health looks like out of the HealthSet 'Compliance' everything What does this mean and where should I look next?
[PS] C:\Windows\system32>Get-ServerHealth -Identity Server State Name TargetResource EMAIL NotApplicable AuditLogSearchCom... Compliance EMAIL NotApplicable MailboxSearch.Inc... Compliance EMAIL NotApplicable MailboxSearch.RPC... Compliance EMAIL NotApplicable MaintenanceFailur... EMAIL NotApplicable MaintenanceTimeou... EMAIL NotApplicable JournanlingMonitor Compliance EMAIL NotApplicable ComplianceOutlook... EMAIL NotApplicable ComplianceOutlook... EMAIL NotApplicable AsyncSearchServic... Compliance EMAIL NotApplicable Hold.HoldErrors.M... Compliance EMAIL NotApplicable PermanentPolicyAp... Compliance EMAIL NotApplicable UnknownPolicyAppl... Compliance EMAIL NotApplicable ELCTransientMonitor Compliance EMAIL NotApplicable ELCPermanentMonitor Compliance EMAIL NotApplicable ELCMailboxSLAMonitor Compliance EMAIL NotApplicable ELCDumpsterWarnin... Compliance EMAIL NotApplicable ChildPolicyApplic... Compliance EMAIL NotApplicable ApplyPolicyErrorM... Compliance EMAIL NotApplicable RuleExecutionErro... Compliance EMAIL NotApplicable DarTaskErrorMonitor Compliance EMAIL NotApplicable RetryTimeoutDarTa... Compliance EMAIL NotApplicable JournalFilterAgen... Compliance 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
is Healthy except for ELCDumpsterWarnin...
'EMAIL' -HealthSet 'Compliance'
HealthSetName AlertValue ServerComp
onent
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Unhealthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None
Compliance Healthy None

Ok 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.

OnPremisesSmtpClientSubmissionMonitor unhealthy

Similar Messages

Maybe you are looking for