locked
Event id: 1479 ( Primary Server) and Event id: 1474 ( Witness Server) RRS feed

  • Question

  • We Having Environment of Mirroring High Safety with automatic fail-over ( Witness Server ) in SQl 2012.

    Primary Server: ABC; Mirror Server: CBA; Witness Server: DEF

    I got two alerts 

    One from Primary Server with event id 1479 and Msg: The mirroring connection to "TCP://DEF(Witness Server):5022" has timed out for database "XXXX" after 10 seconds without a response.  Check the service and network connections.


    Second Alert from Witness Server with event id 1474 and Msg: " Database mirroring connection error 4 'The connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)'' for 'TCP://ABC(Principle Server):5022'.

    I verified three servers are up and both Primary and Mirror Server databases are Synchronized.

    My Question is what are the reason caused to generate the alerts
    Thursday, September 19, 2013 2:01 PM

Answers

  • Hi Siraj,

    According to the alert description, this problem can occurred as following, you can refer to the points.

    1) The witness cannot make connection to principle server due to network error, and then  Mirror server was trying to change role from Mirror to Principle.
    2)Due to unknown reason (possible network problem) mirror server cannot fully changed status to Principle and hence its status is “Synchronizing”.

    Thanks,
    Sofiya Li


    Sofiya Li
    TechNet Community Support

    • Marked as answer by Sofiya Li Friday, October 4, 2013 8:35 AM
    Friday, September 20, 2013 7:22 AM

All replies

  • Hi Siraj,

    According to the alert description, this problem can occurred as following, you can refer to the points.

    1) The witness cannot make connection to principle server due to network error, and then  Mirror server was trying to change role from Mirror to Principle.
    2)Due to unknown reason (possible network problem) mirror server cannot fully changed status to Principle and hence its status is “Synchronizing”.

    Thanks,
    Sofiya Li


    Sofiya Li
    TechNet Community Support

    • Marked as answer by Sofiya Li Friday, October 4, 2013 8:35 AM
    Friday, September 20, 2013 7:22 AM
  • Hi,

    Make sure that you have logged in to the SQL Server Management Studio with the User that has a SYSADMIN permission. It should work.

    Regards

    Syed

    Tuesday, January 21, 2014 6:56 AM