June 2, 2016 at 1:26 am
Hi Team,
i have windows 2012 R2 cluster set up node1 and node2, on that i have installed SQL 2012 instances ins1,ins2 and SQL 2014 instances ins3, ins4 later i have uninstalled SQL 2012 instances ins1,ins2 on both the nodes, and started installation of SQL Server 2016 ins1,ins2 on node1, node2 successfully, but SQL Server Agent failed to start, when i bringing the agent services online it comes online and again failing, i have verified the registry keys all good.
below are the error messages:
SQL Server Agent could not be started unable to connect the server Agent can not start.
sqlgtres check service alive dead.
Agent log also same information, agent having permissions and all
Someone please advise me to resolve the issue.
June 2, 2016 at 2:07 am
Possibly login failed for the account that runs SQL Server. Does your SQL Server errorlog capture failed logins? If so, have a look and see whether there are any entries at the time you attempted to start SQL Server Agent.
It would also help if you could post the exact error messages you're getting on screen and/or in SQLAGENT.OUT. In my experience, they read much more like full sentences than what you've posted.
John
June 2, 2016 at 2:31 am
Hi Thanks for the reply
Below are the SQLagent.out output
2016-06-02 03:03:24 - ? [100] Microsoft SQLServerAgent version 13.0.1601.5 (X64 unicode retail build) : Process ID 9008
2016-06-02 03:03:24 - ? [495] The SQL Server Agent startup service account is OFFICE\SQLService.
2016-06-02 03:03:54 - ! [150] SQL Server does not accept the connection (error: 65535). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2016-06-02 03:03:54 - ! [000] Unable to connect to server 'IP-SQL630-INS1\INS1'; SQLServerAgent cannot start
2016-06-02 03:03:59 - ! [298] SQLServer Error: 65535, SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
2016-06-02 03:03:59 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2016-06-02 03:03:59 - ! [298] SQLServer Error: 65535, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2016-06-02 03:03:59 - ! [382] Logon to server 'IP-SQL630-INS1\INS1' failed (DisableAgentXPs)
2016-06-02 03:03:59 - ? [098] SQLServerAgent terminated (normally)
June 2, 2016 at 2:49 am
What protocols (Named Pipes, TCP/IP etc) is SQL Server configured to use? You can find this out by looking in SQL Server Configuration Manager.
John
June 2, 2016 at 2:50 am
We have TCP\ip and ( changed the default port), named pipes are enabled
Thanks
June 2, 2016 at 3:03 am
June 2, 2016 at 3:07 am
Yes, browser service running
June 2, 2016 at 3:23 am
1) Are you able to access the database instance from a remote SSMS ?
2) Are you using any aliases in the SQL Agent Properties-Connection?
June 2, 2016 at 3:27 am
Yes I am able to connect remotely and no aliases, I checked all low level
June 2, 2016 at 3:45 am
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible.
I think this clearly says the cant see the database engine service itself. I think you need to troubleshoot in that direction. firewall, port etc
June 2, 2016 at 3:55 am
Yes, maybe Named Pipes is configured in a non-default way. Try creating an alias that connects with TCP/IP and specify that as the alias in the properties of SQL Server Agent.
John
June 2, 2016 at 3:57 am
firewalls are off, ports are specified and Services failing over and failing back perfectly, not able to find where the issue exactly.
June 2, 2016 at 4:58 am
TITLE: Microsoft SQL Server Management Studio
------------------------------
Unable to cast COM object of type 'System.__ComObject' to interface type 'System.Management.IWbemServices'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{9556DC99-828C-11CF-A37E-00AA003240C7}' failed due to the following error: The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD)). (mscorlib)
------------------------------
BUTTONS:
OK
------------------------------
is this related to SQL Server Agent???
June 2, 2016 at 5:23 am
From your first reply it looks like shared memory is not enabled. For connections connecting locally, SQL server must be using shared memory protocol. Have you tried enabling this?
June 2, 2016 at 5:29 am
Nope all protocols are enabled
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply