July 1, 2009 at 7:59 am
Hi all,
I have two sql server 2008. One principal and the other the mirror. I have not witness. Both are in the same domain and installed using domain user service account on both. The two servers are exactly identical.
I used the following script to to setup mirroring.
-- Change the recovary model to full.
USE [master]
GO
ALTER DATABASE [myDB] SET RECOVERY FULL WITH NO_WAIT
GO
-- Create a full backup of the database
USE myDB
GO
BACKUP DATABASE myDB
TO DISK = N'E:\backup\myDBDATA\myDB.bak' WITH NOFORMAT, INIT
GO
-- Create a transaction log backup
BACKUP LOG [myDB] TO DISK = N'E:\backup\myDBDATA\myDB.trn' WITH NOFORMAT, INIT
GO
On the Mirror server
RESTORE DATABASE [myDB]
from disk = '\\Server_1\E$\Backup\myDBDATA\myDB.bak'
WITH NORECOVERY, REPLACE
RESTORE LOG [myDB]
FROM DISK = '\\Server_1\E$\Backup\myDBDATA\myDB.trn'
WITH NORECOVERY
On the principal
CREATE ENDPOINT Mirroring
STATE = STARTED
AS TCP (LISTENER_PORT = 5022)
FOR DATABASE_MIRRORING (ROLE = PARTNER)
GO
On the mirror
CREATE ENDPOINT Mirroring
STATE = STARTED
AS TCP (LISTENER_PORT = 5022)
FOR DATABASE_MIRRORING (ROLE = ALL)
GO
ALTER DATABASE myDB
SET PARTNER = 'TCP://Server_1.xxx-ge.net:5022'
GO
The following step fails with the following error
On the principal
ALTER DATABASE myDB
SET PARTNER = 'TCP://Server_2.xxx-ge.net:5022'
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://PDIESS01SQ0012.POLIZEI-BW.DE:5022" 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.
Please I appreciate if you could give me a hint on how to solve this problem.
July 1, 2009 at 9:08 am
Port 5022 is blocked on the principal or mirror server.
Do a netstat -a to see if anything else is using it.
Unblock 5022 in your firewall http://support.microsoft.com/kb/842242
Troubleshooting Mirroring
http://technet.microsoft.com/en-us/library/ms189127.aspx
Error 1418
http://technet.microsoft.com/en-us/library/aa337361.aspx
July 1, 2009 at 9:14 am
I'd got similar issue once and resolved it by changing the authentication mode to windows negotiate.
See if that works for you case.
July 10, 2009 at 3:36 am
Hello,
I also got the same i.e.
The server network address "TCP://indserver.****.local:5022" can not be reached or does not exist. Check the network address name and reissue the command. (Microsoft SQL Server, Error: 1418)
even not working with the available solution
is any other solution?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply