March 18, 2011 at 10:45 am
I installed R2 on my laptop and it seemed to install fine. I run SQL Server service and SQL Agent service as manual startup services so I don't have the drag on my processor every time I fire up my laptop. The service accounts are mapped to my user account (private laptop with test data only for studying purposes).
Every time I go into the Services mmc, I can start the SQL Server service just fine. But when I try to start the Agent service, I get the following message (after several minutes of service starting).
The SQL Server Agent (SQL2K8_R2) service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
Terribly generic and I can't seem to find this error on Google anywhere. Thoughts?
March 18, 2011 at 10:53 am
You can usually get more information by looking in the SQLAGENT.OUT in your SQL Server logs directory...
The path is something like C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG by default
March 18, 2011 at 11:07 am
Or check the event logs, usually the security one.
March 18, 2011 at 11:09 am
Thanks, Howard. I have both 2k5 and 2k8 R2 installed on my laptop and I can only find one version of that file, exactly where you said it was. However, all the dates on the file are filled with 02/02/2011 and don't have any information for today (which is the last time I tried to start the service).
I'm running Vista business as my OS. I'm hoping that's not the issue.
Trying online help (from Event Viewer) gets me the generic "We're sorry. There is no additional information about this issue..." Bleargh.
Any other thoughts?
March 18, 2011 at 11:19 am
What does the event viewer message say? You can double check which logs directory to look in by looking at the path to the executable for the agent service.
In the absence of the actual error, there's not much I can suggest other than that these sorts of problems always seem to be permissions based for me... Especially if it's not getting as far as touching SQLAGENT.OUT, it's possible the service account has no access to the directory...
March 18, 2011 at 11:24 am
Steve Jones - SSC Editor (3/18/2011)
Or check the event logs, usually the security one.
Not seeing a whole lot under security, except a few messages (about the first time I tried) about the Firewall blocking an application and failing to warn me.
So I checked the Firewall. A recent update to my laptop changed the settings. I went to Exceptions, but none of the SQL components are listed as possible to exclude (and no method of manual entry / browsing to a program) except the DTC.
So I tested by turning off the Firewall and no go. And yes, I've also tested using the Local System account and no go on that either.
March 18, 2011 at 11:33 am
HowardW (3/18/2011)
What does the event viewer message say?
The Application event says exactly what I posted above, with an event ID of 103, Task Category: Service Control, Keywords: Classic and Detail says "Unable to connect to server 'ComputerName\SQL2k8_R2'; SQLServerAgent cannot start.
The thing I don't understand is that the instance name is correct. I can connect to it via SSMS and the SQL Server service runs just fine. But I can't start the agent either in Services or SSMS.
You can double check which logs directory to look in by looking at the path to the executable for the agent service.
Thanks I'll look at that.
In the absence of the actual error, there's not much I can suggest other than that these sorts of problems always seem to be permissions based for me... Especially if it's not getting as far as touching SQLAGENT.OUT, it's possible the service account has no access to the directory...
I'm not sure that's the problem here given that I've given my account admin access to the machine, but I guess I'll have to test with the typical plain vanilla account and see what happens.
March 18, 2011 at 11:42 am
PROGRESS!
Found the proper log under the directory I set as my default database location.
...\R2\MSSQL10_50.SQL2K8_R2\MSSQL\Log
"SQL Server 2008 SQLServer Error: 65535" comes up with Google links, the first of which is this:
I'll be checking this and other articles. Thank you both for pointing me in the correct direction.
March 23, 2011 at 5:04 am
Well, progress didn't help me much. There's still not a whole lot out there. But I'm attempting to repair the install to see if that works.
If not, I guess I'm stuck with an uninstall - reinstall. Anyone know if uninstalling R2 shared components will hurt SQL 2k5?
March 23, 2011 at 5:23 am
Hi
if sql server agent is not able to connect sql server database engine, we will get this error
Kindly check what service account sql server agent service is running , whether that service account has permission to connect to database engine... and also it should have SA pervilege.
Regards
Kokila K
March 23, 2011 at 5:25 am
Kokila, thanks for the advice, but as stated above, the service account is running under full Sysadmin permissions (which would be a complete no-no if I were running this on a corporate box of any flavor. As would be using SA permissions). That's not the issue.
EDIT: You do understand why using Sysadmin / SA permissions is a bad idea for a service account, right?
March 23, 2011 at 7:38 am
Gah. This is seriously annoying. Neither Repair nor an uninstall / reinstall fixed the issue.
Any more thoughts?
March 23, 2011 at 7:42 am
Can you post the entire contents of SQLAGENT.OUT? I take it this is the RTM version of R2, not a CTP (just checking as the connect bug you linked to was for a pre-release version)
Edit: Also, what OS and is it 64 bit?
March 23, 2011 at 7:56 am
I've just opened up a new connect issue with the details of the SQLAgent.Out.
EDIT: OS is Vista Business 32 bit.
Here's what I've posted:
"2011-03-18 13:34:41 - ! [298] SQLServer Error: 65535, SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
2011-03-18 13:34:41 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2011-03-18 13:34:41 - ! [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]
2011-03-18 13:34:41 - ! [000] Unable to connect to server 'ComputerName\SQL2K8_R2'; SQLServerAgent cannot start
2011-03-18 13:34:46 - ! [298] SQLServer Error: 65535, SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
2011-03-18 13:34:46 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2011-03-18 13:34:46 - ! [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]
2011-03-18 13:34:46 - ! [382] Logon to server 'ComputerName\SQL2K8_R2' failed (DisableAgentXPs)
2011-03-18 13:34:47 - ? [098] SQLServerAgent terminated (normally)"
Remote Connections is set to allow (so I don't know why it's giving me that error). Instance name is the same for SQL Agent as it is for SQL Service, so if that was wrong, both should have failed. I have Shared Memory and TCP / IP enabled.
For those who might have the same issue, my connect issue is at:
March 23, 2011 at 8:09 am
Is the SQL Server Browser Service Running?
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply