Sqlserver agent is not running

[nisha23]

on reboot I could see two sql server agent running. What could be the reason?
If I give sql server agent as dependencies to run custom service.
Does it start again sql server agent or if it is running already it would take it automatically.
But what I have noticed that sql server agent is running in Event log and then custom service get failed as it could not do database work. Then later on another instance of sql server agent is started comes up in log event.

need help!!

 

[SQLBill]

You will have one SQL Server Agent for each instance of SQL Server. How many instances do you have?

Are the SQL Server Agent services set for AUTOMATIC start?

If so, go to Enterprise Manager, drill down to Management, right click on SQL Server Agent, select Properties.

On the General tab: which account are you using?

On the Advanced tab: what do you have set in the Restart Services section?

-SQLBill

 

[nisha23]

Checked it there is just one sql server instance.
There is one custom extended stored procedure in master database.
What I saw it started sql server one instance
then it started sql server agent. then again it started sql server agent after a while with same number.
between 10:53:50 and 10:55:11 I saw twice Sqlserveragent service getting started.
If I run my application at first event message of sqlserver agent service started, it fails.
After second event message it works.

Need help!!

Here are events
24/09/2003 10:55:11 SQLSERVERAGENT Information Service Control 101 N/A SQLServerAgent service successfully started.
24/09/2003 10:55:10 MSSQLSERVER Information (2) 17055 NT AUTHORITY\SYSTEM 8128 :
Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.

24/09/2003 10:55:07 MSSQLSERVER Information (2) 17055 N/A 17052 :
Recovery complete.

24/09/2003 10:54:48 MSSQLSERVER Information (2) 17055 N/A 3454 :
Recovery is checkpointing database 'abc' (39)

24/09/2003 10:54:42 SQLSERVERAGENT Information Service Control 101 N/A SQLServerAgent service successfully started.
24/09/2003 10:54:31 atkctrs Error None 3001 N/A Unable to open ATK device for R access. Returning IO Status Block in Data.
24/09/2003 10:54:26 MSSQLSERVER Information (2) 17055 N/A 17126 :
SQL Server is ready for client connections

24/09/2003 10:54:26 MSSQLSERVER Information (2) 17055 N/A 19013 :
SQL server listening on

24/09/2003 10:54:26 MSSQLSERVER Information (2) 17055 N/A 19013 :
SQL server listening on TCP, Shared Memory, Named Pipes.

24/09/2003 10:54:26 MSSQLServer Warning (8) 19011 N/A
24/09/2003 10:54:19 MSSQLSERVER Information (2) 17055 N/A 17834 :
Using 'SSNETLIB.DLL' version '8.0.194'.


24/09/2003 10:53:51 MSSQLSERVER Information (2) 17055 N/A 17124 :
SQL Server configured for thread mode processing.

24/09/2003 10:53:50 MSSQLSERVER Information (2) 17055 N/A 17162 :
SQL Server is starting at priority class 'normal'(1 CPU detected).

 

[SQLBill]

You didn't answer this question:

Are the SQL Server Agent services set for AUTOMATIC start?


If the SQL Server Agent service is NOT set for Automatic start, it will start each time a job begins and then stop when the job finishes.

It looks like it started for the recovery job. Then it stopped when the recovery was complete. Then it started when the extended procedure started. And stopped when the procedure completed.

-SQLBill