Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance 论坛
Viewing all articles
Browse latest Browse all 8719

Help with Autodiscover.Proxy Unhealthy state.

$
0
0

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.



Viewing all articles
Browse latest Browse all 8719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>