I had been trying to solve this error with no success :
One or more of the server network addresses lacks a fully qualified domain name (FQDN). Specify the FQDN for each server, and click Start Mirroring again.
The syntax for a fully-qualified TCP address is:
I had installed three instances on my local machine to test Data base mirroring :
Principal : running SQL Developer Instance
Mirror : running SQL Developer Instance .
Witness : Running SQL Express.
Database mirroring already enabled using startup flag : -T1400
i even tried to configure it with out a witness but still have the same error .
I used the follwoing server name in the mirroring wizard(not localhost) :
Principal : TCP://Ali-laptop:5022
Mirrored : TCP://Ali-laptop:5023
Witness : TCP://Ali-laptop:5044
whats the problem guys?!
Hmmm. The wizard seems to suck a bit. It only handles one scenario, with all machine participating in a domain. Change the machine names to IP addresses of the machines. So it will read "TCP://192.168.0.8:5022 or what ever your IP and ports are set to. I also had to use certificates to get it to work in my instances (high safety and availability). Two must reads from MS on this are "Achieve High Availability for SQL server" and "Using Certificates for Database Mirroring" These are the ONLY two MS articles that will address certificates. They are not complete and you still need more info. "Database Mirroring in SQL Server 2005" is also a required document to get it working, but they do not address a setup correctly if you want High safety and availability. The first two docs I mentioned take precidence and then the information they lack, you have to backfill with the third.
I ended up with a thirty page how to guide for my scenario when I finally got it working. Hte trick was really the swapping f the machine names with the IPs. That did the trick for me.
Sorry about the lack of links to the MS docs. The doc names are vebatum so you can esily search for them. Sorry there is no easy answer either. MS needs some serious work on the wizard at the moment, but it is a decent first stab at it. The mirroring works great once it is established. I would recommend it in opposition to other methods. Setup is painfull however.
thanks for all replies ,but this is really frustrating ,i follow ALL instruction to apply one of the NEWEST technologies MS boasts ,step by step ,i restored the mirror in no recovery mode ,stupid wizard always taking me back to the same place ,my server naming has a problem! ,i changed my server name to be :localhost so the wizard can capture :
still getting the same misleading error ,i was NOT able to change my machine name to an IP address as windows XP doesnt allow special characters in a machine name ,i am starting to think by default the stupid wizard of MS assumes that you are a part of a DOMAIN and expects to see the domain name as a part of your server name .
I wonder why they design wizards if one has to go eventually to scripts?!!
will let you guys know if i have further updates!
I have had the same problem, but it solved
I have a stand alone SQL Server 2005, without member of any domain. I put "local" to the "Primary DNS Suffix of this computer" textbox, then I specified my server as MyServer.local
Then it worked. Try this please. If it will not be working for you, then you have a problem of something else.
I tried to set up on my local machine with 3 instances this option. I got the same error message. I just got the idea to set up my computer to avoid this error like this:
- Right click on the "My Computer" then properties.
- Click on the "computer name" tab, then click on the change button next to the "To Rename this computer or join a domain, click change"
- then you see the "Computer name changes" window, click the "More" button on it.
- You will see the "DNS suffix and NetBIOS ComputerName" window. Here, type "local" to the "Primary DNS Suffix of this Computer" textbox.
- then press OK 3 times and restart computer.
After put this "computername.local" to your computer name for the mirroring computer server network address.
- Proposed as answer by Janos Berke Thursday, June 03, 2010 2:12 PM
if the wizard failes the t-sql always works. Just run these lines:
ALTERDATABASE yourDB SET PARTNER = 'TCP://original_server:5022'
--in original serverALTER DATABASE yourDB SET PARTNER = 'TCP://mirror_server:5022'
ALTERDATABASE yourDB SET WITNESS = 'TCP://witness_server:5022'
where 5022 is the port you stated in wizard. If you want to do everything manually (starting from the endpoints) then heres the commands and info:
We are not require to script to change the server name instead ip address. while you configure mirror thru wizard you need to mention all the information as per the system configuration at the end of the wizard configuration (ie, after clicking finish button) it will as you whether you are starting mirron now or not. click not now then 2 textbox having your server names with be enable for editing.
please contact me if you have any doubt.
I configured mirroring with GUI. When I'm pressing START MIRRORING I got this message:
"One or more of the server network addresses lacks a FQDN. Specify the FQDN for each server and click Start Mirroring"
Both servers are in separate locations with no active directory domain (just WORKGROUP), I made changes in hosts file, both servers runs under the same accont with the same password, I can ping servers by host and IP number. Just mirroring doesn't want to start. Both servers are updated including SP3. I did even DNS sufix trick - no help. I can telnet of 5022 ports.
I was curious and done this on db2 server:
ALTER DATABASE [db] SET PARTNER = 'TCP://db2:5022'
and I got this:
The server network address "TCP://db2: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.
Anyone can help me with it?
This problem that you can solved by set the dns suffix .
The SQL database mirroring need the dns suffix to concate server name to FQDN.
1. Open the server's properties window then click the [change] button
2. Click [More] button
3. Input the [Primary DNS suffix of this computer]
4. Click [OK]
When you change this setting, the win server need to restart.
it is a good post here.
however, by changing Primary DNS suffix does not help for problems.
my case is I use two standalone SQL2005 servers (SP2), I tried to change the Primary DNS suffix on both DB servers, but it doesn't work anymore.
any experts who can post a T-SQL example?