Can't (re)start SQLServerAgent After Changing Its Logon Credentials
May 30, 2007
Since Copy Databas Wizard failed to copy anything from remote SS20005 (both are with SP2 3054) in any combination,
I changed SQLServerAgent(myinstance_name) to run under Network from Local System with the help of SQL Server Configuration Manager
For this change it was restarted, failed to start again and continues to be stopped giving
"SQLServerAgent could not be started (reason: Unable to connect to server '<mymachine_name><myinstance_name>'; SQLServerAgent cannot start)."
I changed SQL Server Agent (myinstance_name) back to Local Service, then to Local System and still can't start it.
So, my questions:
1)
What has happened and how can I start SQLServerAgent?
2)
Why cannot I start it under Network Service? since it apparently should access remote resources for CDW to copy from remote SS2005
This is on MS Windows XP SP2
PS
After few trials I amnaged to restart it again under Local System but still cannot change to any different one
We're running sql 7.0 sp1 and both the sqlserver service and sqlserveragent service are running under local system account. For some reason, the sqlserveragent service started failed with "error 2140" - windows nt internal error From event viewer, it saids it has some connection problem.
The sqlserver service has no problem. All knowledge base material related to 6.5 resolution. Would rebuilding the registry entry help ? I tested and rebuilding the registry did not regrant any registry permission, should it ?
I have a maintenance plan on SQL2000, that is backing up the database.
It is under Management/SQL Server Agent. When I try to start the job, I got an error, saying: Error 22022 SQLServerAgent is not currently running so it cannot be notified of this action.
But, when I try to start the SQL Server Agent (in Services), it stops directly with the following information: The SQLAgent$Sharepoint service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
When I try to start it from the SQL Server Service Manager: no reaction at all!
I have successfully installed SQL 2005 on W2K3 Cluster. The problem is that SQL Server Agent won't start. Below are the lines from SQLAGENT.OUT:
2007-03-15 09:40:02 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001] 2007-03-15 09:40:02 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-03-15 09:40:02 - ! [298] SQLServer Error: 2, 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] 2007-03-15 09:40:02 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start 2007-03-15 09:40:07 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001] 2007-03-15 09:40:07 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2007-03-15 09:40:07 - ! [298] SQLServer Error: 2, 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] 2007-03-15 09:40:07 - ! [382] Logon to server '(local)' failed (DisableAgentXPs) 2007-03-15 09:40:08 - ? [098] SQLServerAgent terminated (normally)
I have tried starting Agent with Domain Admin account. No luck. SQL Server is started.
We just set up VPN on our system and changed the passwords. For some reason I cannot start the SQL Server Agent now. I get this msg: "An error 1069 - (The service did not start due to a logon failure) occurred while performing this service operation on the SQLServerAgent service.
Any ideas why is that happening and what should I do about that?
I restarted the MSSQLSERVER service and SQLSERVERAGENT will not restart. I get the following error.
Could not start the SQLSERVERAGENT service on Local Computer. The service did not return an error. This could be an internal Windows erroror an internal service error. If the problem persists, contact you system administrator.
I need to start the SQLServerAgent because I have a need to install a backup procedure that will run regularly. but I need to also make the Agent service be set up to autostart with the PC. If I go into ControlPanel...Services I can do this manually, but how to do it programmatically? Is there a command line command like net start that can do the trick, or can I direct SQL Server to do it through a TSQL procedure?
i'm using a domain accout to setup a sql 2005 cluster in a win2003 cluster.when the installation ended,the SqlServerAgent service can't be started.the event in event viewer
is "SQLServerAgent could not be started (reason: Unable to connect to server "(local)"; LServerAgent cannot start). " (event id 103 ,source sqlserveragent).I try to use local system and network service account to start it,but it's all the same.
And i found i can connect to the sql cluster vitrual ip 10.73.2.224,but can't connect to the node A.So i enable all the network protocols for the instance MSSQLSERVER,and also enable every ip in the TCP/IP protocol,then restart the sqlserver service,but it still doesn't work.
When I installed MS SQL Server 2000 on our client's computer I installed it under a local account using Windows Authentication as the server logon and am now accessing it using a network login (remoting into the same box). The result is that if I change the password for the local Windows account and reboot the server, SQL server cannot be restarted; I get an error:
A connection could not be established to (LOCAL)
Reason: SQL SERVER does not exist or access denied. ConnectionOpen (Connect())..
Please verify SQL Server is running and check your SQL Server registration properties and try again.
I've changed the registration properties to use SQL Server Authenticaiton instead of Windows to no avail. Whichever connection option I use the server will not start unless I change the local account's password back to what it was when I installed. This works, but our client wants to have that local account's password changed for security/peace of mind. Any help or advice would be appreciated here :)
The local sql server that was working fine earlier does not start now. I have already created tables and accessed them using stored procedures.
I get an error 1069: The service did not start due to logon problems. I have only changed my domain password. I do not remember what authentication I chose for log on.
We seem to be being plagued by the error below by our SQL Server agent. This happens almost everytime we restart the server that has been running for a day or two.
Our SQL Server Agent uses a none expiring domain credential. I understand that this problem only happens when the profile being used by the SQL Servr Agent has changed (password change). What puzzles me is that the login is A ok and no changes has been made to it's password.
We always resolve this problem by changing the login used in the SQL Server Agent to local and after that, returning it back to it's original domain login. Unfortunately, we cant always do this everytime something goes wrong.
Can anyone please help us shed a light on this? We're using SQL2k with SP3a. Thanks!
Error:
An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation on the SQLServerAgent service.
I have come across this error message in ssrs and cannot seem to locate the error. Report manager lets me logon-- I can navigate to the folder but once I click on the actual report I get this error
I am using Administrator to log in the WinNT and I have just changed the password of the Administrator. After that, I discover that I cannot use all function in the sql server. Althougt the server is still running, I cannot open the database, login the security manager.
I have checked that the SQL Executive in NT service is assigned to local system account. As you know, there is no place for inputting password. Where can I change the password in order to let the function of sql server run again?
hi all, i am using SQL Server 7.0 . After changing the machine name the sqlserver is not starting. if i changed the machine name to the old name the server starts as usual. is there a solution for this problem. where can i change the machine name in the sql server configuration. so as to start it correctly... thanks... jinujose
i had installed Sqlserver on drive E: before but i changed the drive letter to D: yesterday and now i can't start my sql server. how can i fix this problem?
Has anyone written or come across a routine that validates start and enddate in a slow changing dimension? (eg verifies there is no overlap in any of the records).
What would cause this message to display or what does this mean?? "Could not start the SQLServerAgent Service, error 2186, the service is not responding to the control function"
I can't start the SQLSERVERAGENT for my sql 2k under win 2003 sp1.
SQLServerAgent could not be started (reason: SQLServerAgent cannot start because the instance of the server (MSSQLSERV) is not the expected instance (MSSQLSERVER)).
I can't find any useful information regarding this error. Any one can help?
When my system re-boots SQLServerAgent will no longer start. The following message is sent to the NT Event Log:
(Event ID 103) "SQLServerAgent could not be started (reason: Unable to connect to server; SQLServerAgent cannot start)."
Following this message are two messages from MSSQLServer that read:
(Event ID 19020) "RPC Net-Library listening on: ncalrpc:USBGRSYSTST1[WMSG0000009A.00000001]."
So is this a timing issues? Is MSSQLServer taking too long to completely start before SQLServerAgent is started? If so, is there a way (without hacking through the registry) to make the SQLServerAgent service dependant on the MSSQLServer service?
This startup issue did not exist until an application was installed on the machine that also has several services that auto-start. I noticed that many of these new services are starting at the same time the MSSQLServer service is starting.
wanted to start the sql server agent and i got this error : An Error 1069 - (The service did not start due to logon faliure ) occured wile performing this service operation on SQLServerAgent servcice.
I am getting the following warning message in the event viewer. I have only one schedule in sql. there is no other schedules in task scheduler or database management.
Event Type:Warning Event Source:SQLSERVERAGENT Event Category:Job Engine Event ID:208 Description: SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan 'DB Maintenance Plan1'' (0xD25A4CDDD1C59E48B4D28F61F0A411B8) - Status: Failed - Invoked on: 2004-08-16 02:30:00 - Message: The job failed. The Job was invoked by Schedule 2 (Schedule 1). The last step to run was step 1 (Step 1).
please i need your help on that sudenly me SQLserveragent stopped and when i try to start it again it give me that error: Event Type:Error Event Source:SQLSERVERAGENT Event Category:Service Control Event ID:103 Date:2/27/2006 Time:11:00:19 AM User:N/A Computer:EGDC2 Description: SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
This may be more of an IT question, but I hope someone here will have the answer.
I am trying to change the "Log on as" for SQLSERVERAGENT NT Service through Windows Registry. I am able to find HKLMSYSTEMCurrentControlSetServicesSQLSERVERAGENTObjectName and change it but I dont know how to specify a password to go with it. If I simply change it to .Administrator (from Local System) it errors out.
Ideally I would like to script this so I can change the logon without having to go though the Services Control Panel or SQL Management Studio.
I have a maintenance plan on SQL2000, that is backing up the database.
It is under Management/SQL Server Agent. When I try to start the job, I got an error, saying: Error 22022 SQLServerAgent is not currently running so it cannot be notified of this action.
But, when I try to start the SQL Server Agent (in Services), it stops directly with the following information: The SQLAgent$Sharepoint service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
When I try to start it from the SQL Server Service Manager: no reaction at all!
I was able to connect to SQL Server 2005 as a localhost by starting SQLSERVERAGENT in the Windows Services page. I was not able to attach the sample databases for the tutorials because of a compatibility issue with SQL Server 2000. I had both SQL Server 2000 and 2005 uninstalled and had SQL Server 2005 reinstalled to resolve this issue. SQLSERVERAGENT is no longer listed as a Windows service after 2005 was reinstalled. Any ideas what happened to SQLSERVERAGENT?
When I using Create Publication Wizard for database 'MY DATABASE', and setup 'MY SERVER' as the Distributor, then I get a message:
SQLServer Agent on 'MY SERVER' current uses a system acount, which cause replication between servers to fail. In the following dialog, specify a domain account for the Service startup account.
I don't understand this message (current in SQL Server Agent properties, tab Service startup account using System account)? Anyone can explain to me?
I'm running SQLServer 7.0. When trying to open the <server>ManagementSQL Server AgentJobs window from Enterprise manager, the SQLServerAgent terminates with the following messages written to the sqlagent.out file in the logs directory: 19.09.2000 10:01:43 - ! [LOG] Exception 5 caught at line 321 of file ..srcjob.c. SQLServerAgent initiating self-termination 19.09.2000 10:01:58 - + [188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop 19.09.2000 10:01:59 - + [098] SQLServerAgent terminated (forcefully)
We have a sqlserver 7 on windows nt 4. We'd just change a startup account for sqlserver agent to a not domain admin for security reason. The startup account for sqlserver service is still domain admin. We are now getting the following error every 5 second in our application event log.
"SQLServeragent security context does not have server-autorestart privileges"
Is there a way to get rid of this error without putting a domain admin as a startup account for sqlserver agent?
For some weeks now, SQLServeragent hangs after I restart the computer. Whatcould be a reason for this? I don't think I changed anything.The system protocol only says "SQLServeragent hung during start" (orsimilar - I have a German speaking system here).The application protocol says something like: "SQLServerAgent can not bestarted (reason: Connection to server can not be established. SQLServerAgentcan not start.)"MSSQL runs without problems, and when I start SQLServeragent manually, itruns without problems too.System: Microsoft SQL Server 7.00 - 7.00.1077 (Intel X86)Sep 6 2002 15:10:15Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)-mpe
I've gone through hundreds of posts here and on the Net. I'm creating an ssis package to access my db on my desktop. I then save a copy as "Test" on the msdb database on our sql 2005 box.
Try to create a job and I'm getting nowhere. My SQL Server Agent account is a member of local Administrator group and a member of the domain.
Now what I noticed is if I run the dtsexec from the command prompt and use the command line string then it works. Just seems like I'm not able to run anything from the SQL Server>>Jobs interface.