November 17, 2016 at 5:32 am
We are receiving the below Error message in Mirroring and principal server is failovering automatically to Mirror Server.
Database mirroring connection error 4 'The connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)''
Database mirroring connection error 4 '10054(An existing connection was forcibly closed by the remote host.)'.
Database mirroring connection error 2 'Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.'
I have verified telnet to mirroring ports which is working from both sides.
Any thoughts?
November 17, 2016 at 8:29 am
DBA_007 (11/17/2016)
We are receiving the below Error message in Mirroring and principal server is failovering automatically to Mirror Server.Database mirroring connection error 4 'The connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)''
Database mirroring connection error 4 '10054(An existing connection was forcibly closed by the remote host.)'.
Database mirroring connection error 2 'Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.'
I have verified telnet to mirroring ports which is working from both sides.
Any thoughts?
answers to here
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 20, 2016 at 10:05 pm
This was removed by the editor as SPAM
November 21, 2016 at 6:31 am
Tracert gives me output less than 1ms.
December 7, 2016 at 8:41 am
The solution provided by MS for SQL 2016 SP1 Standard Edition running on Windows Server 2012 R2 Enterprise Edition was
Make the following changes on both the principal and mirror server, and then restart the SQL services.
Create / Update the Registry key
•[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL13.<InstanceName>\MSSQLServer\ServiceBroker]
Create / Update the following in the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL13.<InstanceName>\MSSQLServer\ServiceBroker]
•IdleConnectionTimeoutREG_SZ300
You will most likely have to create the ServiceBroker key.
Replace <Instancename> as required. You may have to make this change for each instance if the server hosts multiple instances
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply