Post reply

Mirroring issues when adding a Witness Server

  • May 7, 2009 at 8:39 am

    #200186

    Hi all,

    A- Principal / SQL 2008 Std 64-bit / Win 2003 Std

    B- Mirror / SQL 2008 Std 64-bit / Win 2003 Std

    C- Witness / SQL 2008 Express / Win XP

    I'm having some issues adding a witness server to SQL 2008 Mirroring. I've basically setup mirroring and failover runs fine between the principal and mirror. I've double checked the endpoints and their security as per the MS docs and I can't find any issues.

    Some more notes:

    - Servers are not in a domain

    - I've edited the hosts file, all can ping each other and connect fine through SSMS

    - Endpoints have been configured as well as CONNECT granted on local accts

    - A master key was generated for each instance, certificates backed up, copied and added to each instance as well as configuring logins

    - I've tried with & without FQDN

    - I've tried setting the witness via SSMS 'Configure Security' - it falls over when I hit ok at the end

    Alter failed for database 'Widgets ..... The ALTER DATABASE command could not be sent to the remote server instance 'TCP://WITNESS' The database mirroring configuration was not changed. Verify that the server is connected, and try again (Microsoft SQL Server, Error:1456))''

    I've tried setting the witness via T-SQL & via the configure security option in SSMS

    ALTER DATBASE Widgets SET WITNESS = 'TCP://WITNESS.RR.DOMAIN:7024'

    Results in

    The ALTER DATABASE command could not be sent to the remote server instance 'TCP://WITNESS.RR.DOMAIN:7024'. The database mirroring configuration was not changed. Verify that the server is connected, and try again

    On the Witness box, the event log shows the following:

    A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error '3(failed to retrieve text for this error. Reason: 1815)'.

    I have followed this guide too

    Does anyone know where I should start looking?

    Thanks in advance!

  • May 7, 2009 at 10:25 am

    #990492

    Solved my own problem - Firewall had turned itself on the Witness / XP box -grrr!

Viewing 2 posts - 1 through 1 (of 1 total)

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