Unable to access OWA or ECP if Mailbox Node one is down (DAG) , get me Blank web

Dears,

I have Exchange 2013 in my environment . the below is description for my environment:

- All servers are with windows 2012 r2

- I deployed 2 CAS servers (CAS01 & CAS02), then I configured Windows NLB .

- I deployed 2 Mailbox servers and configured DAG .

When I disconnect 1 server (CAS), I can access my mailbox . also, users can. my issue is when I power off Mailbox node 1 database moving to mailbox node 2 successfully , outlook still connected and can send or receive successfully. but I cant open OWA or ECP it get me blank screen. when I power mailbox node 1 again I can access OWA and ECP. 

I Uninstalled Exchange , IIS , and all things related to exchange on this node and reinstall it again with the same issue.

Any Idea?!!! 

June 7th, 2015 8:04am

Dears,

I have Exchange 2013 in my environment . the below is description for my environment:

- All servers are with windows 2012 r2

- I deployed 2 CAS servers (CAS01 & CAS02), then I configured Windows NLB .

- I deployed 2 Mailbox servers and configured DAG .

When I disconnect 1 server (CAS), I can access my mailbox . also, users can. my issue is when I power off Mailbox node 1 database moving to mailbox node 2 successfully , outlook still connected and can send or receive successfully. but I cant open OWA or ECP it get me blank screen. when I power mailbox node 1 again I can access OWA and ECP. 

I Uninstalled Exchange , IIS , and all things related to exchange on this node and reinstall it again with the same issue.

Any Idea?!!! 

Does it work if you go directly to the server that is still up?  I assume you are connecting to the load balanced name you have created on the NLB cluster yes?

WNLB is not optimal, so I have some suspicions that the problem lies there and not Exchange.

Free Windows Admin Tool Kit Click here and download it now
June 7th, 2015 8:19am

No, actually I tried when the working Node is down to logon with the below:

- Virtual Name (NLB Name).

- Virtual IP (NLB IP).

- Cas1 IP

- CAS2 IP 

all the above give me the same result. blank screen. this only happen when Mailbox 1 is down.

June 7th, 2015 8:22am

Hi, It sounds like your CAS server doesn't know the database has failed over and is still pointing users to the failed server.

Please run the following exhcange powershell command: Get-MailboxDatabase |fl Identity, RpcClientAccessServer

If it points to name of database servers,you will have to run the following command to point to your NLB name:

Set-MailboxDatabase "<<Affected Database>>" -RpcClientAccessServer mail.domain.com

where rpcclientaccessserver is name of you

Free Windows Admin Tool Kit Click here and download it now
June 7th, 2015 3:29pm

Hi, It sounds like your CAS server doesn't know the database has failed over and is still pointing users to the failed server.

Please run the following exhcange powershell command: Get-MailboxDatabase |fl Identity, RpcClientAccessServer

If it points to name of database servers,you will have to run the following command to point to your NLB name:

Set-MailboxDatabase "<<Affected Database>>" -RpcClientAccessServer mail.domain.com

where rpcclientaccessserver is name of you

June 7th, 2015 5:02pm

sry,but i thought Connection betweenCAS and mailbox goes over RPC and the command is still valid and can be configured. So thought it might be Worth a try:)
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2015 4:52am

I think the problem has been solved with me . the below is the solution:

login with this URL as I still have co-existence scenario (Exchange 2010 & Exchange 2013).

https://mail.domain.com\ecp\exchclientver=15 

But , only ECP working with me. still OWA get blank. so, I will complete migration and completely remove Exchange 2010 then try it again.

Kindly advise.

Thank you.

June 9th, 2015 8:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics