Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 2, 2018 7:10 AM
Hi all, need the collective wisdom here on how to start on the troubleshooting for this alert raised by scom for my mailbox server.
Been digging around and doesn't seem to resolve the alert raised.
Exchange Admin Center logon is failing on Mailbox Server E1.
Availability has dropped to 4REPLACE_PERCENT_SIGN. You can find protocol level traces for the failures on F:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\ECP\EacBackEndLogonProbe.
Incident start time: 30/7/2018 8:02:53 AM
Last failed result:
Failing Component - Ecp
Failure Reason - PassiveDatabase
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. > 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: Ecp
Failure reason: PassiveDatabase
Failing component:Ecp
Exception hint: OwaErrorPage: Microsoft.Exchange.Data.Storage.WrongServerException
Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.OwaErrorPageException
ErrorPageFailureReason: PassiveDatabase, Exception type: Microsoft.Exchange.Data.Storage.WrongServerException, Exception trace: Exception:Microsoft.Exchange.Data.Storage.WrongServerException: The user and the mailbox are in different Active Directory sites. > Microsoft.Mapi.MapiExceptionMailboxInTransit: MapiExceptionMailboxInTransit: Detected site violation (hr=0x0, ec=1292)
End of inner exception stack trace
at Microsoft.Exchange.Data.Storage.MapiStoreFactory.CreateMapiStore(IMapiAccessor mapiAccessor, MapiStore linkedStore, IExchangePrincipal mailboxOwner, String userLegacyDn, ClientSecurityContext authenticationContext, LogonType logonType, OpenStoreFlag storeFlag, ConnectFlag connectFlag, UnifiedGroupAccess unifiedGroupAccess, RemoteMailboxProperties remoteMailboxProperties, CultureInfo internalPreferredCulture, Boolean nonInteractiveSession, String clientInfoString, Func`1 clientSessionInfoFactory)
at Microsoft.Exchange.Data.Storage.MailboxSession.<>c__DisplayClass218_0.<ForceOpen>b__0()
at Microsoft.Exchange.Data.Storage.Performance.MailboxOperationPerformanceTracker.RunOperationWithTrac
Message:Your mailbox isn't available right now. Please wait 30 seconds and then try to access it again.
MessageId:ErrorMailboxFailoverWithoutRedirection
MessageParameter:
SiteMailbox:False
GroupMailboxDestination:
Lids:
SupportLevel:Transient
Mode:
Microsoft.Exchange.Net.MonitoringWebClient.OwaErrorPageException: The response contained an OWA error page
WebExceptionStatus: Success
POST https://localhost:444/owa/proxylogon.owa HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 11.0; Trident/7.0; rv:11.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; EACBACKENDLOGON)
Accept: */*
Cache-Control: no-cache
X-FeToBeTimeout: 100
X-IsFromCafe: 1
X-CommonAccessToken: VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTBxNU0RTTkVUXEhlYWx0aE1haWxib3gxYTc5MDIzVS1TLTEtNS0yMS0xMDc3MzA5NTc4LTE4MjMwMDU5NjItNjYxNzkxMTIyLTU2OTNHBwAAAAcAAAAsUy0xLTUtMjEtMTA3NzMwOTU3OC0xODIzMDA1OTYyLTY2MTc5MTEyMi01MTMHAAAAB1MtMS0xLTAHAAAAB1MtMS01LTIHAAAACFMtMS01LTExBwAAAAhTLTEtNS0xNQcAAMAUUy0xLTUtNS0wLTE4Nzg2NjY1NzIHAAAACFMtMS0xOC0yRQAAAAA=
Content-Type:
HTTP/1.1 302 Redirect
Pragma: no-cache
X-Content-Type-Options: nosniff
request-id: 184229db-73f0-438f-9c32-69a44f3f3f72
X-RetriableError: 1
X-OWA-Error: Microsoft.Exchange.Data.Storage.WrongServerException
X-DBMountedOnServer: a08f4c6d-de36-4963-9cc6-03acb6aa3443~E2.domain~1942062471
X-ErrorTrace: RXhjZXB0aW9uOk1pY3Jvc29mdC5FeGNoYW5nZS5EYXRhLlN0b3JhZ2UuV3JvbmdTZXJ2ZXJFeGNlcHRpb246IFRoZSB1c2VyIGFuZCB0aGUgbWFpbGJveCBhcmUgaW4gZGlmZmVyZW50IEFjdGl2ZSBEaXJlY3Rvcnkgc2l0ZXMuIC0tLT4gTWljcm9zb2Z0Lk1hcGkuTWFwaUV4Y2VwdGlvbk1haWxib3hJblRyYW5zaXQ6IE1hcGlFeGNlcHRpb25NYWlsYm94SW5UcmFuc2l0OiBEZXRlY3RlZCBzaXRlIHZpb2xhdGlvbiAoaHI9MHgwLCBlYz0xMjkyKQ0KICAgLS0tIEVuZCBvZiBpbm5lciBleGNlcHRpb24gc3RhY2sgdHJhY2UgLS0tDQogICBhdCBNaWNyb3NvZnQuRXhjaGFuZ2UuRGF0YS5TdG9yYWdlLk1hcGlTdG9yZUZhY3RvcnkuQ3JlYXRlTWFwaVN0b3JlKElNYXBpQWNjZXNzb3IgbWFwaUFjY2Vzc29yLCBNYXBpU3RvcmUgbGlua2VkU3RvcmUsIElFeGNoYW5nZVByaW5jaXBhbCBtYWlsYm94T3duZXIsIFN0cmluZyB1c2VyTGVnYWN5RG4sIENsaWVudFNlY3VyaXR5Q29udGV4dCBhdXRoZW50aWNhdGlvbkNvbnRleHQsIExvZ29uVHlwZSBsb2dvblR5cGUsIE9wZW5TdG9yZUZsYWcgc3RvcmVGbGFnLCBDb25uZWN0RmxhZyBjb25uZWN0RmxhZywgVW5pZmllZEdyb3VwQWNj
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'E1' -HealthSet 'ECP'
State Name TargetResource HealthSet AlertValue ServerComponent
NotApplicable NewAdminApiBackEndLogonMonitor ECP Healthy None
NotApplicable Ecp.EventLog.LandingDefaultPageError... ECP Healthy None
NotApplicable PrivateWorkingSetError.msexchangeadm... msexchangeadminapiapppool ECP Healthy None
NotApplicable PrivateWorkingSetWarning....changead... msexchangeadminapiapppool ECP Healthy None
NotApplicable Ecp.EventLog.HttpUnhandledExceptionR... ECP Healthy None
NotApplicable MaintenanceFailureMonitor.ECP ECP Healthy None
NotApplicable PrivateWorkingSetError....changemana... msexchangemanagementapppool ECP Healthy None
NotApplicable PrivateWorkingSetError.msexchangeecp... msexchangeecpapppool ECP Healthy None
NotApplicable CrashEvent.msexchangeecpapppool msexchangeecpapppool ECP Healthy None
NotApplicable ProcessProcessorTimeWarning....emana... msexchangemanagementapppool ECP Healthy None
NotApplicable ProcessProcessorTimeError.msexchange... msexchangeecpapppool ECP Healthy None
NotApplicable PrivateWorkingSetWarning.msexchangee... msexchangeecpapppool ECP Healthy None
NotApplicable CrashEvent.msexchangemanagementapppool msexchangemanagementapppool ECP Healthy None
NotApplicable ProcessProcessorTimeWarning.msexchan... msexchangeecpapppool ECP Healthy None
NotApplicable CrashEvent.msexchangeadminapiapppool msexchangeadminapiapppool ECP Healthy None
NotApplicable EacBackEndPingMonitor ECP Healthy None
NotApplicable PrivateWorkingSetWarning....angemana... msexchangemanagementapppool ECP Healthy None
NotApplicable EacBackEndLogonMonitor ECP Unhealthy None
NotApplicable ProcessProcessorTimeError....hangead... msexchangeadminapiapppool ECP Healthy None
NotApplicable ProcessProcessorTimeWarning....ngead... msexchangeadminapiapppool ECP Healthy None
NotApplicable AdminApiBackEndLogonMonitor ECP Healthy None
NotApplicable ProcessProcessorTimeError....ngemana... msexchangemanagementapppool ECP Healthy None
NotApplicable MaintenanceTimeoutMonitor.ECP ECP Healthy None
Note: Subsequent detected alerts are suppressed until the health set is healthy again.
Knowledge: http://technet.microsoft.com/en-us/library/ms.exch.scom.ECP(EXCHG.150).aspx?v=15.1.1415.2
All replies (7)
Thursday, August 9, 2018 8:30 AM âś…Answered
Hi Jacy,
If you have installed updates released on 7/10, please install the associated KB to fix it:
Issue with July Updates for Windows on an Exchange Server
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Friday, August 3, 2018 4:51 AM
Hi,
Have you recently install any security updates on Exchange server?
For troubleshooting:
1. Go to the following path to check if the folders are empty.
Folder 15.x.xxxx.xx in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp
Folder 15.x.xxxx.xx in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa
2. Besides, in IIS manager, go Exchange Back End -> ecp -> Application Settings in /ecp Home -> BinSearchFolders
Check if the values are as follows:
%ExchangeInstallDir%bin;%ExchangeInstallDir%bin\CmdletExtensionAgents;%ExchangeInstallDir%ClientAccess\Owa\bin
In my lab, they are:
C:\Program Files\Microsoft\Exchange Server\V15\bin;C:\Program Files\Microsoft\Exchange Server\V15\bin\CmdletExtensionAgents;C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin
3. Recycle the ecp application pool:
Restart-WebAppPool msexchangeecpapppool
4. Run Updatecas.ps1 under %ExchangeInstallDir%bin.
5. If all the above steps doesn't work, run the below command to check the ecp VD settings:
Get-EcpVirtualDirectory -Server <SERVERNAME> | fl *auth*,*url*
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Monday, August 6, 2018 6:51 AM
Hi Manu,
Thanks for the advice! I did patched in July, and both my ECP and OWA folder is not empty. I followed your steps and it seems like the alert isn't coming back. Will monitor and see if it does stay silent.
Monday, August 6, 2018 6:55 AM
Hi Manu,
Thanks for the advice! I did patched in July, and both my ECP and OWA folder is not empty. I followed your steps and it seems like the alert isn't coming back. Will monitor and see if it does stay silent.
OK, feel free to post back if there is any update about the issue.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Tuesday, August 7, 2018 12:56 AM
The alerts came back again.
I ran Get-EcpVirtualDirectory -Server <SERVERNAME> | fl *auth*,*url* and all my exchanges servers have the same output of
InternalAuthenticationMethods: {Basic, FBA}
BasicAuthentication: True
WindowsAuthentication: False
DigestAuthentication: False
FormsAuthentication: True
LiveIdAuthentication: False
AdfsAuthentication: False
OAuthAuthentication: False
ExternalAuthenticationMethods: {FBA}
InternalUrl: https://domain/ecp
ExternalUrl: https://domain/ecp
Wednesday, August 15, 2018 8:53 AM
Hi,
It has been a long time since you made the last post on this thread. If you could get any help from the above posts, please be free to mark them as answers, it will be easy for other community members to find the useful one/ones.
Thanks for your understandings!
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Monday, September 3, 2018 1:54 AM
Hi Manu,
sorry for the slow reply. Finally got around to a downtime where i can patch them. It was really the patches that was affecting it.