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.
View 3 RepliesJust wondering if anyone knew if it was possible to create a SQL Server agent job that ran once every 30 seconds. I can't enter a value below 1 minute when editing the job schedule in Enterprise Manager.
Alternatively, I can create duplicate stored procedures and set one to run on the minute and one on the half minute. Thought there might be a better alternative to this though and I'll always have to be remembering to makes changes to both sprocs.
Thanks!
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.
can any one help me in this matter
Thanks in advance
Ananth
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.
When I am trying to start SQL Server Agent from Enterprise Manager I am getting:
" An Error 5 - (Access Denied) occured while performing this operation on SQLServerAgent. "
No sound explanation found in MSDN library.
How to resolve this matter, is there other than EM methods so start it?
Thanx.
Zaven
Hi
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 ,
Please help
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.
Has anyone seen this behaviour before??
Thanks in advance
Michael
Hi guys, I'm trying to figure out why i'm having issues with the SQL server agent trying to start.
the error i get is 14258 cannot perform this operation while sqlserveragent is starting. try again later. sql-dmo(odbc sqlstate:42000)
any ideas how to fix this. I start the service as a domain user that is an admin on the server. but when i run a job it gives me the above error.
thanks.
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??
I want to group my data into 15 minute interval . Below is my sample data and desired result set.
Create TABLE #HalfHourlyIntervals
(
OrderDate DATETIME,
IRevenue FLOAT,
TRevenue FLOAT
)
[Code] ....
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
Thankx in Advance
Sha
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...
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?
Thanks.
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Is any has the same problem ?
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.
Any suggestions would be appreciated.
Sidney Ives
Database Administrator
Sentara Healthcare.
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)
What could have changed on the Server?
When attempting to start SQL Server agent I get the following error:
"Error 1753 No End points available from Endpoint Mapper"
How can I solve this problem?
Thanks in advance for your time.
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.
I'm running SQL 2012 on a Win 2012 VM and the SQL server shuts down automatically after starting the SQL Server & SQL Server Agent Jobs.
View 9 Replies View RelatedWe 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?
View 1 Replies View RelatedHow 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!
Hi ,
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 .
Thank you ,
Shaji
SQL is generating dump every 1 min with error
EXCEPTION_ACCESS_VIOLATION reading address 0000000000000020 at
Server is running SP2 CU2.
I am not able to run more than 8 jobs in SQL Server using SQL Agent JOB.
Any ideas and suggestions.
Thanks in advance.
Hi
All my SSIS packages consistently take 1 minute to start when they are scheduled via the SQL Agent.
For example, a package runs in 20 seconds in the BI Studio. I transfer it to the SQL server and store it in MSDB. I then run it manually from SSMS - Integration Services and it takes 20 seconds. I then schedule it via a job in the SQL Agent and it takes 1 minute 20 seconds.
I can see from some simple logging that there is consistently a delay of 1 minute between the job starting and the package starting.
I have also switched every occurrence possible of DelayValidation to TRUE in all my packages and tasks. All this did was reduce the package run time from 27 seconds to 20 - the 1 minute delay still exists.
This happens on all my packages on all my servers. Any ideas.....?
Thanks
Hi,
I wonder if anybody can shed any light on this problem. I have a SQL Agent job which has three steps, each step runs an SSIS package.
The job is scheduled to start at 11.00 pm, which is does successfully. However, it has been taking between 2 and 3 hours to run, which is way longer than it should.
When I've looked at the logging, I've found that the although the job starts at 11.00 pm, the first package (in job step 1) does not start executing until about 11.30. It finishes in about 5 minutes, there is then about an hour delay before the second package (in job step 2) starts. This finishes in about 10 minutes, then there is another hour delay before the third package (in job step 3) starts.
I've tried configuring the steps as SSIS jobs, and also as cmd jobs using dtexec, both exhibit the same behaviour.
Any ideas about what could be causing this delay? The packages are stored in msdb on the same server as the SQL Agent job, if that makes any difference.
Thanks,
Sam
SQL agent is using NT login with all permission & agent and sqlserver using the same NT username . SA password has not been changed for more than one year.
The SQL Server agent log is showing "waiting to recover database". What could be the reason ?
------------
Ray Miao at 6/5/2002 8:13:38 AM
Double check with sql service manager. Did you change sa pwd?
------------
Shaji at 6/5/2002 4:36:16 AM
Hi ,
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 .
Thank you ,
Shaji
I want to give developers access to view SQL Job history, but not let them inhert permission to create local jobs like they get with the fixed server roles.
how can this be achieved? Or can it only be achieved by giving them access to the tables in msdb and querying them?
What sort of things would it interact with to justify having this ticked as the sqlserver.exe seems to be consuming all the CPU constantly and some suggestions have said that having this ticked can cause a performance issue.
View 3 Replies View RelatedI'm trying to create a report which will give me a break down of how many unique vehicles have been seen between two dates via a 15 minute interval and what Lane they were seen. My current script looks like this
SELECT l.Name [Name], count(l.Name) Total, p.Created
FROM PlateReads p
inner join Lanes l on p.Lane_ID = l.ID
where LicencePlate in (Select Plate from LPRnet_MelAir_C.dbo.TempVehiclePlates)
group by Name
Name being the Lane they were in and the Total being the amount of times a unique vehicle has been seen and p.Created being the date they were seen (thats what I need the interval powered off)
Ideally the output would look like this
16/03/201408:00 to 08:15Bus Lane 15
16/03/201408:00 to 08:15Elevated Road150
16/03/201408:00 to 08:15Public Pickup75
16/03/201408:15 to 08:30Bus Lane 13
16/03/201408:15 to 08:30Elevated Road120
16/03/201408:15 to 08:30Public Pickup55
All the way to 12/04/2014
I’ve got it so it says Lane and Count just can’t get the interval part
I have an odd one. I have a SQL job that doesn't have a schedule and is being run each morning. It is a legacy system and I am trying to document the data flow process and I am having a hard time tracking down where/what is starting the job. I see which user executed the job:
SELECT message FROM sysjobhistory WHERE job_id = 'jobid' AND run_date > 'yesterday'
Which is useful, but I want to know what is starting the job.
In one of my environments, I need to grant the ability to view all the logins and agent jobs to an account, but I don't want to give him "sysadmin" or "securityadmin".
View 2 Replies View Related