July 21, 2015 at 7:14 am
Hi Guys,
I am configuring our first DB mirror, our PRIMARY server has been running for quite a few months now but the MIRROR server is just a few days old. Both servers are running on Windows Server 2012 R2 and SQL Server 2008 R2 Standard. Both have the same patch and service packs installed. Both have dual NIC and configured like so:
Principal Server Configuration
Name: MICROSQL1.domain.com
NIC1 : 172.16.0.80
NIC2 : 172.16.0.81 (use for mirroring)
Named Instances:
SQLSERVER1
SQLSERVER2
Mirror Server Configuration
Name: MICROSQL2.domain.com
NIC1 : 172.16.0.82
NIC2 : 172.16.0.83 (use for mirroring)
Named Instances:
SQLSERVER1
SQLSERVER2
NO WITNESS YET
A records in DNS server
172.16.0.81 dbm-pri.domain.com
172.16.0.83 dbm-mir.domain.com
I followed every step for configuring mirroring on a dedicated NIC as itemized in this blog:
But when I issue the ALTER DB SET PARTNER command on the PRIMARY, I get the dreaded
Msg 1418, Level 16, State 1, Line 2
The server network address "" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
Both endpoints status are STARTED, both SQL Service are running on a common Domain\User account, the same account has been granted CONNECT permission on both server. I already gave sysadmin server permission to the sql service account. Opened the 6024-6027 ports, tried all other ports, eventually disabled the Firewall on both server, named pipes are enabled on SQL SERVER Config Manager for both server and all INSTANCES. Both servers answer to ping and tracert also resolves even from other servers/workstation w/in the network
But I still get the said error, tested via netstat and the ports are not listening on both server, telnet connection is being refused.
I am really out of ideas, I've also asked another forum and we reached a dead end. I might be missing something on the MIRROR server as it is new, might have missed to configure something..
July 21, 2015 at 10:05 am
firstly check the windows firewall on both nodes.
rcaballero (7/21/2015)
But when I issue the ALTER DB SET PARTNER command
what commands did you use to create the database mirroring endpoints on each instance?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 21, 2015 at 10:40 am
these commands
---ON Mirror---
CREATE ENDPOINT SQLSERVER1_EndPoint
STATE=STARTED
AS TCP (LISTENER_PORT=6025,LISTENER_IP=(172.16.0.81))
FOR DATABASE_MIRRORING (ROLE=PARTNER)
---ON Principal---
CREATE ENDPOINT SQLSERVER1_EndPoint
STATE=STARTED
AS TCP (LISTENER_PORT=6024,LISTENER_IP=(172.16.0.83))
FOR DATABASE_MIRRORING (ROLE=PARTNER)
and here are the set partner commands
--ON Mirror--
ALTER DATABASE DBName
SET PARTNER = 'TCP://dbm-pri.domain.com:6024'
--ON Primary--
ALTER DATABASE DBName
SET PARTNER = 'TCP://dbm-mir.domain.com:6025'
July 22, 2015 at 4:44 am
looks ok initially, any other errors in the event logs or sql logs
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 22, 2015 at 5:13 am
every time I run the ALTER..SET PARTNER on the PRIMARY, I get these logged under the SQL Logs
- Database mirroring has been terminated for database 'DBName'. This is an informational message only. No user action is required
- Message
Error: 1443, Severity: 16, State: 2.
That's it, there's nothing logged on the MIRROR server
July 22, 2015 at 5:39 am
rcaballero (7/22/2015)
every time I run the ALTER..SET PARTNER on the PRIMARY, I get these logged under the SQL Logs- Database mirroring has been terminated for database 'DBName'. This is an informational message only. No user action is required
- Message
Error: 1443, Severity: 16, State: 2.
That's it, there's nothing logged on the MIRROR server
Check the DNS records are correct, confirm you have registered the dedicated mirroring NICs for DNS.
Ping each fqdn from a partner node and ensure a timely response.
Double check firewalls, have you performed a telnet?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 22, 2015 at 6:04 am
Perry Whittle (7/22/2015)
rcaballero (7/22/2015)
every time I run the ALTER..SET PARTNER on the PRIMARY, I get these logged under the SQL Logs- Database mirroring has been terminated for database 'DBName'. This is an informational message only. No user action is required
- Message
Error: 1443, Severity: 16, State: 2.
That's it, there's nothing logged on the MIRROR server
Check the DNS records are correct, confirm you have registered the dedicated mirroring NICs for DNS.
Ping each fqdn from a partner node and ensure a timely response.
Double check firewalls, have you performed a telnet?
On the DNS Server I created these A records:
172.16.0.81 dbm-pri.mydomain.com static
172.16.0.83 dbm-mir.mydomain.com static
Firewall is temporarily OFF but there are rules created for the ports used, ping on each fqdn works from each partner node and from other servers.
Telnet does not work "telnet fqdn port" returns "cannot open connection to host on port "
netstat does not show the ports to be listening
July 22, 2015 at 7:07 am
check the endpoints to make sure theyre started
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 22, 2015 at 7:19 am
Perry Whittle (7/22/2015)
check the endpoints to make sure theyre started
yes they are started, here's the status on principal
SQLSERVER1_EndPoint DATABASE_MIRRORING STARTED 6024 172.16.0.83
on mirror
SQLSERVER1_EndPoint DATABASE_MIRRORING STARTED 6025 172.16.0.81
July 23, 2015 at 5:55 am
Ok, this is getting ridiculously painful... here's what I did so far:
-deleted previously created endpoints and ran alter db set partner off
-went into SQL Server Config Manager and made sure TCP is enabled, then added the endpoint ports to the TCP All field
- restarted the SQL Service
- run netstat and confirmed that the endpoint ports are now LISTENING
- from both PRINCIPAL and MIRROR, ran "telnet FQDN port", confirmed that I can connect from both (as opposed to failing a few posts above)
- created the endpoints on both servers
- granted connect permission to the sqlservice account (same service account on BOTH servers, I am using a domain\user account)
- backed up and restored DB and logs with NO RECOVERY
- ran alter db set partner on the mirror server - SUCCESS
- ran alter db set partner on principal server
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://dbm-mir.domain.com:6025" can not be reached or does not exist...
I am all out of ideas...
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply