| Author |
Topic |
|
kerrycorcoran
Starting Member
38 Posts |
 Posted - 2008-02-07 : 15:04:08
|
| I am attempting to mirror a SQL database. I ran a full backup of the primary database (RESTORE WITH NORECOVERY) to the mirror server.When I created the mirror (on the primary) server I get the following message:The server network address "TCP://servername: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.The port is not blocked. I can ping both servers from one another. I am using the same SA account on both servers.Any insight?Thanks,Kerry |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
kerrycorcoran
Starting Member
38 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-02-07 : 16:04:06
|
| I've only ever set it up through T-SQL, so I don't have any information about the wizard.You might also try the fully qualified servername instead of just servername. I believe that's what we had to do initially.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
kerrycorcoran
Starting Member
38 Posts |
Posted - 2008-02-07 : 20:38:52
|
quote:
Originally posted by tkizer
I've only ever set it up through T-SQL, so I don't have any information about the wizard.You might also try the fully qualified servername instead of just servername. I believe that's what we had to do initially.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/
That's the crazy thing, I am using a FQDN ??This is driving me nuts. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-07 : 21:30:39
|
| Run 'select @@servername' on target server, what do get? |
|
|
|
kerrycorcoran
Starting Member
38 Posts |
Posted - 2008-02-07 : 22:12:25
|
quote:
Originally posted by rmiao
Run 'select @@servername' on target server, what do get?
Here is my test lab:Primary server - LIUSPC01Mirror server - LIUAPP20I get an error when I run 'select @@LIUAPP20' on LIUAPP20Appreciate all the assistance. Help!!! |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-07 : 23:16:08
|
| No, run 'select @@servername' and it should return LIUAPP20. If not, have to run 'sp_addserver LIUAPP20, local' and restart sql to fix it. |
|
|
|
kerrycorcoran
Starting Member
38 Posts |
Posted - 2008-02-07 : 23:29:29
|
quote:
Originally posted by rmiao
No, run 'select @@servername' and it should return LIUAPP20. If not, have to run 'sp_addserver LIUAPP20, local' and restart sql to fix it.
Yes, it returned LIUAPP20 |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-08 : 01:40:14
|
| Then check LIUSPC01 if it connects to LIUAPP20 with tcp/ip protocol. |
|
|
|
kerrycorcoran
Starting Member
38 Posts |
Posted - 2008-02-09 : 10:21:35
|
quote:
Originally posted by rmiao
Then check LIUSPC01 if it connects to LIUAPP20 with tcp/ip protocol.
I can ping both servers from one another. How else can I verify? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-09 : 13:03:51
|
| Should check that in sql server configuration manager. |
|
|
|
kerrycorcoran
Starting Member
38 Posts |
Posted - 2008-02-09 : 14:10:00
|
quote:
Originally posted by rmiao
Should check that in sql server configuration manager.
Can you elaborate how? Not sure what I am checking, nor how to check it.Thanks,Kerry |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-09 : 19:23:34
|
| There is a sql tool call sql server configuration manager on each sql server, open it and look at sql native client configuration. Create alias if necessary, and books online has details. |
|
|
|
kerrycorcoran
Starting Member
38 Posts |
Posted - 2008-02-09 : 20:05:31
|
| If I can ping the secondary server from the primary server doesn't that verify the IP traffic is working properly? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-09 : 22:47:16
|
| That doesn't mean sql talk each other with tcp/ip protocol. You should get help from your dba if you don't know what we are talking about. |
|
|
|
|
Ahhh!!!!