SQL Server 2k Agent Service Stuck In Starting State
Mar 10, 2004
I have a Win 2003 server running 3 instances of SQL 2000 Enterprise.
The problem is I can only start 2 of the 3 Job Agents at a time, as the 3rd gets stuck in a starting state.
Has anyone struck this problem before?
Hi, we have a SQL server 7.0 on windows 2000 m/c,from yesterday onwards suddenly sqlserver agent is not starting,till then it was working fine. I tried to start SQL server agent manually and i got following message
"[241] Startup error: Unable to initialize error reporting system (reason: The specified module could not be found) "
Then i tried to start from services in controll panel,but i could't.
Then i checked event log ,found following error messages
Application log:
1) "The description for event ID(105) in soure(SQL Server Agent) can not be found. The Localcomputer may not havethe nessary registry information or message DLL files to display messagees from a remote computer.The following information is part of the event: The handle is invalid."
Event ID: 105 Source : SQLServerAgent Category: Disk
system log:
1)The Sql server agent service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Hi Folks, Can anyone amongst u solve my problem..When i try to start the Sql Server Agent..i'm given the following error meassage.. Could not start Sql Server Agent.Error 2140.An Internal Windows NT error. Please help me if anybody can.
Hi have you guys seen this error when trying to start the sql agent?
SQLServerAgent could not be started (reason: sqlserveragent must be able to connect to sqlserver as sysadmin, but '(unkown)' is not a member of the sysadmin rol.
What is this all about I can start the sql server service with the same account i'm trying to start the agent.
How can we start the SQL Server Agent without having physical acess to the server, I mean i have access to the EM which is installed on another server. How to start the SQL Server Agent , the login i use has sa rights ,
Hi, Running SQL 7.0 on NT4. When server boots the SQL Server Agent appears to start normally. NT Service starts, Event Viewer shows service is started, Service Control Manager shows service started.
However when I try to view a job or create a lob I get the following error:
Error 14258: Cannot perform this operation while SQLServerAgent is starting. Please try again later.
I am running windows 2003 and sql server 2005. i am following the directions in books online:
On the Start menu, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
In SQL Server Configuration Manager, expand Services, and then click SQL Agent.
In the results pane, right-click any instance, and then click Start.
A green arrow on the icon next to the SQL Server Agent and on the toolbar indicates that SQL Server Agent started successfully.
Click OK.
the problem is i have nothing in Services. there is nothing to expand. is it installed wrong?? or is there another step before this that i have to do??
We have SQL 2000 (SP2) , Our SQL server agent showing green light as started from EM , It is succussfully restarting from NT Services too . But When I open the properties of the jobs from EM its gives error message SQL DMO error " SQl Agent is starting , try later " . And in EM Next run Date & Time not available .
MDDB database is accessable & in Log file its recovered fully
I'm new to this forum but was wondering if you could advise me on getting the DB back to an accessible state. I tried restoring the DB but unfortunately I don't have enough disk space. The error message appeared instantly informing me of the lack of disk space. Now it says its in (Loading state) and I cannot access the DB. Is there anyway I can manually change it back??
I'm testing log shipping locally and had it running between two boxes. I tried to remove log shipping so on the primary I unchecked "Enable this as a primary database in a log shipping configuration" as per another thread. The primary stopped after a bit but the secondary never came out of the (Restoring...) state.
I'm obviously missing a step that needs to be run on the secondary because what I did wouldn't work if site A exploded but I can't figure out what the last step is.
I've been struggling to figure out how to set the "Log on as" login for a SQL Server agent that isn't a member of the Administrators group.
Is this even possible? No matter what policy settings I assign the the user, I get an access denied error when I try to start the SQL Server Agent service. If that user is part of the administrators group, there are no errors.
I have no problems with other services and "log on as" logins...
When our rep distribution services time-out (several times a day) some dba's just restart the service while others restart the rep job which starts the service. Are there any differences between these two methods? Does restarting the service inherit any changes made to the job's attributes?
When I start SQL Server Agent it's shutting down minute after starting. I tried to set Alerts to send email. After I configured Database Mail ,I was able to send test email , however after that SQL Server Agent started to misbehave.
Hi all, I do understand that it is highly recomended to have aserprate user (perfered a domain user account) for each of the SQL Server service and SQL Agent service. What is the reason behind that? (Someone told me to not run the service with an account that has a powerul privilegs! - I don't undrstanmd this point can you explain it please?) What is the diffrent between: 1- Local System account 2 -Network Service account
Hello there,This is a bit of strange one.My local version of SQL Server fails to start when I boot yet if Istart Enterprise Manager its started and working fine. ISQL or QueryAnalyzer is also not working.If I try and register the server by another SQL Server is not there. Methinks that the named pipes might be a bit broken but would appreciateany advise from people.ThanksGinters
We have windows server 2000 and sql server 2005 on the same machine with 15 clients. There was a power failure. The sql server is automatically stopped. When we tried to start the service we are getting the error as action failed please check application event log for errors.
This has happened for the 2 times, kindly tell me why this happens and what precaution we can take and is there any setting we are missing. Since I am newbie to sql server and windows server I am unable to solve this problem.
After the install is done I start the service form the command prompt using
start mssqlserver
I see that the SQL Server service has started under NETWORK SERVICE account!!! when the documentation i Read on MSDN says it starts in Local System account
I don't know too much about 6.0 so I need your help. I can't get to this database with a 6.5 enterprise manager either. The SQLOLE65.SQL script hasn't been run against the master database.
Well, here's the problem the Service Manager shows the services in a SERVICE STATE INDETERMINATE. No green, yellow red showing. I can't get into the database using enterprise manager because it says it's unavailable. However, on the enterprise manager it shows the database in a green (running state). So I'm uncertain whether to stop and start the database.
Has anyone every ran this SQLOLE65.SQL script so they can manage a 6.0 db thru a 6.5 enterprise manager? If so, please provide step by step instructions or warnings to look out for....
I upgraded my SQL 2005 Workgroup 2005 to SP2 and subsequently could not get the SQL Server service running. Turns out this was a problem because I had created separate folders for my data and log files. The distmdl.mdf and mssqlsystemresource.mdf files were in my data folder and distmdl.ldf and mssqlsystemresource.ldf were in my log folder. During SP2 upgrade a new distmdl.ldf and mssqlsystemresource.ldf were created in my data folder. I deleted the distmdl.ldf and mssqlsystemresource.ldf files in my log folder and then moved the newly created ones in my data folder into the log folder and all is well now.
The SQLAgent service was modified to login as a domain account. SQLAgent would not start. I made sure that the account was in the Admin group on the server, I setup the account as a System Administrator in SQL. I made sure that the network protocols in Client Network Utiliity and Server Network Utility where the same as other servers using the domain account. The message I'm getting is...
SQLServerAgent could not be started (reason: Unable to connect to server; SQLServerAgent cannot start).
I modified the properties for SQLAgent back to login as local account and I still get the same problem.
For three months I have be starting the SQL Agent using the following bat file
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'.
Starting this week the agent is not starting. This is the error message
10/26/00 6:25:36 PM - ! [000] Password verification of the 'SQLAgentCmdExec' proxy account failed (reason: A required privilege is not held by the client)
I am unable to get SQL Agent service to run under the same domain name that my SQL Server service is running under. It will start and continue to run when Server and Agent are both ran under the Local Account. But once the services are switched over to the domain account, the Server starts, but the Agent fails. The domain user has administrative rights on the server, along with admin rights to the SQL instance.
Here is the event log.
Event Type: Error Event Source: SQLSERVERAGENT Event Category: Service Control Event ID: 103 Date: 3/28/2007 User: N/A Computer: SQL2 Description: SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to the SQL Server as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
Any help would be greatly appreciated or links to threads with answers.
We have SQL Server 7.0 running on an NT 4.0 sp5 box. Whenever we stop the SQL Server Service, we get the message that SQL Agent will also be stopped. If we do this, all the services seem to stop fine, but when we try to start the SQL Server Agent Service back up, it won't let us. In order for it to restart, we have to reboot the server so that it starts 'automatically'. Does anyone have any ideas as to why this is?
How do you start SQL Agent? MS states not to start thru Service Manager as it may corrupt registry. There is no Resource for SQL Agent in 7.0 cluster. The service is down, need to start to get jobs to run. I've just checked (enabled) the properties so Agent will start on O/S reboot or start after Unexpected stop. How do I get it start in the meantime? Thanks!
Whenever I restart the Server , SQL server service is starting properly, but the agent is showing the green sign in EM ,agent Log also its showing its started. But in EM the jobs are not showing the next run time its showing ( Date and time not available). When I double click the jobs its showing the following error message Micorsoft SQL - DMO ( ODBC Sql state 42000) Error 14258 : can not perform this operation while SQL server agent is starting) FYI :This server contain the databases of SMS too .
Hi All, I have downloaded evaluation sample of SSRS for 120 days. But myproblem is that while creating setup the server components and Report server is not installed. Dut to that i cant run my report.It gives me error ,No report server was found . I dont know what i missed? Anybody help me? Its urgent.