Post reply

sql 2012 mirroring using sql xpress as witness

  • June 23, 2013 at 4:19 pm

    #278953

    Hi,

    I'm trying to set up mirroring between two sql server 2012 instances and use sql server 2012 xpress as the witness. the primary and secondary instances do not see the xpress instance, which is a vm btw. but the witness sees the primary and secondary, kinda like a compatibility issue. Can i use xpress as a witness when setting up sql server 2012 mirroring? all are in the same domain.

  • June 23, 2013 at 9:28 pm

    #1626636

    Firstly, yes Express can be the witness (see http://msdn.microsoft.com/en-us/library/cc645993.aspx)

    This may be a configuration issue with the Express instance. Not sure whether this is the correct suggestion, but - is the Express instance configured to allow remote connections ?

  • June 25, 2013 at 8:53 am

    #1627170

    Thanks SS I will check the config.

  • June 26, 2013 at 11:02 am

    #1627661

    got it had to do the following:

    To assign a TCP/IP port number to the SQL Server Database Engine

    Using SQL Server Configuration Manager

    1.In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, expand Protocols for <instance name>, and then double-click TCP/IP.

    2.In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties to identify the IP address that you want to configure.

    3. If the TCP Dynamic Ports dialog box contains 0, indicating the Database Engine is listening on dynamic ports, delete the 0.

    4.In the IPn Properties area box, in the TCP Port box, type the port number you want this IP address to listen on, and then click OK.

    5.In the console pane, click SQL Server Services.

    6.In the details pane, right-click SQL Server (<instance name>) and then click Restart, to stop and restart SQL Server.

    Thanks for everyones help and hope this may help the next person with a similiar issue

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply