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?
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
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.
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.
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.
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?
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 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.
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
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 am not able to run more than 8 jobs in SQL Server using SQL Agent JOB.
Any ideas and suggestions.
Thanks in advance.
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...
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 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.
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 Replies View RelatedHello,
I had created a windows service using C#. I set its Startup Type as Automatic but it is not getting started automatically when my System Starts.
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?
Thanks!
when I run a package from a command window using dtexec, the job immediately says success.
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 3:37:41 PM
Finished: 3:37:43 PM
Elapsed: 2.719 seconds
However the Job is still in th agent and the status is executing. The implications of this are not good. Is this how the sql server agent job task is supposed to work by design.
Thanks,
Larry
Hi All,
I would appreciate any help here at all. I am pulling my hair out!
I am unable to start the snapshot agent or log reader agent from within SQL management studio. it fails on executing step 2 with unknown username or bad password.
I have checked all account details and they are correctly using my domain admin account. I can connect to SQL using teh same account and it also has sysadmin permissions.
If i copy the step 2 paramters and start from the cmd prompt (again logged in using the same domain account) they both start fine.
Any ideas would be gratefully received.
I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.
For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).
This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"
Any ideas???
Also this domain account is a member of
SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER
SQLServer2005MSAgentUser$ServerName$MSSQLSERVER
We just moved source server to newer, bigger box ... Windows 2003 and Active Directory ... Snapshot agent worked but distribution failed ... Same login as on older machine, login is sysadm, used DCOMCNFG to allow ability to launch process ... What are we missing?
View 4 Replies View RelatedI've read frequently how stored procedures we create shouldn't be named withsp_ since SQL Server will first check the master db before the current dbwhen trying to find the sp to execute. I always nodded and thought how Iwas glad I hadn't done that. For some reason it never clicked that UDFbehavior could be the same.I have several UDFs that start fn_... When I reference a UDF as dbo.fn_...does SQL Server check the master db for these and only upon not finding themcheck the current db? If so, is there a performance hit for this?TIA,John
View 2 Replies View RelatedHi,
I'm quite new to this forum. I've a fair experience in Databases and Programming. Now that I want to take a stride into Data Mining and Warehousing. Experts please suggest me where I can start from and any learning path ?
Best regards,
Markish
Hi Everyone:
I am just starting out on SSIS, and have the following business challenge that I would like to solve utilizing SSIS. There are two SQL Server data stores, one would be the source, and other would be the destination. I need to grab some data from store 1, and insert that data into store 2. Here are my questions:
1) Before i move the data to store 2, i have to check some criterias by callin some sps, and then the end result would need to be inserted into the destination database. Can anyone tell me how would i setup the control flow, to accomodate that in SSIS?
2) Can someone email me a sample package that does something similar?
I just need a starting point so i can build the design of my package. Basically i need to call three sps during the process to move data. First one will compile a list of all the records to process. Second one, will pick those up, make some calls to set some other parameters, and then finally insert it into some staging tables. Third one should simply pick up the data from staging tables, to a replica of those tables in the actual destination db. I would really appreciate if I can get some response to this post soon. Also, I would appreciate if you can point me in the right direction in terms of how to design this using SSIS. Basically i need a starting point control flow design(rough) to understand what control flow items would be used in this case. Thanks.
MA