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?
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 ?
Where should I look into if above doesn't work ?
Thx.
Hi all,
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!
What to do to fire the job ?
regards, Ger.
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.
Regards, Iztok
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?
Thank you!
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.
Well the system administrator has no idea.
I am new at this.
please give me a hand.
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
hi all
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.
Any advise?Thanks a lot.
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"
Anyone has an idea, how to detect whether SQLServerAgent is started/running or not using vb code and if not how to start it programatically ?
Thanking you all in advance
JP
Dear all,
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?
Thanks,
bchu
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.
Any asssistance would be most appreciated.
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.
What could be the solution for the above error.
Thanks in advance
I scheduled jobs to take backups, but i found out that sqlserver agent is stopping by itself, what could be the solution for this problem.
Thanks in advance
Hello,
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).
Kindly give the suggestions at earliest.
dear all;
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).
please help
thank you
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.
Thanks.
Mark
Hi all,
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?
Thanks,
Tom
Can the SQLServerAgent be changed from running a system a/c to a domain a/c without re-installing?
If yes, is the place to change at
1) Enterprise Manager -> Management -> SQL Server Agent -> General tab
or
2) Control Panel -> SQLSERVERAGENTSERVICE -> Log On tab
Thanks in advance,
Ben
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)
What could cause this error?
Hi,
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?
Ted
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
View 2 Replies View RelatedI'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.
Please Help :)
Hi All,
I need a help here please.
I have a sql server 2000 running on windows server 2003. I run the services (MSSQLSERVER,SQLSERVERAGENT) under a local user which has no admin right. This local user named "sqlsvr".
The configuration that i used to make the "sqlsvr" able to run the services is in this web address :
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q283811
After im able to run the services under "sqlsvr". I added also permission "Impersonate client after authentication" on security policy for "sqlsvr" in order to make the clients able to connect to sqlserver through ODBC with "windows authentication" mode.
But the problem is, after i finished these configuration, i cannot make the SQLSVRAGENT run. And it shows an error message :
"SQLServerAgent started then stopped. Some services stop automatically if they have no work to do for example Performance Logs and Alert Service" and stops there. Then what we have to do is use the start to startup the service....€?
Please help
note : I must run the services under "sqlsvr" in order to comply with the security standard on my office.
Thank you very much
Best Regards
Felix Adhitya
I recently installed SQL Server 2005 and setup a database for one of the systems that I support as a DBA. After installation and the system, which has remote developers, was tested successfully, our security group performed a security scan on the SQL server. The scan revealed a few potential vulnerabilities. Below are the questionable items that the scan identified within the Windows User Rights Assignment. I believe the SQL Server installation assigns these system privileges to the SQLServer and SQLServerAgent accounts by default. I'd like to know how many, if any of these privileges, are necessary.
1) SQLServer and SQLServerAgent accounts have "Bypass Traverse Setting" privilege within Windows User Rights Assignment
2) SQLServer and SQLServerAgent accounts have "Log on as Batch Job" privilege within Windows User Rights Assignment. I realize I need this to schedule SQL Server jobs which run batch jobs and such, but any other reason to keep this privilege.
3) SQLServer and SQLServerAgent accounts have "Memory Quota" privilege within Windows User Rights Assignment
4) SQLServer and SQLServerAgent accounts have "Replace Process Token" privilege within Windows User Rights Assignment
Any guidance on this would be greatly appreciated.
Thanks in advance,
Jason Malasovich
SQL Server DBA
The 2005 Best Practices Analyzer (July 2007) contradicts Books Online about what account to run SQLSERVERAGENT under.
BPA says use Network Service Account, BOL explicitly says not to use Network Service Account:
BPA gives a warning saying "SQL Server Service [MY-PCSQLSERVERAGENT] In Unrecommended Account On Host [MY-PC]. We recommend that the service [SQLSERVERAGENT] on host [MY-PC] be run under Network Service Account. Currently it is designated to run under the account [SOMEDOMAINsomeaccount]."
BooksOnline says "Security Note: Because multiple services can use the Network Service account, it is difficult to control which services have access to network resources, including SQL Server databases. We do not recommend using the Network Service account for the SQL Server Agent service."
So who's right ? BPA or BOL ?
Hi all
Thanks for advance if u people giving solution to me
How can i generate SSrs with Sqlserveragent job
plz give me steps or send me any example
Regards
Kishore shetty
I'm not sure i was clear the first time. When the MSSQLServer Service is stopped and started, it stops the SQLServerAgent Service also. But when the MSSQLServer Service is started, it DOES NOT start the SQLServerAgent Service. I don't think this is configurable, so I was wondering if someone had a workaround (.bat file, service dependency, etc.).
TIA,
Mike
How do I configure the SQLServerAgent 2000 mail session? Do I need MS Outlook installed on the server?
View 1 Replies View RelatedDear All - The following message pops up when I try to execute SQL Agent Jobs - has anyone else seen this before, or know what it is ??
Box Heading is : Microsoft SQL-DMO (ODBC SQLState : 42000)
Message is : Error 22022: Unable to post notification to SQLServerAgent (reason Unknown)
Thanks,
Jazz.
SQL Server in on a ‘member’ server in my company domain (We took the ‘stand-alone’ option when installing NT on this server).
I have set up an NT domain account for SQL ServerAgent ‘Service startup account’ which is a different account than the NT domain account listed in the SQL Server Properties, Security tab, ‘Startup service account’.
I log on to this server with the login in the latter.
Replication is working OK, but my application log keeps filling up with the message “SQLServerAgent security context does not have server autorestart privileges”.
What have I done wrong?
Thanks,
Judith