Problem with SQL 2005 Mirror | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Problem with SQL 2005 Mirror

Hi all, I’m having a problem setting up a SQL 2005 Mirror across 2 servers. I’m using a manual failover at the moment so I don’t use a witness server. Server Details: Both have Win Server 2003 + SP1
Both have SQL 2005 running but with different version:
– One is 9.0.2047 (SP1)
– One is 9.0.3033 (SP2) I’ve tested both server connecting via port 5022 with telnet and they connect fine, (should do as well as they are on the same gigabit switch!). Using SQL sa user Auth and I keep getting the following when trying to start it: The Server network address "TCP://192.168.1.44:5022" can not be reached or does not exist. Check the network address name as that the ports for the local and remote endpoints are operational. Any ideas? Ta.
Make sure the defined port is enabled on other server and try with client alias defintion Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.
I don’t know what "client alias definition" is? I tested the port 5022 on both servers and they connect to each other. Also check port via cmd: netstat -ab and it showed SQL Server process with 5022 TCP open.
I think Satya wants you to create an Alias in SQL SERVER CONFIGURATION MANAGER/SQL Client Configuration Mohammed U.
I’m connecting the servers via the "sa" user which should be ok as it does have full database access.
OK, I think I know what the problem is now, it’s the "Service Accounts" as they arn’t configured. Turns out that the service account on each SQL instance didn’t have CONNECT permissions to the endpoint on the other instance. I haven’t used the Service Accounts section so what do I configure there? Let’s say Principal Server is "SATURN" and Mirror is "MARS". I presume I have to setup an NT account on both servers like "MirrorService" which is configured in SQL 2005 security with CONNECT permissions. I’m only guessing here but this is the problem. Got this from MS MSDN forums, ref: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1083613&SiteID=1 Look at the last post.
The problem with the above is the fact that the 2 SQL 2005 Servers I have arn’t on a domain so how can I setup the "Service Accounts" so they can connect to each other?
Create an account with same name and password then try to connect each other from one of the server. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.
try to follow these steps , just remove the witness server line step
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=17295 AKTHAR
Hi Akthar, As I said, the 2 servers are not on a domain so they can’t connect to each other. I’ve come the conclusion that it’s not going to work unless they are on a domain so I’ll have 2 configure that when possible. Thanks anyway.
If the domains are TRUSTED to each other then with the WINS and Client alias they can be connected. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
]]>

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |