Exchange 2013 - Stability problems

Question

Hi All,

I'm having a couple of problems with an existing multirole on premise exchange 2013 server running within a DAG (consisting of another server)

The problems started after upgrading to CU21 and whilst this worked fine on the first server this doesn't appear as successful on the second. As it stands i'm getting so very odd issues, once of which involves the the following components going offline;

AutoDiscoverProxy

ActiveSyncProxy

EcpProxy

EwsProxy

OabProxy

OwaProxy

RpsProxy

RwsProxy

RpcProxy

MapiProxy

I've gone through the initial help guides which involve recycling the app pools and invoking the relevant monitoring probes but this doesn't seem to fix it. A server reboot also doesn't work.

I can temporarily fix the problem by running 'Set-ServerComponentState ServerName-Component As listed above -State Active -Requester HealthApi' which works for a couple of days, after that the above components go offline again.

Running the invoke commands (e.g. Invoke-MonitoringProbe OWA.Proxy\OwaProxyTestProbe -Server Servername | Format-List) all show the exact same problem, however running the same invoke commands for the 'working' server also gives me the same errors (so i'm unsure if this is actually the issue or if this is sending me on the red herring) the error is as follows;

System.InvalidOperationException: Unknown app pool name:

at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeProtocols.Get(String

appPool)

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()

Looking through google doesn't really give me much information around how to fix this problem so short of calling Microsoft support i thought i'd ask the community to see if anyone has come across this before and has any ideas on how to resolve it?

Any help would be greatly appreciated!

Kind Regards,

Mark

Answer 1

Because the issue is with Exchange 2013, I recommend posting to the Exchange forum in the TechNet, plus this forum is targeted to end users. The admins hang out in TechNet.

https://social.technet.microsoft.com/forums/en-...

Answer 2

Hi Mark,

As Diane mentioned, since your issue is related to On-premise Exchange 2013, and our team focus on Exchange Online service, to get further assistance, please post your issue in Exchange 2013 forum as the link provided by Diane. Looking forward to your understanding.

Best Regards,

Iry