Question

Pawan Rajput on Mon, 04 Feb 2013 10:45:30


HI All,

we are facing problem in database mirroring in single database. when i try to establish mirroring it's gives me below mrntion error. 

Communications to the remote server instance 'TCP://####.ABC.NET:5022' failed before database mirroring was fully started. The ALTER DATABASE command failed. Retry the command when the remote database is started.

Currently we mirrored aprox 20 database  but this single database make problem.

we are using sql server 2008 R2 (RTM) enterprise edition.

Please help me to fix this issue.


Thanks


Sponsored



Replies

Joel Engineer on Mon, 04 Feb 2013 10:51:08


Try stopping the SQL Server and restarting.  There may be an existing connnection.  The credentials may be different in the user account on the server or in the dattabase that is preventing the user from account to enable mirrowing.  Make sure you are using an admin account in both the login to the server and the SQL server.

Pawan Rajput on Mon, 04 Feb 2013 10:59:44


thanks for your quick response

which server i need to restart sql server services. currently we using sysadmin login on both the server so there is no issue with right.please let me know if we can do anything else.


Joel Engineer on Mon, 04 Feb 2013 11:08:44


I never assume anything!!!  Even though you are using an sysadmin login the accounts may be set up different on two computers. Also the Group Polies may be different on the two computers.  The SQL server also has a seperate set of credentials from the login account that may not be set up properly.  the SQL Service can be stopped and started from the SQL Server Manager which is an application you can access from the START - Programs menu.

Pawan Rajput on Mon, 04 Feb 2013 12:18:35


i check the login it's same on both server. I think problem not with login we need see other aspect as well, becuse currently we mirrored 20 number of databases no one have problem only this single database given this error. i know how to restart sql server service but i want to know on which server principal or mirror server.

Reed Kimble on Mon, 04 Feb 2013 16:39:24


I don't see where this has anything to do with VB.Net... moving to SQL forum.

Fanny Liu on Tue, 05 Feb 2013 07:38:28


i check the login it's same on both server. I think problem not with login we need see other aspect as well, becuse currently we mirrored 20 number of databases no one have problem only this single database given this error. i know how to restart sql server service but i want to know on which server principal or mirror server.

Thanks

Hello,

Please restart the mirror server. If the issue presists, you can review the error log on the mirror server for detail information and find the root cause.

Regards,

Fanny Liu

Rama Udaya on Wed, 06 Feb 2013 02:10:52


Although its for 2005, but it still gives some hints-

http://support.microsoft.com/kb/947462

PrinceLucifer on Mon, 11 Feb 2013 06:43:30


Two things you can check:

1) Telnet to the mirroring endpoint from both sides

2) If telnet works check permissions on mirroring endpoint

Pawan Rajput on Mon, 11 Feb 2013 17:21:43


Hi Princel,

i already specify database mirror already running for other databases so there is no need for check telnet
i given connect permission on endpoint.
 please let me know if i have to do anything else. 

Joel Engineer on Mon, 11 Feb 2013 17:45:46


There are log files in the c:\Program Files\SQL Server 2008 folder.  I would check to see if there are additional info in the log files that may give a clue.  I suspect one of two things that are causing the problem

1) There is a permission issue with the account you are using to allow the "ALTER DATABASE" command to complete.  Not sure which end of the mirroring is causing the issue.  Make sure you check the log file on both Servers.

2) YOu have a firewall that is blocking the port number that the SQL Server is using to link the two servers.  Possible that there is no route between the two servers.  Try using PING to make sure the two PCs can communicate.  I always recommend trying PING on both servers because I have seen cases where PING works in one direction and not in the other direction.