October 9, 2008 at 1:56 am
Hi to all,
i'm a junior dba and i have a problem with implementing a database mirroring.
In a unique server with o.s. Windows 2003 R2 and out of domain, i have installed 3 instances of SQL Server 2005 Standard Edition SP2, called "Principal" (port 5022), "Mirror" (port 5023) e "Witness" (port 5024).
First:
- instances uses the same service account and, by SQL Server Management Studio, i enter with "Windows Authentication" and "SQL Server Authentication" (with user "sa").
- firewall is disabled
- for all 3 instances TCP/IP and Named Pipes are enabled
In attach you can find all steps that i execute, with error at step number 12.
Could you help me, please?
Many thanks to all and have a good day.
Marco
October 9, 2008 at 2:47 am
Try using full-qualified Tcp address.
instead of
TCP://MYSERVER:5023
try
TCP://MYSERVER.yourdomain.com:5023
October 9, 2008 at 2:57 am
Hi steveb,
my server is not in a domain...
October 9, 2008 at 6:13 am
Okay, check the error log of the failed sever and this should give you more of a clue on what is going on
October 9, 2008 at 7:29 am
Event viewer shows me this message:
"
Database mirroring has benn terminated for database "MyDB".
This is an informational message only. No user action is required
"
Nothing other...
October 9, 2008 at 7:41 am
can you use this to solve the problem ?
http://www.sqlservercentral.com/scripts/Maintenance+and+Management/31867/
and / or
did you read my adventures with SSB ?
http://www.sqlservercentral.com/articles/Service+Broker/2897/
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 9, 2008 at 7:50 am
Now i try and read your adventure 😉
Thanks
October 9, 2008 at 9:07 am
Nothing, i don't resolve it, same message error:
"Network address TCP://MYSERVER:5023 cannot be reached"
:crazy:
October 9, 2008 at 12:55 pm
You could try using the IP address, ALTER DATABASE MyDB SET PARTNER = N'TCP://127.0.0.1:5022';
October 10, 2008 at 12:03 am
- are you able to telnet Mirror 5023 ?
- logon to the server using the service account, and then try to telnet the port.
- logon to the server using the service account, and then try to connect to the instance using TCPIP !
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 10, 2008 at 7:40 am
Nothing, it doesn't function.
But Mirror "speak" with Principal, but Principal doesn't speak with Mirror.
October 10, 2008 at 7:41 am
Yes, telnet functions with port 5022, 5023, 5024, it's strange...
Now i try other your ideas, thanks;)
October 14, 2008 at 10:50 am
ALZDBA (10/10/2008)
- are you able to telnet Mirror 5023 ?- logon to the server using the service account, and then try to telnet the port.
- logon to the server using the service account, and then try to connect to the instance using TCPIP !
All tests are correct, but problem remains...:doze:
October 14, 2008 at 11:27 pm
Firstly, check your ip connectivity between the servers. If you have connectivity issues you may need to update the hosts file with the ip addresses of the other servers.
Secondly, all endpoints in the mirroring topology should talk on the same port numbers. Re-create your endpoints using the same port and then the servers should be able to talk to each other.
Don't worry about using the IP address, contrary to everything the documentation and assorted blogs tell you, the only difference is that you can't start mirroring via the GUI. Using ordinary T-SQL commands works without any problems at all.
--------------------
Colt 45 - the original point and click interface
October 15, 2008 at 6:12 am
philcart (10/14/2008)
Firstly, check your ip connectivity between the servers. If you have connectivity issues you may need to update the hosts file with the ip addresses of the other servers.Secondly, all endpoints in the mirroring topology should talk on the same port numbers. Re-create your endpoints using the same port and then the servers should be able to talk to each other.
Don't worry about using the IP address, contrary to everything the documentation and assorted blogs tell you, the only difference is that you can't start mirroring via the GUI. Using ordinary T-SQL commands works without any problems at all.
Hi philcart,
i have only one server, in this server i have 3 istances, so it's mandatory has 3 different ports, and when i create enpoints i must write 3 distinct ports specified in Configuration Manager.
When i set role with Principal (from Mirror), it's ok, but when set roles with Mirror and Witness (from Principal), i receive this error:
Network address TCP://MYSERVER:5023 cannot be reached
Now i want try to associate "network_service" to administrator group.
Viewing 15 posts - 1 through 15 (of 31 total)
You must be logged in to reply to this topic. Login to reply