Post reply

Database Mirroring: fails when enable button is activated

  • November 9, 2006 at 8:23 am

    #171000

    I think I may already know the answer to this but I'd like someone to confirm it!

    I am trying to set up database mirroring between 2 Servers (no Witness) everything looks to be working fine until I hit the enable mirroring button it then fails with the message:

    The server network address "TCP://NOTNT94.DOMGENNT.DGGROUP.COM: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. (.Net SqlClient Data Provider)

    Server Name: WIMNT93\Respond

    Error Number: 1418

    Severity: 16

    State: 1

    Line Number: 1

    I can ping both these servers from each other and the ports are open. the one thing that is worrying me is that the service accounts being used on both servers for the instances login and run under the local system account. Is this going to cause the mirroring operation to fail? 

    I have done everythin the BOL suggests - creating certificates etc, but I still get the dreaded 1418 message when I attempt to start the mirror.

    I have looked at the ports using the NETSTAt -abn command and find that the port i am using (7024) is listening but with an ipaddress of 0.0.0.0 when the server ipadress is 172.18.8.217 is this normal? if not how can i sort it out? The BOL is not great for networking advice 

  • November 10, 2006 at 2:33 am

    #671029

    Your port declarations in your post don't match. You say that you are using port 7024, but the network address is specifying port 5022. Check your port declarations. If that isn't it, redo your certificate set up.

    My blog: SQL Soldier[/url]
    SQL Server Best Practices:     SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

  • November 10, 2006 at 7:10 am

    #671075

    That was a typo!! - 18 hour day! anyway came in this morning and rebooted the mirror server and then did new backups and restores , It is now all working (port 7024). The next thing is to test the failover, which will happen tomorrow.

    I assume if I manually failover I don't need to pause or resume the the mirror first?

    Anybody got any experience of adding a witness using SQLExpress Edition that's the next phase of the project!

        

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

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