Problems on connection during mirroring (Error 1418)

  • Hi everyone, I am a newbie on setting up database mirroring and right now I am facing the connection problem during mirroring which is Error 1418 which kinda common problem. I just view through all the threads regarding this problems and BOL also. However, I just based on all the guide to setting it up and the result are still the same.

    I did tried on both instance names in my server for mirroring and displayed the same results as well. When I type this t-sql on mirror server :

    ALTER DATABASE AdventureWorks SET PARTNER = 'TCP://TSUYOSHI:5022' -- which is the  principal server

    It shows connection ok to me. However, when I type this t-sql on the principal server :

    ALTER DATABASE AdventureWorks SET PARTNER = 'TCP://HAN:5023' -- which is the  Mirror server

    It shows connection ok to me. However, when I type this t-sql on the principal server :

    Msg 1418, Level 16, State 1, Line 1

    The server network address "TCP://HAN:5023" 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.

    I just wondering that why mirror can get a connection to principal but principal can't? Is that any extra configuration especially security settings that needed to be set within the database (MS sql server 2005) ?

    I hope I am able to get any assistance from anyone at here and will appreciate on it. Thanx. Anyway, sorry for the inconvenience

    Best Regards,

                              Han

  • i set up mirroring a few weeks ago via the GUI and it went pretty smoothly. Had a problem earlier in the week and restarting SQL on the witness seemed to fix it. Along with a few other things.

    Are you running replication? Check for locks due to replication. I had to pause my distributor.

  • Nope, I didn't even setting up the replication at all. I did check on Can I know how am I going to check the error through log within sql server 2005 ?

    -------------------------------------------

    a) (TSUYOSHI) Principal server's Information :

    i) sys.database_mirroring_endpoints

    name : Mirroring

    endpoint_id : 65536

    principal_id : 1 

    protocol : 2,

    protocol_desc : TCP

    type : 4

    type_desc : DATABASE_MIRRORING

    state : 0 

    state_desc : STARTED

    is_admin_endpoints : 0 

    role : 1 

    role_desc : PARTNER

    is_encryption_enabled : 1

    connection_auth : 3 

    connection_auth_desc : NEGOTIATE

    certificate_id =  0 

    encryption_algorithm = 1 

    encryption_algorithm_desc = RC4

    ii) sys.endpoints

    name : Mirroring 

    endpoint_id : 65536 

    principal_id : 1 

    protocol : 2 

    protocol_desc : TCP

    type : 4

    type_desc : DATABASE_MIRRORING

    state : 0 

    state_desc : STARTED 

    is_admin_endpoint : 0

    iii) sys.tcp_endpoints

    name : Mirroring 

    endpoint_id :65536 

    principal_id : 1 

    protocol : 2 

    protocol_desc : TCP 

    type : 4 

    type_desc : DATABASE_MIRRORING 

    state : 0 

    state_desc : STARTED 

    is_admin_endpoint : 0 

    port : 5022 

    is_dynamic_port : 0 

    ip_address : NULL

    b) (HAN) Mirror server's Information :

    i) sys.database_mirroring_endpoints

    name : Mirroring 

    endpoint_id : 65536 

    principal_id : 1 

    protocol : 2 

    protocol_desc : TCP 

    type : 4 

    type_desc : DATABASE_MIRRORING 

    state : 0 

    stated_desc : STARTED 

    is_admin_endpoint : 0 

    role : 3 

    role_desc : ALL

    is_encryption_enabled : 1 

    connection_auth : 3 

    connection_auth_desc : NEGOTIATE 

    certificate_id : 0 

    encryption_algorithm : 1 

    encryption_algorithm_desc : RC4

    ii) sys.endpoints

    name : Mirroring 

    endpoint_id : 65536 

    principal_id : 1 

    protocol : 2 

    protocol_desc : TCP

    type : 4

    type_desc : DATABASE_MIRRORING

    state : 0 

    state_desc : STARTED 

    is_admin_endpoint : 0

    iii) sys.tcp_endpoints

    name : Mirroring 

    endpoint_id :65536 

    principal_id : 1 

    protocol : 2 

    protocol_desc : TCP 

    type : 4 

    type_desc : DATABASE_MIRRORING 

    state : 0 

    state_desc : STARTED 

    is_admin_endpoint : 0 

    port : 5023 

    is_dynamic_port : 0 

    ip_address : NULL

    -------------------------------------------

    Information stated as above are the settings for my principal and mirror's endpoints and both seems are the same. Is there any wrong for the settings?

    Extra questions :

    1) What's the 'Build-in Account' that is valid to prefer for log on in both  principal and mirror server? (Local System/Local Service/Network Service). I am using Local System for login into both servers by the way.

    2) What's the meaning of Service Accounts? Is it needed to be set? Can give  some example on it ?

    3) Is there any configuration need to be concern in preferred database's properties at principal server side ?  

    Sorry for the inconvenience again.Hope can solve it as soon as possible.Thx.

    Best Regards,

            Hans

     

  • For the updates, I did tried on the telnet connection to test on the port whether is available between the principal and mirror server. As the results, both of the ports are work. However, it still unable to get mirroring in server 2005. Is there any additional tasks required?

     

    Best Regards,

                    Hans

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

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