October 28, 2005 at 8:47 am
"SQL Server Agent Started & Stopped. Some Services stopp because they have no work to do"
This is the error which SQL server agent is throwing when i try to Start it.
MsSQL server agent is running properly.
I'm trying to log-on with Administrative rights. As i want to do replication, the account should not run on Local System account.
Can anyone suggest any advice regarding this issue.
i have done replication successfully before. Thus, i hope this is not a replication issue, rather an account to setting of service accounts or SQL server.
my project is on the edge of deployment. Thas why, eagerly waiting for replies.(UserID=275407)
October 28, 2005 at 8:51 am
Review the agent log and OS system log for more info.
October 28, 2005 at 8:56 am
I've never seen that error before nor do I claim to understand what it is trying to tell you...
My question is this, though...Where are you telling it to run the SQLAgent as a non-system account? Is your SQL Server running as a non-system account? I've always set up both the MSSQL server and the SQLAgent service to run as the same user, so I'd recommend you do that, too. I'd also recommend that you make that sort of change through Enterprise Manager instead of the Windows Services window. The reason for that is Enterprise Manager will make sure that user has access to the DB, etc.
Mike
October 28, 2005 at 9:09 am
Thank You so much Mike for replying me instantly.
I'mdescribe my prob in detail....
i'm NOT running MsSQL server agent & SQL server agent on different accounts.
whenever i START sql server agent it throws the SAME error for the resp logins which i use (for eg: if i SET log on property as LOCAL system account OR if i log on as Administrator).
Thus, the error is so irritating that i even cannot try any option to troubleshoot it.
whenever i try to assign a job to SQL server agent, it says....
"SQL server agent has been stopped..... Start the SQL server agent...."
& when i try to start it, it says.....
"SQL server agent has been stopped because it has NO WORK TO DO......"
this is the scenario.....
& for replication, it requires SQL server agent running so that OTHER users can subscribe the publications.....
Awaiting for your reply.......
October 28, 2005 at 9:14 am
Can you log onto the database with that admin account you are trying to use?
October 28, 2005 at 9:19 am
Review the agent log and OS system log, and SQL Server logs for more info.
October 28, 2005 at 9:24 am
I've seen this before when the account the agent was running under didn't have the correct permission on the registry key when running the agent service undera domain account.
Check the registry keys for the agent and ensure that the user has full permission on that key and its subkeys
hth
David
October 28, 2005 at 9:26 am
i can log-on as Administrator to the Database......
October 28, 2005 at 12:02 pm
Did you take a minute to look at any logs?
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply