Post reply

Static port of SQLServer exe is grapped by SQL Agent of another instance in cluster env.

  • June 19, 2012 at 9:02 am

    #98466

    Static port of SQLServer exe is grapped by SQL Agent of another instance in cluster environment

    ========================================================================

    We have faced issue of application connectivity in SQL SERVER 2000 + Windows Server 2003 cluster.

    This problem occurs after failover of node A to node B due to unexpected restart of node A. We have found that SQLG\G instance is failed to bind the supersocket connection with port 2539 in sql server error log of SQLG\G instance.

    After trouble shooting we comes to know that port 2539 on node B is already used by SQL SERVER Agent service of SQLF\F instance.”

    Can any body know how this can be avoided? Can we assign static port to SQL Agent services as well?

  • June 19, 2012 at 10:48 am

    #1502989

    What did you use to determine that the SQL Agent service was using that port?

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • June 20, 2012 at 1:57 am

    #1503256

    Below is the output of netstat from SQLB node before re-start ( I have run below command to get the output)

    netstat -ano | find "0.0.0.0"

    SQL server exe :

    TCP 101.228.656.153:1433 0.0.0.0:0 LISTENING 2508 - Instance D

    TCP 101.228.656.154:4538 0.0.0.0:0 LISTENING 1128 - Instance E

    TCP 101.228.656.155:3875 0.0.0.0:0 LISTENING 6248 - Instance f

    SQL Agent exe :

    TCP 0.0.0.0:2462 0.0.0.0:0 LISTENING 2508 - D Agent

    TCP 0.0.0.0:2443 0.0.0.0:0 LISTENING 1128 - E Agent

    TCP 0.0.0.0:2539 0.0.0.0:0 LISTENING 6248 - F Agent

    First 3 lines are for SQL server exe which is confirmed by it’s respective port no. (1433, 4538 & 3875). Its respective agent process has also taken the port mentioned in the 2nd column. [/size]Combination of SQL Server and Agent exe is matched on the basis of PID ( last column).

  • June 20, 2012 at 10:03 am

    #1503565

    SQL Agent shouldn't take a port on startup. Has somebody configured an endpoint for it to use one of those ports?

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

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

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