Results 1 to 3 of 3

Thread: SQL ENT 2005 on 2 node ENT 12003 cluster SQL Server Agent will not start

  1. #1
    Joe Guest

    SQL ENT 2005 on 2 node ENT 12003 cluster SQL Server Agent will not start

    PLEEEEEASE HELP

    I am at my wits end now 3 days 5-6 Install / Un-Installs with trying
    to get this 2 node Active/Passive to start the SQL Server Agent.

    The Cluster Resource Registry entries are just like MS MSDN, Technet
    and a 100 other articles have said they should look like.

    Both Nodes
    Environment: MS Server 2003 SP2
    Dual Dual Core 2.28 processors
    2 Gig Memory each
    Quorum EMC iSCSI lun x
    Data drive EMC iSCSI lun y

    MSCS is setup and works great.

    Failover of SQL server works great with the exception of the SQL
    Server Agent.
    Also I can connect to SQL server/instance remotely from my
    workstation.

    All the DOMAIN/GROUPS and Service DOMAIN/USER are in the groups and
    the Local Machine Administraor group.

    What is happening is that when the SQL Server Agent trys to connect to
    the SQL Server Instance Servername/Instance it is not using the
    VirtualServerName from the Sql Server Agent Resource but the Virtual
    Cluster name.


    This is the error log from the SQLagent.out
    Notice the Servername/Instance line. Server is not the Virtual SQL
    name which is I3PLCLSSQL and has a DNS Entry and can be connected
    to SQL Server remotely.

    2008-04-19 16:38:35 - ! [298] SQLServer Error: 65535, SQL Network
    Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
    [SQLSTATE 08001]
    2008-04-19 16:38:35 - ! [165] ODBC Error: 0, Login timeout expired
    [SQLSTATE HYT00]
    2008-04-19 16:38:35 - ! [298] SQLServer Error: 65535, An error has
    occurred while establishing a connection to the server. When
    connecting to SQL Server 2005, this failure may be caused by the fact
    that under the default settings SQL Server does not allow remote
    connections. [SQLSTATE 08001]
    ==============
    2008-04-19 16:38:35 - ! [000] Unable to connect to server

    '3PLSQLCLS\I3PLRPTSQL'; SQLServerAgent cannot start

    2008-04-19 16:39:05 - ! [298] SQLServer Error: 65535, SQL Network
    Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
    [SQLSTATE 08001]
    ==============

    2008-04-19 16:39:05 - ! [165] ODBC Error: 0, Login timeout expired
    [SQLSTATE HYT00]
    2008-04-19 16:39:05 - ! [298] SQLServer Error: 65535, An error has
    occurred while establishing a connection to the server. When
    connecting to SQL Server 2005, this failure may be caused by the fact
    that under the default settings SQL Server does not allow remote
    connections. [SQLSTATE 08001]
    2008-04-19 16:39:05 - ! [382] Logon to server '3PLSQLCLS\I3PLRPTSQL'
    failed (DisableAgentXPs)
    2008-04-19 16:39:06 - ? [098] SQLServerAgent terminated (normally)

  2. #2
    Joe Guest

    Re: SQL ENT 2005 on 2 node ENT 12003 cluster SQL Server Agent will not start

    On Sat, 19 Apr 2008 23:32:44 -0400, Joe <jmowry@joment.com> wrote:

    WHOO HAAAA FOUND THE FIX FOR THIS DEVIOUS ISSUE LISTED BELOW.

    Added VIRTUALSERVERNAME\INSTANCE as the value for the following
    registry key on both nodes of the cluster.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
    Server\MSSQL.1\SQLServerAgent\ServerHost

    With in place went to Cluster Admin and brought the Resource on line
    without issue.

    Failed to 2nd node, all came up perfectly

    Failed back to 1st node and all started again perferctly.

    After 4 days of searching FOUND IT.


    >PLEEEEEASE HELP
    >
    >I am at my wits end now 3 days 5-6 Install / Un-Installs with trying
    >to get this 2 node Active/Passive to start the SQL Server Agent.
    >
    >The Cluster Resource Registry entries are just like MS MSDN, Technet
    >and a 100 other articles have said they should look like.
    >
    > Both Nodes
    >Environment: MS Server 2003 SP2
    >Dual Dual Core 2.28 processors
    >2 Gig Memory each
    >Quorum EMC iSCSI lun x
    >Data drive EMC iSCSI lun y
    >
    >MSCS is setup and works great.
    >
    >Failover of SQL server works great with the exception of the SQL
    >Server Agent.
    >Also I can connect to SQL server/instance remotely from my
    >workstation.
    >
    >All the DOMAIN/GROUPS and Service DOMAIN/USER are in the groups and
    >the Local Machine Administraor group.
    >
    >What is happening is that when the SQL Server Agent trys to connect to
    >the SQL Server Instance Servername/Instance it is not using the
    >VirtualServerName from the Sql Server Agent Resource but the Virtual
    >Cluster name.
    >
    >
    >This is the error log from the SQLagent.out
    >Notice the Servername/Instance line. Server is not the Virtual SQL
    >name which is I3PLCLSSQL and has a DNS Entry and can be connected
    >to SQL Server remotely.
    >
    >2008-04-19 16:38:35 - ! [298] SQLServer Error: 65535, SQL Network
    >Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
    >[SQLSTATE 08001]
    >2008-04-19 16:38:35 - ! [165] ODBC Error: 0, Login timeout expired
    >[SQLSTATE HYT00]
    >2008-04-19 16:38:35 - ! [298] SQLServer Error: 65535, An error has
    >occurred while establishing a connection to the server. When
    >connecting to SQL Server 2005, this failure may be caused by the fact
    >that under the default settings SQL Server does not allow remote
    >connections. [SQLSTATE 08001]
    >==============
    >2008-04-19 16:38:35 - ! [000] Unable to connect to server
    >
    >'3PLSQLCLS\I3PLRPTSQL'; SQLServerAgent cannot start
    >
    >2008-04-19 16:39:05 - ! [298] SQLServer Error: 65535, SQL Network
    >Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
    >[SQLSTATE 08001]
    >==============
    >
    >2008-04-19 16:39:05 - ! [165] ODBC Error: 0, Login timeout expired
    >[SQLSTATE HYT00]
    >2008-04-19 16:39:05 - ! [298] SQLServer Error: 65535, An error has
    >occurred while establishing a connection to the server. When
    >connecting to SQL Server 2005, this failure may be caused by the fact
    >that under the default settings SQL Server does not allow remote
    >connections. [SQLSTATE 08001]
    >2008-04-19 16:39:05 - ! [382] Logon to server '3PLSQLCLS\I3PLRPTSQL'
    >failed (DisableAgentXPs)
    >2008-04-19 16:39:06 - ? [098] SQLServerAgent terminated (normally)


  3. #3
    Ryan Sokolowski [MVP] Guest

    Re: SQL ENT 2005 on 2 node ENT 12003 cluster SQL Server Agent will not start

    Not really sure you should have needed to do this, as installing SQL 2005 on
    a properly setup 2003 cluster is really *almost* automatic, but I'm happy
    that it works for you now! :-)

    Let us know if you have any other issues...

    --
    Ryan Sokolowski
    MVP - Clustering
    MCSE, CCNA, CCDA, BCFP

    "Joe" <jmowry@joment.com> wrote in message
    news:s0jl045488v9rk1etql9o4d5f0h36p5398@4ax.com...
    > On Sat, 19 Apr 2008 23:32:44 -0400, Joe <jmowry@joment.com> wrote:
    >
    > WHOO HAAAA FOUND THE FIX FOR THIS DEVIOUS ISSUE LISTED BELOW.
    >
    > Added VIRTUALSERVERNAME\INSTANCE as the value for the following
    > registry key on both nodes of the cluster.
    >
    > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
    > Server\MSSQL.1\SQLServerAgent\ServerHost
    >
    > With in place went to Cluster Admin and brought the Resource on line
    > without issue.
    >
    > Failed to 2nd node, all came up perfectly
    >
    > Failed back to 1st node and all started again perferctly.
    >
    > After 4 days of searching FOUND IT.
    >
    >
    >>PLEEEEEASE HELP
    >>
    >>I am at my wits end now 3 days 5-6 Install / Un-Installs with trying
    >>to get this 2 node Active/Passive to start the SQL Server Agent.
    >>
    >>The Cluster Resource Registry entries are just like MS MSDN, Technet
    >>and a 100 other articles have said they should look like.
    >>
    >> Both Nodes
    >>Environment: MS Server 2003 SP2
    >>Dual Dual Core 2.28 processors
    >>2 Gig Memory each
    >>Quorum EMC iSCSI lun x
    >>Data drive EMC iSCSI lun y
    >>
    >>MSCS is setup and works great.
    >>
    >>Failover of SQL server works great with the exception of the SQL
    >>Server Agent.
    >>Also I can connect to SQL server/instance remotely from my
    >>workstation.
    >>
    >>All the DOMAIN/GROUPS and Service DOMAIN/USER are in the groups and
    >>the Local Machine Administraor group.
    >>
    >>What is happening is that when the SQL Server Agent trys to connect to
    >>the SQL Server Instance Servername/Instance it is not using the
    >>VirtualServerName from the Sql Server Agent Resource but the Virtual
    >>Cluster name.
    >>
    >>
    >>This is the error log from the SQLagent.out
    >>Notice the Servername/Instance line. Server is not the Virtual SQL
    >>name which is I3PLCLSSQL and has a DNS Entry and can be connected
    >>to SQL Server remotely.
    >>
    >>2008-04-19 16:38:35 - ! [298] SQLServer Error: 65535, SQL Network
    >>Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
    >>[SQLSTATE 08001]
    >>2008-04-19 16:38:35 - ! [165] ODBC Error: 0, Login timeout expired
    >>[SQLSTATE HYT00]
    >>2008-04-19 16:38:35 - ! [298] SQLServer Error: 65535, An error has
    >>occurred while establishing a connection to the server. When
    >>connecting to SQL Server 2005, this failure may be caused by the fact
    >>that under the default settings SQL Server does not allow remote
    >>connections. [SQLSTATE 08001]
    >>==============
    >>2008-04-19 16:38:35 - ! [000] Unable to connect to server
    >>
    >>'3PLSQLCLS\I3PLRPTSQL'; SQLServerAgent cannot start
    >>
    >>2008-04-19 16:39:05 - ! [298] SQLServer Error: 65535, SQL Network
    >>Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
    >>[SQLSTATE 08001]
    >>==============
    >>
    >>2008-04-19 16:39:05 - ! [165] ODBC Error: 0, Login timeout expired
    >>[SQLSTATE HYT00]
    >>2008-04-19 16:39:05 - ! [298] SQLServer Error: 65535, An error has
    >>occurred while establishing a connection to the server. When
    >>connecting to SQL Server 2005, this failure may be caused by the fact
    >>that under the default settings SQL Server does not allow remote
    >>connections. [SQLSTATE 08001]
    >>2008-04-19 16:39:05 - ! [382] Logon to server '3PLSQLCLS\I3PLRPTSQL'
    >>failed (DisableAgentXPs)
    >>2008-04-19 16:39:06 - ? [098] SQLServerAgent terminated (normally)



Similar Threads

  1. Replies: 1
    Last Post: 21-05-2011, 12:41 AM
  2. Replies: 1
    Last Post: 23-04-2011, 06:14 PM
  3. could not start the cluster service on node 2
    By Rami Khatib in forum Windows Server Help
    Replies: 4
    Last Post: 19-06-2009, 09:07 PM
  4. Windows 2008 cluster for SQL server 2005 cluster
    By Roger in forum Windows Server Help
    Replies: 2
    Last Post: 21-05-2008, 10:16 AM
  5. Failover behaviour on a 2 node cluster
    By Ariel in forum Windows Server Help
    Replies: 9
    Last Post: 30-04-2005, 02:16 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •