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

Similar Messages

  • Exchange 2013 Managed Availability: ProcessIsolation HealthSet unhealthy.

    In env with 2 CAS and 3 MB Servers, all 2013 CU3, the ProcessIsolation healthset is market as Unhealthy. Here is the result from the monitor:
    < Message > Maintenance workitem "Process.Isolation.Maintenance.Workitem" (ID: 64) has failed. Health Manager has detected it is either set to run once and failed, or has been failing consistently. Maintenance workitem failure could cause
    monitoring gap and should be investigated. The error message from the last result is: workitem completed with result: TimedOut ------------------------------------------------------------------------------- States of all monitors within the health set: Note:
    Data may be stale....<Result from Get-HealthReport here>.........
    Note: Subsequent detected alerts are suppressed until the health set is healthy again. </ Message >
    Using get-serverhealth I can see that "ProcessIsolation\MaintenanceFailureMonitor.ProcessIsolation\" is Unhealthy.
    I cannot find any documentation regarding this Healthset. How should I investigate this?

    Hi,
    Is there any related error message in the Application log?
    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

  • 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

  • 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: <b>MachineName:</b>
    EMAIL <b>ServiceName:</b> Autodiscover.Proxy <b>ResultName:</b> AutodiscoverProxyTestProbe/MSExchangeAutodiscoverAppPool <b>Error:</b> The remote server returned an error: (500) Internal Server Error. <b>Exception:</b>
    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() <b>ExecutionContext:</b> 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. <b>FailureContext:</b> <b>ResultType:</b> Failed <b>IsNotified:</b> False <b>DeploymentId:</b> 0 <b>RetryCount:</b> 0 <b>ExtensionXml:</b> <b>StateAttribute1:</b>
    No response headers available. <b>StateAttribute2:</b> [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][
    <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> 0 <b>StateAttribute21:</b> <b>StateAttribute22:</b> <b>StateAttribute23:</b>
    <b>StateAttribute24:</b> <b>StateAttribute25:</b> <b>PoisonedCount:</b> 0 <b>Client Access Array:</b> Client Access Array name could not be retrieved. <b>ExecutionId:</b> 30334093 <b>ExecutionStartTime:</b>
    12/23/2014 12:03:08 PM <b>ExecutionEndTime:</b> 12/23/2014 12:03:08 PM <b>ResultId:</b> 32263287 <b>SampleValue:</b> 0</message> <monitor>AutodiscoverProxyTestMonitor/MSExchangeAutodiscoverAppPool</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

  • Tuning Exchange 2013 HealthSet Monitors (example: MailboxTransport - Mapi.Submit.Monitor)

    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'

  • Health set components seems to be unhealthy

    Hi,
    In my environment health sets components seems to be unhealthy but there is no problem with user side
    Below are the components
     HealthSet           AlertValue
     MailboxTransport    Unhealthy
     HubTransport        Unhealthy
     ECP                 Unhealthy
     Search              Unhealthy
     Store               Unhealthy
     MSExchangeCertif... Disabled
     DataProtection      Unhealthy
     RPS                 Unhealthy
     RWS                 Unhealthy
     Compliance          Unhealthy
     Outlook             Unhealthy
    Can somebody help me through this please.

    Hello,
    I think you can combine the heltht reports with the application log?
    Is there any warning or error reprot in it about these unhealty items. If no, I think we can safely ingore these errors.
    Thanks,
    Simon Wu
    TechNet Community Support

  • HealthSet issue since CU6

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

    Hi 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

  • 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>

  • 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.&lt;&gt;c__DisplayClass2.&lt;StartExecuting&gt;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 SP1 - healthsets failing

    Hi,
    I have recently installed two Exchange 2013 SP1 servers in different environments and are experiencing issues on both. Issues that I haven't seen on Exchange 2013 without SP1.
    I have 6 healthsets which are unhealthy. 
    Autodiscover...
    ActiveSync.P...
    EWS.Proxy
    OAB.Proxy
    Outlook.Proxy
    OutlookMapiH...
    I found this article: 
    http://technet.microsoft.com/en-us/library/ms.exch.scom.ecp.proxy(v=exchg.150).aspx
    Which describes, that try to restart the app pool, then an iisreset - and lastly reboot the server. Tried all and none of them helped.
    But then I found this error in the Exchang event log:
    RecycleApplicationPool-MSExchangePowerShellAppPool-RpsDeepTestPSProxyRestart: Throttling rejected the operation
    Which fails almost every minute.
    And I guess that this could be the issue. But I can't figure out which throttling that is causing this.
    Any one else with this issue on Exchange 2013 SP1?
    Thanks in advance.
    /Kim

    Hi,
    I have seen a lot of similar issues with health manager service. For IIS services, we can safely ignore these warnings. Personal experience, we just need to monitor whether there are related
    error reports in event log.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Get-healthreport unhealthy

    Hi all,
    been installing Exchange 2013 ( cu1,cu2 and cu3) a couple of times and out of the Box it seems like some healthset are unhealthy or disabled.
    Still everything seems to work (most important like ActiveSync,owa,oab and ecp) even those healthsets are unhealthy.
    What is the main reason for this?
    My lab environment is really simple,only firewall is my D-Link router,no co-existing (just Exchange 2013) With one site and one AD.
    Thanks!
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Hi,
    According to the screenshot, we can see that the Outlook.Proxy health set is unhealthy.
    I recommend you refer to the following article to troubleshoot the issue:
    Troubleshooting Outlook.Proxy Health Set
    The Outlook.Proxy health set monitors the availability of the Outlook Anywhere proxy infrastructure on the Client Access server (CAS).
    If you receive an alert that specifies that the Outlook.Proxy service is unhealthy, this indicates an issue that may prevent users from accessing their mail.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • ADA 508 Compliance Workflow Overview (tab key for navigation / WebAim Toolbar)

    Hi,
      I've been assigned to update interactive training for a State agency..... with of course, an emphasis on ADA / 508 compliance.
    So, before I pinpoint my two questions/scenarios, here is a basic, initial attempt at providing an overview of ADA compliance workflow in Captivate and beyond. 
    PS - useful Captivate forum urls are at the end of this post. I'm using Captivate v.6
    ADA Compliance Workflow Overview:
    1. All assets need an alt tag and conceivably a description > highlight the asset, like a pic, and click the Accessibility button under Properties.
    2. Create slide notes for each slide > load slide, highlight no assets and click the Accessibility tab under Properties. Copy and paste your notes > for screen readers.
    3. Need closed captioning for video/audio content > I use Camtasia for CC and will use the JW player for screen reader of video content.
    4. Interactivity needs to be accessible via the tab and enter keys.
    What else am I missing?
    Question 1
    My question targets how to get the enter key to initiate after a successful tab. To be clearer.... I hit tab and I can navigate through all the buttons in the correct order, but hitting enter provides no action. I am gettining the yellow highlights around buttons when I tab through. Everything works very well when using the mouse, but blind users don't use mice.
    I did create my own animation buttons in Flash and imported them in as animations. I then placed a Click Box behind the button animation to engage the rollover action. Could this be causing problems? The prebuilt (and clunky looking) buttons on the quizzes do work (ie) tabbing to them and hitting enter provides effective navigation.
    I'm opting not to use the playback control skin, only my Flash nav bar.
    Question 2 (Scenario 2)
    I have downloaded the WebAim Toolbar feature designed for FireFox, used to check ADA compliance issues.
    I am getting this error message:
    A frame does not have a title attribute or value. Okay... I bet I can fix this via the .html file or via the standard.js file??
    and these warnings:
    Alert: Javascript in head - A javascript element is present in the page head section.
    Alert: Flash - A Flash object is present.
    Does anyone know if these alerts are worth fixing?
    Obviously Captivate is going to pump out, or rather publish... javascript elements, but is this bad in the page head section?
    And..... of course a Flash object is present...Captivate produces Flash / Shockwave files.
    I'll obviously ask the programmers at WebAim for guidance as well. As always any help would be appreciated and Tanks in advance.
    http://forums.adobe.com/message/117985#117985
    http://gneil.blogspot.com/2008/09/target-6-million-settlement-is-your.html
    http://kb2.adobe.com/cps/403/kb403160.html
    http://forums.adobe.com/message/3515968#3515968
    Screen grabs are attached.
    Thanks, Calif Dreamin'

    Hi,
      Attached is my zipped project file. I did create my own buttons in Flash - this might be the problem. I have only been problem solving with navigation on the first four slides.
      To clarify, hitting the Enter key does engage navigation, however I’m having difficulty controlling the navigation so that it goes to the correct location.
      I’m using Captivate v.6 / publishing SCORM 1.2 / Using IE to deliver via the SyberWorks LMS.
    Here is question 1:
    Question 1
    My question targets how to get the enter key to initiate after a successful tab. To be clearer.... I hit tab and I can navigate through all the buttons in the correct order, but hitting enter provides no action. I am getting the yellow highlights around buttons when I tab through. Everything works very well when using the mouse, but blind users don't use mice.
    I did create my own animation buttons in Flash and imported them in as animations. I then placed a Click Box behind the button animation to engage the rollover action. Could this be causing problems? The prebuilt (and clunky looking) buttons on the quizzes do work (ie) tabbing to them and hitting enter provides effective navigation.
    I'm opting not to use the playback control skin, only my Flash nav bar.
    Thanks for reaching out!!
    Thanks,
    Bill Farrell  (aka Calif Dreamin’)

  • Update showing up in "Compliance 5 - Specific Computer" Report even after removing the update from the Software Update before creating Group and Package

    So I've created a Software Update Group and I did NOT want anything in there dealing with Internet Explorer 11 since the organization is currently stuck at using 10 as the highest. So I made sure that Internet Explorer was NOT in the list and then I deployed
    the package. 
    After running my Overall Compliance report it shows that the systems are compliant, but when I view the "Compliance 5 - Specific Computer" I see that "Internet Explorer 11 for Windows 7 for x64-based Systems" is listed in the report. 
    This is just a testing phase right now and I have not created a WSUS like Domain level GPO. I understand that the SCCM client creates a local policy on the clients for the location of the Software Update Point (Specify
    Intranet Microsoft update service location), but the "Configure Automatic Updates" policy is set to Not Configured, which it looks like when this
    is set, the "Install updates automatically (recommended)" at 3AM is the default. 
    Is the reason why the "Internet Explorer 11 for Windows 7 for x64-based Systems" update is showing up in the list due to the fact that the "Configure
    Automatic Updates" policy is set to Not Configured
    and therefore it is still reaching out to check Windows Update online? 
    So, if I do create a Domain level GPO to Disable the "Configure
    Automatic Updates" policy, then the "Internet Explorer 11 for Windows 7 for x64-based Systems" update would not show up in the "Compliance 5 - Specific Computer" report?
    By the way, I have a Software Update Maintenance Window configured for the hours of 1AM-4AM so the 3AM default time falls within this time frame, therefore, I am assuming the SCCM 2012 client will not allow the Windows Update Agent to install the "Internet
    Explorer 11 for Windows 7 for x64-based Systems" update, even though it has detected it is "Required". 
    Thanks

    But, don't you need a Deployment Package in order to deploy the Software Update Group? The Software Update Group uses the downloaded updates contained in the Deployment Package located in, wherever the Package Source is, right?
    One more quick question that you will know right off hand, because, well, you just will I'm sure.
    No. The software update group really has nothing to do with any update packages. The update group assigns updates to clients and in turn clients use update packages to download assign and applicable updates from. There is no connection between the two though
    as the client can download an update from any available update package. Thus, it's more than possible to updates in an update package that are not in any update groups and it is also possible for an update to be in an update group without being in any update
    package.
    If the "Configure Automatic Updates" policy is set to "Not Configured" and since this keeps the 3AM Automatic Updates default, if I was to remove the Software Update Maintenance Window from being between 1AM-4AM, will the WUA agent install updates
    at 3AM, or no because the SCCM 2012 client still manages and oversees it and basically blocks that from occurring?
    No, ConfigMgr does not in any way block the WUA; however, the WUA can only autonomously install updates it downloads directly from WSUS. Thus, since there are no updates approved or downloaded in your WSUS instance, there's nothing for it to download and
    install. If you happen to actually be going into WSUS and approving updates (which you should not be doing as its unsupported), then yes, it actually would install updates -- this is outside of ConfigMgr's control though. Generally, disabling the WUA via a
    GPO is the recommended to prevent any accidental installations or reboots (as the WUA wil also check for initiate pending reboots outside of ConfigMgr).
    Lots more info in these two blog posts:
    - http://blog.configmgrftw.com/software-update-management-and-group-policy-for-configmgr-what-else/
    - http://blog.configmgrftw.com/software-updates-management-and-group-policy-for-configmgr-cont/
    Jason | http://blog.configmgrftw.com

  • 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

Maybe you are looking for

  • Burn 7 times (Playlist or individual MP4 file)

    I buy the new Daughtry album. I create a new Playlist and call it Daughtry S/T and drag the songs into it. Now I can burn that playlist 7 times. If I cahnge the name of the Playlist to Daughtrt 1st CD does this give me a new 7 times or are the indivi

  • HOw to improve insert/update/select  for nested table.

    Hi All, I think this is my second thread for nested table. i just want to know what are the different ways available to improve the insert/update/select operation on Nested table. Thanks in advance.

  • Document type should always post to specific account type

    Hello experts, I have 1 question,  Depeneding on the Document type definition I can post to different account types (S, K, D , M ,A). Assume I created a doc type ZA and checked all the account types then it allows me post to all the account types. He

  • Linebreak in Indesign xsl?

    Hey guys, I have a little question about xsl. I tried to solve it myself, but I can't get it done. My xsl looks like this: <?xml version="1.0" encoding="UTF-8" ?> <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" xmlns:ex=

  • Fade out/fade in

    A couple months ago someone (Karsten Schluter?) showed me a cool way to fade out / fade in my titles without separating each title by a few frames and then applying a cross dissolve to all. I have been under a lot of pressure since my wife of 61 year