Search

Database Mirroring GUI does not work and throws FQDN error by Michael Hotek

Closed
as Won't Fix Help for as Won't Fix

1
0
Sign in
 to vote
Type: Bug
ID: 343027
Opened: 5/9/2008 12:01:51 PM
Access Restriction: Public
1
Workaround(s)
0
User(s) can reproduce this bug
I am getting an error within the Database Mirroring GUI about an FQDN that prevents me from using the GUI to configure Database Mirroring. The specific error is:
TITLE: Database Properties
------------------------------

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:
TCP://<computer_name>.<domain_segment>[.<domain_segment>]:<port>

------------------------------
BUTTONS:
OK
------------------------------

The relevant piece of ipconfig \all is:
Windows IP Configuration
        Host Name . . . . . . . . . . . . : hotek
        Primary Dns Suffix . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Principal: TCP://hotek:5022
Mirror: TCP://hotek:5023
Witness: TCP://hotek:5024

Additionally, the fields to specify the server addresses for the principal, mirror, and witness are greyed out and do NOT allow any direct entry. The only way to get an entry into those fields is to use the configure security wizard. This is isolated ONLY to SSMS. Database Mirroring will configure with NO errors by executing the appropriate ALTER DATABASE statements directly. (But it sucks for a demo and when it blows up in front of a couple hundred people, doesn't leave them with a whole lot of confidence that a major HA feature will even work if a simple GUI doesn't even function.)

Version 9.0.3228
Details (expand)
Product Language
English

Version

SQL Server 2005 SP2 - Developer Edition

Category

Tools (SSMS, Agent, Profiler, etc.)

Operating System

Windows XP SP2 Professional
Operating System Language
US English
Steps to Reproduce
1. Launch SSMS
2. Connect to 2 instances in Object Explorer
3. Set recovery model for AdventureWorks to FULL
4. Backup AdventureWorks + 1 TLOG backup
5. Restore backup + tlog to the instance which will be the mirror using NORECOVERY
6. Right click AdventureWorks on the principal and select Properties
7. Click Mirroring tab
8. Notice that all of the server address fields are greyed out
9. Click Configure security and go through the wizard setting/retrieving the endpoints for principal, witness, and mirror
10. At completion of security wizard, click Start Mirroring
Actual Results
1. Throws an error message about an FQDN
2. Does not allow direct specification of server addresses

However, opening a query window and executing the appropriate ALTER DATABASE statement configures Database Mirroring with no errors whatsoever.
Expected Results
Not only does mirroring initiate, but you can also directly specify the server addresses in the GUI.

Platform

32
File Attachments
File Name Submitted By Submitted On File Size  
DatabaseMirroringGUIBug.png (restricted) Michael Hotek 5/9/2008 -
Sign in to post a comment.
Posted by Microsoft on 2/24/2009 at 7:39 PM
Michael, we are resolving this as wont fix in yukon. This is fixed in Katmai. Gopal
Posted by Microsoft on 5/14/2008 at 11:43 AM
Thanks for reporting this issue. As you have seen there are cases where the DBM UI is more restrictive in what it will accept compared to the DDL. This will affect demo scenarios, such as yours, where you're configuring mirroring using multiple instances on the same machine. Production scenarios should not be impacted as the servers will be in a domain and have a FQDN; if not in a domain then certificates needs to be configured and the UI cannot be used.

This issue is addressed in SQL Server 2008 - instead of an error message box, a warning is displayed and you have the option to continue.

On 2005, it looks like you will be able to workaround the issue - see the following forum post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1715639&SiteID=1

Thanks again for taking the time to report this issue.
Sign in to post a workaround.
Posted by Michael Hotek on 5/9/2008 at 12:04 PM
Do not use the GUI.

Open a query window, connect to the mirroring and issue: ALTER DATABASE <databasename> SET PARTNER = 'TCP://principalmachine:port'

Connect to the principal and issue: ALTER DATABASE <databasename> SET PARTNER = 'TCP://mirrormachine:port'
ALTER DATABASE <databasename> SET WWITNESS = 'TCP://witnessmachine:port'
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement