August 12, 2012 at 8:04 am
We are seeing the following error message when we are trying to reconfigure mirroring. We backed up the principal database, restored it on the mirrored server with norecovery option. Still seeing the following error.
End points on both principal server and mirror server is started:
"The server network address "TCP://TESTSERVER.test:1425" cannot be reached or does not exists".
August 12, 2012 at 8:14 am
We have noticed the following error in SQL Server error logs:
The Database Mirroring protocol transport could not listen for connections due to the following error: '10013(An attempt was made to access a socket in a way forbidden by its access permissions.)'.
When we tried to research on the following error code, it has a particular permission issue which Microsoft talks about:
Windows sockets error codes, values, and meanings: http://support.microsoft.com/kb/819124
WSAEACCES (10013)
Translation: Permission denied.
Description: An attempt was made to access a socket in a way that is forbidden by its access permissions. For example, this error occurs when a broadcast address is used for sendto but the broadcast permission is not set by using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind (Wsapiref_6vzm.asp) function is called (in Microsoft Windows NT 4 .0 Service Pack 4 [SP4] or later), another program, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 SP4 and later, and it is implemented by using the SO_EXCLUSIVEADDRUSE option.
August 12, 2012 at 11:31 pm
Hi,
Please check the ports are open from Primary to Mirror & Mirror to Primary serves.
Use Telnet & find.
Thanks
Satish
August 17, 2012 at 1:59 am
ports were open.
We restarted the mirroring endpoints and the issue got fixed.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply