SQLServerAgent will not start

Question

SQLServerAgent will not start

H-122523

Hall of Fame

Points: 3667
More actions
May 24, 2005 at 7:32 am

#109714

Hello all,
I try to start SQLServerAgent service from SQLService Service Manager; it responds:
An error 5 (Access is denied.) while performing this service operation on the SQLServerAgent service.
The Windows System Log shows this:
The SQLServerAgent service failed to start due to the following error:
Access is denied.
Also starting from Computer Management console is not possible ('Could not start the SQLServerAgent service on Local Computer').
The configuration:
W2K Sp3 with SQL2K SP3 Enterprise edition
Intel P4, 1GB Ram
Login is domain account; on this machine 2 instances (default and one named), of which the sqlserveragent of the named instance is starting up without a problem.
Can anybody help me please?

Hans

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply

Gé Brander SSCarpal Tunnel Points: 4353 More actions · Answer 1

This is mostly an issue with NTFS rights or Account rights on the machine. The second is in my opinion not the issue due to the fact you use the same account for another instance on the same machine.

So it leaves some rights on file or directory. Or some rights in the registry. That can be an issue too.

Check your security setting for the errorlog file and database files.

H-122523 Hall of Fame Points: 3667 More actions · Answer 2

Thanks for the reply.

I checked the security settings of the folders of the default instance. The account that I use to run the agent under was not there, so I added them. I also checked the registry, and added the account to the security settings for the sql server entries.

Restarted, but still not possible to start the agent, while the named instance agent is starting without a problem.

Checked the error log for the default instance agent; apparently this agent has been working as there are entries, but the last entry is from August last year.

Windows System log:

The SQLServerAgent service failed to start due to the following error:

Access is denied.

Any folders (temp or other) that I made have forgotten to set security on?

Gé Brander SSCarpal Tunnel Points: 4353 More actions · Answer 3

Check if you are looking to the right location of the errorlog.

Maybe, the default location of the agent errorlog is changed...

H-122523 Hall of Fame Points: 3667 More actions · Answer 4

There are two locations where I found SQLAGENT.OUT, one for the default instance, one for the named instance. There are no other SQLAGENT.OUT files on this machine; also the entries in the registry are OK. I checked security on the folders and found these correct.

Gé Brander SSCarpal Tunnel Points: 4353 More actions · Answer 5

Well, i have no clue now...

Check the filesystem all the way from root till directory for security. That is all i can think of...

H-122523 Hall of Fame Points: 3667 More actions · Answer 6

I can't seem to find any difference in security settings between the named and the default instance, while Agent on the named instance works, so I changed tack.

I need the agent for running a transactional replication, so I attached the SQL database to the named instance and set up a replication. I thougth this a nice workaround , but the Distribution Agent is responding this error:

Could not find file 'C:\WINNT\system32\dbo.mdb'

The replication is between an SQL Server 2000 database and an Access 2000 mdb. I have defined some views that I want to have replicated to the Access database (which has the corresponding tables). I found some info on this matter ('do not use a reference to dbo in your views') but when I remove dbo from the view definition the Distribution Agent says it can't find the table.

Do you have any experience with replication/distribution?

Gé Brander SSCarpal Tunnel Points: 4353 More actions · Answer 7

Change the name of the database to anything else than dbo.mdb. Good luck, I think I can be of no help further down this road. Sorry.

H-122523 Hall of Fame Points: 3667 More actions · Answer 8

H-122523

Hall of Fame

Points: 3667

May 26, 2005 at 5:43 am

#561180

c7,

Thank you for your time .

tosscrosby Hall of Fame Points: 3140 More actions · Answer 9

H,

Any luck? I'm having the identical issue on one of my SQL servers here. Same error when I try starting the SQL Server Agent. Thanks.

Terry

H-122523 Hall of Fame Points: 3667 More actions · Answer 10

Hello Terry,

no luck yet, my last trick would be to add the account that I use for running the agent to the security list of the root folder for each hadr disk on the machine, and to the root of the registry.

I tried to look for the mysterious dbo.mdb, but to no avail. Browsing the internet I come across more references, people using vb, macromedia issues, all somehow having to do with connection to an Access database. Alas no Microsoft links there.

Hans

ITTILID Newbie Points: 5 More actions · Answer 11

first sqlserver version 8.00.534 (servive pack2)

i find this problem. but I install service pack 4 and it 's work

Sugesh Kumar One Orange Chip Points: 27311 More actions · Answer 12

check for permission on sql registry keys and default installation paths. That might have caused the access issue.

Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com

preeth.cs Valued Member Points: 58 More actions · Answer 13

Check out the "path to be executable” of SQL server Agent running , that is check as is it same path as SQL server service running.