Exchange 2019 Database Server Status ServiceDown

Question

Exchange 2019 Database Server Status ServiceDown

Mohd Azrul Kusrin 1

Dear all,
Current infra:

HQ:
HQEMLAPP01 - Ex2019
HQEMLAPP02 - Ex2019

DRC:
DRCEMLAPP01- Ex2019

Exchange 2019 servers stretched between 2 datacenter, HQ and DRC.

Issue:
Sometime the status for Mailbox Database Copies shown as below.

From DRC Exchange server:

From HQ Exchange server:

If result as above shown, we need to restart the Exchange server at DRC site to fix the issue.
Is there any solution to this and what needs to be checked for. Is there any firewall blocking, WMI or any related finding.
Since we need to frequently check the status for server at DRC and if the issue raised, then Mailbox Database replication will have issue until the server being restarted.

Regards,
Mohd

LilyLi2-MSFT 1,981 Reputation points

2022-12-16T03:16:57.237+00:00

Hi @Mohd Azrul Kusrin ,

Was Andy's reply helpful to you?
As Andy said, you should make sure that all ports are open.

Besides, when the database status shows ServiceDown, you could also check whether the replication service of the server is started. If not, start the service.
For more information, please refer to: 52407.exchange-2019-database-status-showing-servicedown.aspx

Thanks.
Mohd Azrul Kusrin 1 Reputation point

2022-12-16T20:52:50.85+00:00

Hi Lily,
During the issue, all Exchange related services were started. Even we tried to restart the service, status for database remain ServiceDown.
Once rebooted, status change back to healthy and replication resumed.

Will take a look on that link provided.

Thanks,
Mohd
LilyLi2-MSFT 1,981 Reputation points

2022-12-19T09:37:18.543+00:00

Hi,
Thanks for your reply.

I'm here to confirm that is there any progress with the issue?
Did you follow Andy's suggestion to check the ports?

Kind Regards
Mohd Azrul Kusrin 1 Reputation point

2022-12-19T21:20:32.153+00:00

Hi Lily,
Security team informed that they didn't filter traffic between those Exchange servers.
I passed to them error that we get, but they keep saying no filtering in place.

Is there any way to proof the traffic between those servers being filtered?

Regards,
Mohd
Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator

2022-12-20T12:39:58.853+00:00

logon to a DAG member in one site and try to connect to another DAG member in another site using telnet on TCP port 64327

From the DR Server:
Telnet <HQ Server> 64327
Mohd Azrul Kusrin 1 Reputation point

2022-12-21T00:08:11.457+00:00

Hi Andy,
Telnet from DRC server to HQ server don't have issue.
Other ports required also allowed when being tested using telnet command.

Came across to one finding during the issue, I cannot access HQ server UNC path.
Example: from DREMLAPP01 I cannot access \HQEMLAPP01 or \HQEMLAPP02 shared folder.

"The specified network name is no longer available" error prompted.

But, once I restart DRC server then I can access those UNC path to HQ server.

Thanks.
Mohd
LilyLi2-MSFT 1,981 Reputation points

2022-12-27T06:47:37.837+00:00

Hi,

Sorry for the late reply.

I found a similar thread that solved the problem by disabling IPv6 and removing the DNS entry, you can check out the related discussion:
https://social.technet.microsoft.com/Forums/exchange/en-US/1c47e857-ebd9-45c6-9759-d355794c301a/dag-copy-status-service-down
Mohd Azrul Kusrin 1 Reputation point

2022-12-27T23:51:24.607+00:00

Hi,
IPv6 being disable on NIC properties after server being setup.
From DNS server also no records for AD & Exchange IPv6 address.
From nslookup no IPv6 records exist.

Thanks.
Mohd

1 answer

Your answer

LilyLi2-MSFT 1,981 Reputation points

2022-12-16T03:16:57.237+00:00

Hi @Mohd Azrul Kusrin ,

Was Andy's reply helpful to you?
As Andy said, you should make sure that all ports are open.

Besides, when the database status shows ServiceDown, you could also check whether the replication service of the server is started. If not, start the service.
For more information, please refer to: 52407.exchange-2019-database-status-showing-servicedown.aspx

Thanks.
Mohd Azrul Kusrin 1 Reputation point

2022-12-16T20:52:50.85+00:00

Hi Lily,
During the issue, all Exchange related services were started. Even we tried to restart the service, status for database remain ServiceDown.
Once rebooted, status change back to healthy and replication resumed.

Will take a look on that link provided.

Thanks,
Mohd
LilyLi2-MSFT 1,981 Reputation points

2022-12-19T09:37:18.543+00:00

Hi,
Thanks for your reply.

I'm here to confirm that is there any progress with the issue?
Did you follow Andy's suggestion to check the ports?

Kind Regards
Mohd Azrul Kusrin 1 Reputation point

2022-12-19T21:20:32.153+00:00

Hi Lily,
Security team informed that they didn't filter traffic between those Exchange servers.
I passed to them error that we get, but they keep saying no filtering in place.

Is there any way to proof the traffic between those servers being filtered?

Regards,
Mohd
Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator

2022-12-20T12:39:58.853+00:00

logon to a DAG member in one site and try to connect to another DAG member in another site using telnet on TCP port 64327

From the DR Server:
Telnet <HQ Server> 64327
Mohd Azrul Kusrin 1 Reputation point

2022-12-21T00:08:11.457+00:00

Hi Andy,
Telnet from DRC server to HQ server don't have issue.
Other ports required also allowed when being tested using telnet command.

Came across to one finding during the issue, I cannot access HQ server UNC path.
Example: from DREMLAPP01 I cannot access \HQEMLAPP01 or \HQEMLAPP02 shared folder.

"The specified network name is no longer available" error prompted.

But, once I restart DRC server then I can access those UNC path to HQ server.

Thanks.
Mohd
LilyLi2-MSFT 1,981 Reputation points

2022-12-27T06:47:37.837+00:00

Hi,

Sorry for the late reply.

I found a similar thread that solved the problem by disabling IPv6 and removing the DNS entry, you can check out the related discussion:
https://social.technet.microsoft.com/Forums/exchange/en-US/1c47e857-ebd9-45c6-9759-d355794c301a/dag-copy-status-service-down
Mohd Azrul Kusrin 1 Reputation point

2022-12-27T23:51:24.607+00:00

Hi,
IPv6 being disable on NIC properties after server being setup.
From DNS server also no records for AD & Exchange IPv6 address.
From nslookup no IPv6 records exist.

Thanks.
Mohd

Answer 1

Andy David - MVP 157.4K MVP Volunteer Moderator

Ensure that that the all ports are open between the data centers between the Exchange Servers and to all the domain controllers.
https://learn.microsoft.com/en-us/exchange/plan-and-deploy/deployment-ref/network-ports?view=exchserver-2019

Mohd Azrul Kusrin 1 Reputation point

2022-12-16T20:50:31.037+00:00

Hi Andy,
Currently waiting for security team confirmation whether they already required ports for Active Directory and Exchange servers.

Just some additional information, DRC site network setup was configured using multisite. Which means same VLAN extended into DRC site.
All servers at HQ and DRC will have same IP address subnet.

Thanks,
Mohd
Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator

2022-12-16T21:05:40.08+00:00

Yea, I would verify that nothing is blocking any ports between Exchange Servers and domain controllers!

Share via

Exchange 2019 Database Server Status ServiceDown

1 answer

Your answer