Mirroring - server network address cannot be reached or does not exist
up vote
8
down vote
favorite
I have read a number of articles on how to configure mirroring on SQL Server 2012. I went through the steps and everything worked until hitting the final step, which didn't work.
When I run this on the Principal:
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4:5022';
I get this error:
The server network address "TCP://1.2.3.4:5022" can not be
reached or does not exist.
When I run the counterpart ALTER statement shown above, but on the Mirror, it works fine.
I have tried all the steps in this troubleshooting article.
Important points:
- The Primary and Mirror servers are in different datacenters, not on the same network at all. Not connected by VPN. Completely untrusted by each other.
- I can connect to the Mirror via SSMS on the Primary and run queries. And vice versa.
- I configured certificates on each server to establish the trust relationship. Everything worked during the setup and config, no errors.
- I configured the endpoints on both servers and verified they're active/enabled.
- I opened port 5022 on both servers by configuring incoming and outgoing windows firewall rules. I can telnet to the Mirror from the Principal and vice versa - ports appear open, no problems.
- In the troubleshooting guide mentioned above, I tried steps 1-6. I didn't try 7, deleting the endpoints and re-creating, because they look perfectly valid and active to me.
Looking for some ideas on this one.
sql-server sql-server-2012 edited Feb 10 '14 at 16:17
Neolisk
20k956110
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
add a comment |
up vote
8
down vote
favorite
I have read a number of articles on how to configure mirroring on SQL Server 2012. I went through the steps and everything worked until hitting the final step, which didn't work.
When I run this on the Principal:
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4:5022';
I get this error:
The server network address "TCP://1.2.3.4:5022" can not be
reached or does not exist.
When I run the counterpart ALTER statement shown above, but on the Mirror, it works fine.
I have tried all the steps in this troubleshooting article.
Important points:
- The Primary and Mirror servers are in different datacenters, not on the same network at all. Not connected by VPN. Completely untrusted by each other.
- I can connect to the Mirror via SSMS on the Primary and run queries. And vice versa.
- I configured certificates on each server to establish the trust relationship. Everything worked during the setup and config, no errors.
- I configured the endpoints on both servers and verified they're active/enabled.
- I opened port 5022 on both servers by configuring incoming and outgoing windows firewall rules. I can telnet to the Mirror from the Principal and vice versa - ports appear open, no problems.
- In the troubleshooting guide mentioned above, I tried steps 1-6. I didn't try 7, deleting the endpoints and re-creating, because they look perfectly valid and active to me.
Looking for some ideas on this one.
sql-server sql-server-2012 edited Feb 10 '14 at 16:17
Neolisk
20k956110
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
1
Did you try to disable Windows Firewall on both machines and then try? I've had a couple of times that, although I had (IMHO correct) rules configured for MSSQL, the firewall somehow blocked in or outgoing connections. Doing this test would at least allow you to either know if its the firewall or not so you can rule that out.
– deroby
Feb 11 '14 at 10:02
@deroby: I just tried turning the firewall completely off on both servers. No difference. Same error.
– HerrimanCoder
Feb 11 '14 at 22:22
@HerrimanCoder: Did you resolve this issue. I know this is an old post. But now I have run into a similar one, and can't find a solution. What was your solution if you have resolved this.
– user726720
Nov 1 '17 at 12:41
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
I have read a number of articles on how to configure mirroring on SQL Server 2012. I went through the steps and everything worked until hitting the final step, which didn't work.
When I run this on the Principal:
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4:5022';
I get this error:
The server network address "TCP://1.2.3.4:5022" can not be
reached or does not exist.
When I run the counterpart ALTER statement shown above, but on the Mirror, it works fine.
I have tried all the steps in this troubleshooting article.
Important points:
- The Primary and Mirror servers are in different datacenters, not on the same network at all. Not connected by VPN. Completely untrusted by each other.
- I can connect to the Mirror via SSMS on the Primary and run queries. And vice versa.
- I configured certificates on each server to establish the trust relationship. Everything worked during the setup and config, no errors.
- I configured the endpoints on both servers and verified they're active/enabled.
- I opened port 5022 on both servers by configuring incoming and outgoing windows firewall rules. I can telnet to the Mirror from the Principal and vice versa - ports appear open, no problems.
- In the troubleshooting guide mentioned above, I tried steps 1-6. I didn't try 7, deleting the endpoints and re-creating, because they look perfectly valid and active to me.
Looking for some ideas on this one.
sql-server sql-server-2012 edited Feb 10 '14 at 16:17
Neolisk
20k956110
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
I have read a number of articles on how to configure mirroring on SQL Server 2012. I went through the steps and everything worked until hitting the final step, which didn't work.
When I run this on the Principal:
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4:5022';
I get this error:
The server network address "TCP://1.2.3.4:5022" can not be
reached or does not exist.
When I run the counterpart ALTER statement shown above, but on the Mirror, it works fine.
I have tried all the steps in this troubleshooting article.
Important points:
- The Primary and Mirror servers are in different datacenters, not on the same network at all. Not connected by VPN. Completely untrusted by each other.
- I can connect to the Mirror via SSMS on the Primary and run queries. And vice versa.
- I configured certificates on each server to establish the trust relationship. Everything worked during the setup and config, no errors.
- I configured the endpoints on both servers and verified they're active/enabled.
- I opened port 5022 on both servers by configuring incoming and outgoing windows firewall rules. I can telnet to the Mirror from the Principal and vice versa - ports appear open, no problems.
- In the troubleshooting guide mentioned above, I tried steps 1-6. I didn't try 7, deleting the endpoints and re-creating, because they look perfectly valid and active to me.
Looking for some ideas on this one.
sql-server sql-server-2012 sql-server sql-server-2012 edited Feb 10 '14 at 16:17
Neolisk
20k956110
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
edited Feb 10 '14 at 16:17
Neolisk
20k956110
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
edited Feb 10 '14 at 16:17
Neolisk
20k956110
edited Feb 10 '14 at 16:17
Neolisk
20k956110
edited Feb 10 '14 at 16:17
Neolisk
20k956110
20k956110
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
asked Feb 6 '14 at 0:55
HerrimanCoder
1,446144480
1,446144480
1
Did you try to disable Windows Firewall on both machines and then try? I've had a couple of times that, although I had (IMHO correct) rules configured for MSSQL, the firewall somehow blocked in or outgoing connections. Doing this test would at least allow you to either know if its the firewall or not so you can rule that out.
– deroby
Feb 11 '14 at 10:02
@deroby: I just tried turning the firewall completely off on both servers. No difference. Same error.
– HerrimanCoder
Feb 11 '14 at 22:22
@HerrimanCoder: Did you resolve this issue. I know this is an old post. But now I have run into a similar one, and can't find a solution. What was your solution if you have resolved this.
– user726720
Nov 1 '17 at 12:41
add a comment |
1
Did you try to disable Windows Firewall on both machines and then try? I've had a couple of times that, although I had (IMHO correct) rules configured for MSSQL, the firewall somehow blocked in or outgoing connections. Doing this test would at least allow you to either know if its the firewall or not so you can rule that out.
– deroby
Feb 11 '14 at 10:02
@deroby: I just tried turning the firewall completely off on both servers. No difference. Same error.
– HerrimanCoder
Feb 11 '14 at 22:22
@HerrimanCoder: Did you resolve this issue. I know this is an old post. But now I have run into a similar one, and can't find a solution. What was your solution if you have resolved this.
– user726720
Nov 1 '17 at 12:41
1
1
Did you try to disable Windows Firewall on both machines and then try? I've had a couple of times that, although I had (IMHO correct) rules configured for MSSQL, the firewall somehow blocked in or outgoing connections. Doing this test would at least allow you to either know if its the firewall or not so you can rule that out.
– deroby
Feb 11 '14 at 10:02
Did you try to disable Windows Firewall on both machines and then try? I've had a couple of times that, although I had (IMHO correct) rules configured for MSSQL, the firewall somehow blocked in or outgoing connections. Doing this test would at least allow you to either know if its the firewall or not so you can rule that out.
– deroby
Feb 11 '14 at 10:02
@deroby: I just tried turning the firewall completely off on both servers. No difference. Same error.
– HerrimanCoder
Feb 11 '14 at 22:22
@deroby: I just tried turning the firewall completely off on both servers. No difference. Same error.
– HerrimanCoder
Feb 11 '14 at 22:22
@HerrimanCoder: Did you resolve this issue. I know this is an old post. But now I have run into a similar one, and can't find a solution. What was your solution if you have resolved this.
– user726720
Nov 1 '17 at 12:41
@HerrimanCoder: Did you resolve this issue. I know this is an old post. But now I have run into a similar one, and can't find a solution. What was your solution if you have resolved this.
– user726720
Nov 1 '17 at 12:41
add a comment |
4 Answers
4
active
oldest
votes
up vote
0
down vote
If you can telnet that port from the principal machine everything is fine with TCP/IP and firewall settings.
I can remember that I had a similar issue in the past. Unfortunatly I dont remember the exact solution but it was related to security/authentication of the endpoints and the SQL Server service account not having enough permission on the mirror machine. Unfortunatly the error message is pretty misleading in this case. Script the endpoints and verify their settings, SSMS has no UI for that.
Another thing that you could check is that you have the possibility to also connect to port 5022 from the mirror to the principal machine. You will get the same error message if the connection is not possible from both instances.
Sorry that I cant provide you a proper solution, but maybe that points you to the right direction.
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
I can connect from mirror to principal 5022. I can telnet to the port from each machine. What permissions should I grant SQL Server service?
– HerrimanCoder
Feb 13 '14 at 18:05
Per default only users having sysadmin role on the local machine are able to connect to Endpoints. In my case I was on the same domain, but that is not applicable to your scenario. You have to make sure the Endpoint is created specifying your certificate as authorisation, a login is created and assigned to that certificate and finally the login is granted permission to that Endpoint. see this link
– m0n0ph0n
Feb 14 '14 at 10:45
add a comment |
up vote
0
down vote
Unfortunately there are quite non-informative error messages in MS SQL. The problem might be an authorization issue and the server still will be saying "network address can not be reached".
Considering "servers are in different datacenters", how the authentication is performed? A MSSQL service (on server1) itself must be runned as a valid db user (on server2, and vice versa) in order to make the mirroring work.
answered Feb 17 '14 at 16:16
enkryptor
91311018
Yes, I have set it up that way.
– HerrimanCoder
Feb 17 '14 at 16:53
As mentioned in original post, I'm using certificates for authentication, which is what MS suggests to do.
– HerrimanCoder
Feb 17 '14 at 19:57
add a comment |
up vote
0
down vote
There can be multiple reasons for this to happen.
In your SQL Server Management Studio, if you see a White bubble next to the server instance name, instead of the Green bubble, then you can try the following:
- "Allow an app through firewall" and add "Windows Management Instrumentation (WMI)" for Windows Server 2012. If it is Windows Server 2008, you can allow "Remote Administration" through firewall.
answered May 18 '16 at 6:16
Sudheer
264
add a comment |
up vote
-1
down vote
Is it meant to be a semi colon?
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4;5022'
The semi colon is used when connecting to IP / Port when using management studio.
answered Feb 10 '14 at 16:20
user1948635
5543918
The semicolon is invalid syntax for that command. "ALTER DATABASE command failed due to an invalid server connection string." The colon is correct, and that's how MS documents to do it. In fact the statement works successfully on the Mirror, just not on the principal. They're both MSSQL 2012.
– HerrimanCoder
Feb 10 '14 at 21:14
Ah ok, apologies. Thought it might be worth a try as thats how SSMS connections to IP/port work. Best of luck resolving the issue.
– user1948635
Feb 11 '14 at 0:22
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
If you can telnet that port from the principal machine everything is fine with TCP/IP and firewall settings.
I can remember that I had a similar issue in the past. Unfortunatly I dont remember the exact solution but it was related to security/authentication of the endpoints and the SQL Server service account not having enough permission on the mirror machine. Unfortunatly the error message is pretty misleading in this case. Script the endpoints and verify their settings, SSMS has no UI for that.
Another thing that you could check is that you have the possibility to also connect to port 5022 from the mirror to the principal machine. You will get the same error message if the connection is not possible from both instances.
Sorry that I cant provide you a proper solution, but maybe that points you to the right direction.
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
I can connect from mirror to principal 5022. I can telnet to the port from each machine. What permissions should I grant SQL Server service?
– HerrimanCoder
Feb 13 '14 at 18:05
Per default only users having sysadmin role on the local machine are able to connect to Endpoints. In my case I was on the same domain, but that is not applicable to your scenario. You have to make sure the Endpoint is created specifying your certificate as authorisation, a login is created and assigned to that certificate and finally the login is granted permission to that Endpoint. see this link
– m0n0ph0n
Feb 14 '14 at 10:45
add a comment |
up vote
0
down vote
If you can telnet that port from the principal machine everything is fine with TCP/IP and firewall settings.
I can remember that I had a similar issue in the past. Unfortunatly I dont remember the exact solution but it was related to security/authentication of the endpoints and the SQL Server service account not having enough permission on the mirror machine. Unfortunatly the error message is pretty misleading in this case. Script the endpoints and verify their settings, SSMS has no UI for that.
Another thing that you could check is that you have the possibility to also connect to port 5022 from the mirror to the principal machine. You will get the same error message if the connection is not possible from both instances.
Sorry that I cant provide you a proper solution, but maybe that points you to the right direction.
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
I can connect from mirror to principal 5022. I can telnet to the port from each machine. What permissions should I grant SQL Server service?
– HerrimanCoder
Feb 13 '14 at 18:05
Per default only users having sysadmin role on the local machine are able to connect to Endpoints. In my case I was on the same domain, but that is not applicable to your scenario. You have to make sure the Endpoint is created specifying your certificate as authorisation, a login is created and assigned to that certificate and finally the login is granted permission to that Endpoint. see this link
– m0n0ph0n
Feb 14 '14 at 10:45
add a comment |
up vote
0
down vote
up vote
0
down vote
If you can telnet that port from the principal machine everything is fine with TCP/IP and firewall settings.
I can remember that I had a similar issue in the past. Unfortunatly I dont remember the exact solution but it was related to security/authentication of the endpoints and the SQL Server service account not having enough permission on the mirror machine. Unfortunatly the error message is pretty misleading in this case. Script the endpoints and verify their settings, SSMS has no UI for that.
Another thing that you could check is that you have the possibility to also connect to port 5022 from the mirror to the principal machine. You will get the same error message if the connection is not possible from both instances.
Sorry that I cant provide you a proper solution, but maybe that points you to the right direction.
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
If you can telnet that port from the principal machine everything is fine with TCP/IP and firewall settings.
I can remember that I had a similar issue in the past. Unfortunatly I dont remember the exact solution but it was related to security/authentication of the endpoints and the SQL Server service account not having enough permission on the mirror machine. Unfortunatly the error message is pretty misleading in this case. Script the endpoints and verify their settings, SSMS has no UI for that.
Another thing that you could check is that you have the possibility to also connect to port 5022 from the mirror to the principal machine. You will get the same error message if the connection is not possible from both instances.
Sorry that I cant provide you a proper solution, but maybe that points you to the right direction.
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
answered Feb 13 '14 at 13:27
m0n0ph0n
1494
1494
I can connect from mirror to principal 5022. I can telnet to the port from each machine. What permissions should I grant SQL Server service?
– HerrimanCoder
Feb 13 '14 at 18:05
Per default only users having sysadmin role on the local machine are able to connect to Endpoints. In my case I was on the same domain, but that is not applicable to your scenario. You have to make sure the Endpoint is created specifying your certificate as authorisation, a login is created and assigned to that certificate and finally the login is granted permission to that Endpoint. see this link
– m0n0ph0n
Feb 14 '14 at 10:45
add a comment |
I can connect from mirror to principal 5022. I can telnet to the port from each machine. What permissions should I grant SQL Server service?
– HerrimanCoder
Feb 13 '14 at 18:05
Per default only users having sysadmin role on the local machine are able to connect to Endpoints. In my case I was on the same domain, but that is not applicable to your scenario. You have to make sure the Endpoint is created specifying your certificate as authorisation, a login is created and assigned to that certificate and finally the login is granted permission to that Endpoint. see this link
– m0n0ph0n
Feb 14 '14 at 10:45
I can connect from mirror to principal 5022. I can telnet to the port from each machine. What permissions should I grant SQL Server service?
– HerrimanCoder
Feb 13 '14 at 18:05
I can connect from mirror to principal 5022. I can telnet to the port from each machine. What permissions should I grant SQL Server service?
– HerrimanCoder
Feb 13 '14 at 18:05
Per default only users having sysadmin role on the local machine are able to connect to Endpoints. In my case I was on the same domain, but that is not applicable to your scenario. You have to make sure the Endpoint is created specifying your certificate as authorisation, a login is created and assigned to that certificate and finally the login is granted permission to that Endpoint. see this link
– m0n0ph0n
Feb 14 '14 at 10:45
Per default only users having sysadmin role on the local machine are able to connect to Endpoints. In my case I was on the same domain, but that is not applicable to your scenario. You have to make sure the Endpoint is created specifying your certificate as authorisation, a login is created and assigned to that certificate and finally the login is granted permission to that Endpoint. see this link
– m0n0ph0n
Feb 14 '14 at 10:45
add a comment |
up vote
0
down vote
Unfortunately there are quite non-informative error messages in MS SQL. The problem might be an authorization issue and the server still will be saying "network address can not be reached".
Considering "servers are in different datacenters", how the authentication is performed? A MSSQL service (on server1) itself must be runned as a valid db user (on server2, and vice versa) in order to make the mirroring work.
answered Feb 17 '14 at 16:16
enkryptor
91311018
Yes, I have set it up that way.
– HerrimanCoder
Feb 17 '14 at 16:53
As mentioned in original post, I'm using certificates for authentication, which is what MS suggests to do.
– HerrimanCoder
Feb 17 '14 at 19:57
add a comment |
up vote
0
down vote
Unfortunately there are quite non-informative error messages in MS SQL. The problem might be an authorization issue and the server still will be saying "network address can not be reached".
Considering "servers are in different datacenters", how the authentication is performed? A MSSQL service (on server1) itself must be runned as a valid db user (on server2, and vice versa) in order to make the mirroring work.
answered Feb 17 '14 at 16:16
enkryptor
91311018
Yes, I have set it up that way.
– HerrimanCoder
Feb 17 '14 at 16:53
As mentioned in original post, I'm using certificates for authentication, which is what MS suggests to do.
– HerrimanCoder
Feb 17 '14 at 19:57
add a comment |
up vote
0
down vote
up vote
0
down vote
Unfortunately there are quite non-informative error messages in MS SQL. The problem might be an authorization issue and the server still will be saying "network address can not be reached".
Considering "servers are in different datacenters", how the authentication is performed? A MSSQL service (on server1) itself must be runned as a valid db user (on server2, and vice versa) in order to make the mirroring work.
answered Feb 17 '14 at 16:16
enkryptor
91311018
Unfortunately there are quite non-informative error messages in MS SQL. The problem might be an authorization issue and the server still will be saying "network address can not be reached".
Considering "servers are in different datacenters", how the authentication is performed? A MSSQL service (on server1) itself must be runned as a valid db user (on server2, and vice versa) in order to make the mirroring work.
answered Feb 17 '14 at 16:16
enkryptor
91311018
answered Feb 17 '14 at 16:16
enkryptor
91311018
answered Feb 17 '14 at 16:16
enkryptor
91311018
answered Feb 17 '14 at 16:16
enkryptor
91311018
91311018
Yes, I have set it up that way.
– HerrimanCoder
Feb 17 '14 at 16:53
As mentioned in original post, I'm using certificates for authentication, which is what MS suggests to do.
– HerrimanCoder
Feb 17 '14 at 19:57
add a comment |
Yes, I have set it up that way.
– HerrimanCoder
Feb 17 '14 at 16:53
As mentioned in original post, I'm using certificates for authentication, which is what MS suggests to do.
– HerrimanCoder
Feb 17 '14 at 19:57
Yes, I have set it up that way.
– HerrimanCoder
Feb 17 '14 at 16:53
Yes, I have set it up that way.
– HerrimanCoder
Feb 17 '14 at 16:53
As mentioned in original post, I'm using certificates for authentication, which is what MS suggests to do.
– HerrimanCoder
Feb 17 '14 at 19:57
As mentioned in original post, I'm using certificates for authentication, which is what MS suggests to do.
– HerrimanCoder
Feb 17 '14 at 19:57
add a comment |
up vote
0
down vote
There can be multiple reasons for this to happen.
In your SQL Server Management Studio, if you see a White bubble next to the server instance name, instead of the Green bubble, then you can try the following:
- "Allow an app through firewall" and add "Windows Management Instrumentation (WMI)" for Windows Server 2012. If it is Windows Server 2008, you can allow "Remote Administration" through firewall.
answered May 18 '16 at 6:16
Sudheer
264
add a comment |
up vote
0
down vote
There can be multiple reasons for this to happen.
In your SQL Server Management Studio, if you see a White bubble next to the server instance name, instead of the Green bubble, then you can try the following:
- "Allow an app through firewall" and add "Windows Management Instrumentation (WMI)" for Windows Server 2012. If it is Windows Server 2008, you can allow "Remote Administration" through firewall.
answered May 18 '16 at 6:16
Sudheer
264
add a comment |
up vote
0
down vote
up vote
0
down vote
There can be multiple reasons for this to happen.
In your SQL Server Management Studio, if you see a White bubble next to the server instance name, instead of the Green bubble, then you can try the following:
- "Allow an app through firewall" and add "Windows Management Instrumentation (WMI)" for Windows Server 2012. If it is Windows Server 2008, you can allow "Remote Administration" through firewall.
answered May 18 '16 at 6:16
Sudheer
264
There can be multiple reasons for this to happen.
In your SQL Server Management Studio, if you see a White bubble next to the server instance name, instead of the Green bubble, then you can try the following:
- "Allow an app through firewall" and add "Windows Management Instrumentation (WMI)" for Windows Server 2012. If it is Windows Server 2008, you can allow "Remote Administration" through firewall.
answered May 18 '16 at 6:16
Sudheer
264
answered May 18 '16 at 6:16
Sudheer
264
answered May 18 '16 at 6:16
Sudheer
264
answered May 18 '16 at 6:16
Sudheer
264
264
add a comment |
add a comment |
up vote
-1
down vote
Is it meant to be a semi colon?
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4;5022'
The semi colon is used when connecting to IP / Port when using management studio.
answered Feb 10 '14 at 16:20
user1948635
5543918
The semicolon is invalid syntax for that command. "ALTER DATABASE command failed due to an invalid server connection string." The colon is correct, and that's how MS documents to do it. In fact the statement works successfully on the Mirror, just not on the principal. They're both MSSQL 2012.
– HerrimanCoder
Feb 10 '14 at 21:14
Ah ok, apologies. Thought it might be worth a try as thats how SSMS connections to IP/port work. Best of luck resolving the issue.
– user1948635
Feb 11 '14 at 0:22
add a comment |
up vote
-1
down vote
Is it meant to be a semi colon?
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4;5022'
The semi colon is used when connecting to IP / Port when using management studio.
answered Feb 10 '14 at 16:20
user1948635
5543918
The semicolon is invalid syntax for that command. "ALTER DATABASE command failed due to an invalid server connection string." The colon is correct, and that's how MS documents to do it. In fact the statement works successfully on the Mirror, just not on the principal. They're both MSSQL 2012.
– HerrimanCoder
Feb 10 '14 at 21:14
Ah ok, apologies. Thought it might be worth a try as thats how SSMS connections to IP/port work. Best of luck resolving the issue.
– user1948635
Feb 11 '14 at 0:22
add a comment |
up vote
-1
down vote
up vote
-1
down vote
Is it meant to be a semi colon?
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4;5022'
The semi colon is used when connecting to IP / Port when using management studio.
answered Feb 10 '14 at 16:20
user1948635
5543918
Is it meant to be a semi colon?
ALTER DATABASE MyDBName SET PARTNER = 'TCP://1.2.3.4;5022'
The semi colon is used when connecting to IP / Port when using management studio.
answered Feb 10 '14 at 16:20
user1948635
5543918
answered Feb 10 '14 at 16:20
user1948635
5543918
answered Feb 10 '14 at 16:20
user1948635
5543918
answered Feb 10 '14 at 16:20
user1948635
5543918
5543918
The semicolon is invalid syntax for that command. "ALTER DATABASE command failed due to an invalid server connection string." The colon is correct, and that's how MS documents to do it. In fact the statement works successfully on the Mirror, just not on the principal. They're both MSSQL 2012.
– HerrimanCoder
Feb 10 '14 at 21:14
Ah ok, apologies. Thought it might be worth a try as thats how SSMS connections to IP/port work. Best of luck resolving the issue.
– user1948635
Feb 11 '14 at 0:22
add a comment |
The semicolon is invalid syntax for that command. "ALTER DATABASE command failed due to an invalid server connection string." The colon is correct, and that's how MS documents to do it. In fact the statement works successfully on the Mirror, just not on the principal. They're both MSSQL 2012.
– HerrimanCoder
Feb 10 '14 at 21:14
Ah ok, apologies. Thought it might be worth a try as thats how SSMS connections to IP/port work. Best of luck resolving the issue.
– user1948635
Feb 11 '14 at 0:22
The semicolon is invalid syntax for that command. "ALTER DATABASE command failed due to an invalid server connection string." The colon is correct, and that's how MS documents to do it. In fact the statement works successfully on the Mirror, just not on the principal. They're both MSSQL 2012.
– HerrimanCoder
Feb 10 '14 at 21:14
The semicolon is invalid syntax for that command. "ALTER DATABASE command failed due to an invalid server connection string." The colon is correct, and that's how MS documents to do it. In fact the statement works successfully on the Mirror, just not on the principal. They're both MSSQL 2012.
– HerrimanCoder
Feb 10 '14 at 21:14
Ah ok, apologies. Thought it might be worth a try as thats how SSMS connections to IP/port work. Best of luck resolving the issue.
– user1948635
Feb 11 '14 at 0:22
Ah ok, apologies. Thought it might be worth a try as thats how SSMS connections to IP/port work. Best of luck resolving the issue.
– user1948635
Feb 11 '14 at 0:22
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f21591899%2fmirroring-server-network-address-cannot-be-reached-or-does-not-exist%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Did you try to disable Windows Firewall on both machines and then try? I've had a couple of times that, although I had (IMHO correct) rules configured for MSSQL, the firewall somehow blocked in or outgoing connections. Doing this test would at least allow you to either know if its the firewall or not so you can rule that out.
– deroby
Feb 11 '14 at 10:02
@deroby: I just tried turning the firewall completely off on both servers. No difference. Same error.
– HerrimanCoder
Feb 11 '14 at 22:22
@HerrimanCoder: Did you resolve this issue. I know this is an old post. But now I have run into a similar one, and can't find a solution. What was your solution if you have resolved this.
– user726720
Nov 1 '17 at 12:41