I have a problem with a server where for some reason when it is rebooted the SQLAgent service does not start automatically. You have to go into control panel, services and start it, even the it is set to Automatic.
Thanking in advance for any ideas??
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
I installed SQL Sp2 and at the same time took Carbon Copy off. No when the machine comes up neither SQL Server or the Agent will not come up. If I go to Service manager I can start both just fine. Nothing in either log to show why. Anyplace or any thoughts
View 2 Replies View RelatedI am a beginner with regard to SQL Server, having previously used Access 2000 databases in my programs.
Recently I installed VB 2005 Express and SQL Server 2005 Express on both my desktop computer and my laptop and have been working at migrating one of my earlier programs, written in VB6 /Access 2000, to VB Express 2005.net/SQL Server 2005.net.
Whilst my desktop version works well, I found that, for some unknown reason, SQLEXPRESS refuses to start automatically on my laptop, despite the fact that it is set that way. (It will start if I open the Configuration Manager and start it from there.) Since the configuration settings on my laptop are the same as those that work on my desktop, I cannot understand why the laptop version doesn't work.
Has anyone any ideas?
NewBarr
I have installed reporting services from SQL Express SP1 package. OS is Windows 2000 SP4. Just after installation "Reporting services" service has StartMode=Automatic and LogOnAS=LocalSystem as shown in SQL Server Configuration Manager. When system is rebooted reporting services state is Stopped and there is 2 errors in System log:
1. Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (REPS) service to connect.
2. The SQL Server Reporting Services (REPS) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
If i select "start" from service's context menu then it starting normally and it's state becomes Running.
What can i do to make reporting services starting automatically on system load?
Hi all
I have a mainteenance Server,SQL Server 2000 Installed on that server,every day some time in mid-night Agent it self stoping
What may be the reason...where I have to find out reason for stop.
Any advice and Help is appreciated.
Hello all,
We are deploying an application using SQL Server Express to a wide variety of desktop and laptop machines. We are currently trying to decide whether we should install the SQL Server instance service to start automatically at startup or not. In the latter case, our application would start and stop the service.
Starting automatically will make our app load more quickly, which is important to our users. However, our support team is concerned that leaving the service running will leave our databases vulnerable to becoming "suspect" if, for example, a laptop user's battery dies suddenly. Of course this will always be a problem if the app is running, but our support team believes that having the service running all the time will increase the chances of this happening. One reason for their concern is that an older version of the software used MSDE which was running all the time, and they saw a good number of suspect database issues.
What is the best practice for leaving the service running, especially when there are a lot of laptop users?
Thanks,
Ben
Hi, I have setup a replication between two servers. And sometimes due to network connection problem, I get error message like :
The subscription to publication 'pub_1' is invalid.
After 10 retries, if connection cannot be made successfully, the Merge Agent will stop running.
How can I start the Merger Agent automatically after it has been stopped?
Hi,
I've created a stored procedure that creates a script to create a number of objects within the database (based on what existing objects are in the database). From Management Studio, this works fine, and the output is exactly as I want it.
I'm now trying to create a job that will execute this stored procedure, and deposit the results into a file somewhere on the server. When the job runs, the script is created in the correct place and is essentially ok.
However, there are a couple of questions I'd like to ask.
Why does SQL Server Agent put a header at the top of the output file? I was hoping to be able to use that output file 'as is' and execute it automatically to recreate my objects when required. (Obviously, I can manually remove the header, but this is an inconvenience in this situation). How do I stop it?
Also, when executed from SSMS, the output is correctly line-spaced. But, the output from the scheduled job adds an extra line between each line of text, which is, again, inconvenient. Why does it do this, and how can I prevent this (again, without manually editting the output)?
Any thoughts and help greatly appreciated.
Cheers
Simon
I have a ssis package that has multiple large lookups without memory restriction. When running the package manually from SSMS on the same server it runs on when running automatically under the job agent, the package errors out when the server memory gets depleted by the loading of the large lookup reference data. One of the messages I get is
"An out-of-memory condition prevented the creation of the buffer object. "
Anyway, the package runs successfully when it runs automatically under the job agent.
I was curious as to why the above happens. Is that a bug or is the run time behavior different under these 2 environments by design.
js40
Hello everyone,
Any ideas of how to start a SQL Agent job, from OTHER-THAN Enterprise Manager !!!
Does Microsoft provide any stored procs, extended procs or any SDK that can help me force-start a scheduled task ?
There has got to be a way, coz' Enterprise Manager is doing it !!!!..
Any help is greately appreciated.
Thanks..
I changed my server's service account to Domainsqladmin and the service started successfully.
I did the same for SQL Agent but the service starts and stops. In Event Viewer saw this error:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
I checked Logins under under security in SSMS and the Domainsqladmin is a member of SysAdmin roles. What's wrong?
Canada DBA
I'm trying to set up SQL 7 for replication, so I set SQLAgent to start automatically, same as SQL Server itself. SQL Server starts fine, but SQL Agent "fails to connect in a reasonable time" according to the Event log (3000 milliseconds).
Can you suggest how I go about fixing this? They both are using valid logins, so I don't know what else could be wrong.
Advice appreciated!
Arthur
hi
when i try to start sql agent hang then mmc
i look the log and the problem is the mail profile
i try remove it from the property of sql agent but this hang the mmc too
can i remove this with tsql?
thanks
In attempt to run the SQLServer Job Agent, the following error occurs:
An error 1068 (the dependency service or group failed to start) occured while performing this service opertion on the SQLServer Agent Service.
An user a/c with Administrator rights is assigned to the SQLServer Agent Service upon setup.
Any idea what is causing it?
Thanks in advance,
Ben
We restored a database with replicated tables. Now, the Log Reader Agent will not run. This displays:
"The process could not execute 'sp_repldone/sp_replcounters' on 'ourservername'."
In Error Details for the agent:
"The process could not set the last distributed transaction."
And, from the logs:
"ForwardLogBlockReadAheadAsync: Operating system error 998(Invalid access to memory location.) encountered."
Does anyone know how we get the Distribution database and the Log Reader running again?
It is only affecting Transactional replication (not snapshot or merge).
Hi guys,
I'm trying to set up merge replication between a SQL Server 2000 SP4 / Win2k box and a MSDE SP4/WinXP box and I'm finding that the initial snapshot isn't being produced.
The SQL Agent runs as a windows user that has admin privileges, the snapshot agent impersonates the SQL Agent. The SQL Server login for the agent account has the server role "System Administrators" and database access to all db's.
When I turn on logging and try to start the agent, the following is written to the log:
Microsoft SQL Server Snapshot Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: SVRName-POS-POS_Test_Suburb-1
Connecting to Distributor 'SVRName'
SourceTypeId = 5
SourceName = SVRName
ErrorCode = 18456
ErrorText = Login failed for user 'SVRNameSQLAgent'.
The process could not connect to Distributor 'SVRName'.
Most of the posts I've seen regarding problems like this are due to subscriber authentication issues (not up to that, this is the initial snapshot) or windows/domain user permissions.
Any ideas what else it might be?
Hi,
I have installed the MSDE and use mixed mode authenticaton.
The SQL Server Agent will not start due to login failures.
Normally, I would use the Enterprise Manager Managment wizard to
correct the System Account and Connection Credentials.
Can anyone tell me how to achieve this using OSQL?
Thanks
We came across a biggg issue with SQL Agent service on one of our SQL Server 2012 production servers. Suddenly, it stopped working. So we just thought of disabling and enabling the service, but once we disabled and try to set automatic (before starting it), gives us error message "The Remote Procedure Call Failed [0x800706be]".
View 1 Replies View RelatedWe are having problems w/ our agent. When we try to start it in computer management, it will say the agent started then stopped because it has nothing to do. In surface area config, when we try to start it it times out. Does anyone have experience with this? We are desperate. Thanks!
View 3 Replies View Relatedhi
i have start sql server agent then dispaly following error message
(The system cannot find specified path) occured while performing this service operation on the sqlserveragent service
Straight from the sqlagent error file: (the username and login I'm providing is correct. for testing purposes only its and admin account and works on another instance)
2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001]
2007-05-14 15:12:07 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-05-14 15:12:07 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-05-14 15:12:07 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001]
2007-05-14 15:12:38 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-05-14 15:12:38 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-05-14 15:12:38 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2007-05-14 15:12:39 - ? [098] SQLServerAgent terminated (normally)
I cannot run SQl Server Agent service. Each time I try I get these 2 errors
Event Type:Error
Event Source:SQLAgent$MY_INSTANCE
Event Category:(2)
Event ID:17310
Date:18/06/2007
Time:09:27:49
User:N/A
Computer:MY SERVER
Description:
A user request from the session with SPID 53 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
Event Type:Error
Event Source:SQLAgent$MY_INSTANCE
Event Category:Service Control
Event ID:103
Date:18/06/2007
Time:09:27:49
User:N/A
Computer:MY SERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent cannot start because the msdb database is not set to a compatibility level of 70 or higher).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I am on SQL Server 2005. Do you have any ideas what might cause it and how to fix it?
Chris
I have a SQL Server 2000 that failed to start after a Windows reboot.Agent properties are checked to auto start if stopped. Under the AgentError Log, I have the following data:Information:SQL Agent stopping because of Windows shutdown.SQL Agent terminated normally.Error:SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.Logon to server(local) failed.Help apprecaited. ThanksFrank*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
View 2 Replies View RelatedI cannot run SQl Server Agent service. Each time I try I get these 2 errors
Event Type: Error
Event Source: SQLAgent$MY_INSTANCE
Event Category: (2)
Event ID: 17310
Date: 18/06/2007
Time: 09:27:49
User: N/A
Computer: MY SERVER
Description:
A user request from the session with SPID 53 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
Event Type: Error
Event Source: SQLAgent$MY_INSTANCE
Event Category: Service Control
Event ID: 103
Date: 18/06/2007
Time: 09:27:49
User: N/A
Computer: MY SERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent cannot start because the msdb database is not set to a compatibility level of 70 or higher).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I am on SQL Server 2005. Do you have any ideas what might cause it and how to fix it?
Chris
HELLO TO ALL OF YOU
IS THERE ANY SQL COMMAND IN ORDER TO START SQL AGENT ?
THANKS IN ADVANCE
The SQL Server Agent process is running. When I use EM to start a database integrity
check job, it fails with an error message of 22029 and the following:
[LOG] SQLServerAgent security context does not have server-autorestart privileges
I can not find error 22029 in Books on Line. I will go to Microsoft Knowledge base
and research this problem.
In the mean time if someone can help, it is much appreciated.
Thanks to all.
I need to start SQL Server Agent so that I can run scheduled jobs. I am running SQL Server 7.0 with windows NT 4.0 service pack 4. When I try to start the agent I get the following error
Error 22003: StartService() returned error 5,'Access is denied'
Does anyone have an idea as to why this is happening?
Any help with this problem would be appreciated.
Thanks
Phil
hi guys i keep getting this error when trying to start the sql server agent service.
"The SQLSERVERAGENT service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service".
the SQL server service starts fine and i tryied starting the agent with the same user but it fails still.
Any ideas?
Thanks.
Hello everyone! We had an issue this week where SQL Server Agent did not restart automatically. Weekly maintenance runs on the server each Sunday in which a reboot of the server occurs. Both SQL Server and SQL Server Agent are set to auto-start when OS starts. SQL started fine, but SQL Server Agent didn't.
Anyone know of a reason why SQL Server Agent wouldn't have restarted? Also, does anyone know of a way to set something up that would alert me (through email) if this service hasn't restarted?
Thanks in advance,
Lance
When l try to start up sql agent on a remote server l get the following error. Error 1722 RCP Server is unavailable. How can l fix that.
View 1 Replies View RelatedAs my sql agent is not starting due to XP's are disabled . when I ran the sp_configure with override and changed to 0 to 1 when I am starting the agent the configured value will be back to again 0 and in logs.Waiting for SQL Server to recover database 'msdb'...ODBC Error: 0, Invalid character value for cast specification [SQLSTATE 22018]
View 1 Replies View Related