Sql server service has been started with a normal user who do not have any permission but he is a domain user.
The sql server service can be started successfuly in cluster
But if the Same user is used to start the SQL Server Agent service there is an error.What is the mininumum priviledge to
start a sql server agent in cluster. Why it cannot the domain user cannot be used to start the sql agent service.
I created a snapshot publication (the engine is SQL2005 and the compatibility is 2000).
I got this message:
"The agent could not be started.
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
SQLServerAgent Error: Request to run job REPLSM-6 (from User DOMcustuser) refused because the job has been suspended.
Changed database context to SM. (Microsoft SQL Server, Error: 22022)"
And when i'm trying to reinitialize the publication, I get this:
"Replication Monitor could not start the Snapshot Agent to generate a new snapshot. You must start the Snapshot Agent manually before the subscription(s) can be reinitialized..."
What can I do? Why it doesn't work?
thnx
The Agent has never been run occurred on Snapshot Agent Status-Replicationhow do I make it run successfully??
View 6 Replies View RelatedHi!
I have a small problem , but it's still a problem.
I have a SQL Server Agent job that runs a .cmd file. This CMD is logged to a textfile.
This process is locked, waiting for me to type a password, but I have nowhere to type that pass.
What I want to do is kill the process that i locking the logfile, because since the logfile is locked, the job cannot be started again (and it's a scheduled job).
The jobs status is 'Not Running'.
I have solved the problem by making the cmd write to another logfile, so the schedule will work, but the file is still locked, and I don't want to restart the server since it's a productionserver.
How to I find the process that is initialized from SQL Agent, and kill it?
Thanks!
Bix
i'm running a SQL Server 2000 SP42000.8.00.2039, developer.
i'm trying to setup a merge replication between the default istance and a named one of the same machine, using the same domain account for both publisher and subscriber.
when it comes to "start synchronizing" (right click on the subscriber merge agent), i found it disabled, just like it is running, but it is not (the icon shows a stop sign, even refreshing.)
The state is "disactivated". When i stop sync and start it again things don't change.
If i setup a "pull" subscription, i get a sequence of a message like "interface not supported" (a translation from italian "Interfaccia non supportata"): after 10 attempts, it stops.
i cannot find this error searching in internet, could you address me?
thanks in advance!
How to prevent the hang on the initator service broker if the target service broker is not started?
Our case has two service brokers (two databases), sometime, the target is need to turn off. But the sitation is the initator service broker (in fact, the message is sent from triggers) become hang, I want to prevent this case and continue to operation, and the messages should queue and will continue to send to target service broker when it startup. How should I do?
I have installed SQL Server 2005 Standard Edition for our Team Foundation Server install. I have verified the installation and all seems well, except that the Analysis Services service does not remain started. I get a message like "Some services stop if there is nothing to do." The Analysis service needs to be running in order for the TFS install to succeed. How can I get the Analysis Services service to remain started?
Thanks in Advance
We have a Process Task component setup in a couple SSIS jobs to call a command batch file to support transfering a file via Secure FTP to other servers and the process works fine if we start the SQL Agent job manually, however when the job is started via the scheduler, it fails with an exit code of 4. Even though there is a proxy setup on the agent job, is there a different user account being invoked by the scheduler??? We're on 2005 SP1 Hotfix 1 (2153). Thanks
Some more info...have found that if we leave a login session open on the server (login is the proxy account) the process works. It appears the issue is associated with a need to render/create a command window for the command line/batch process to run in and without an active windows session it fails....would seem to be that a product setup to run on a server in a batch mode would be able to work without this...is this the case? if so, how? Thanks.
Hi,
My SQLEXPRESS service suddenly gives me this error.
ERROR: The SQL Server(SQLEXPRESS) 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.
My OS is Microsoft Windows Server 2003, Enterprise Edition, SP2.
It all started when I restarted the system prompted by the Windows updates.
Please help. Its urgent as this is one of the important servers to be managed.
Thanks and Regards
Madhu
I'm not sure i was clear the first time. When the MSSQLServer Service is stopped and started, it stops the SQLServerAgent Service also. But when the MSSQLServer Service is started, it DOES NOT start the SQLServerAgent Service. I don't think this is configurable, so I was wondering if someone had a workaround (.bat file, service dependency, etc.).
TIA,
Mike
I have configured Alwayson HA setup as following environment and versions, and working fine to client side by connected with AG Listener.
Two Node WSFC setup. Node1 (Primary), Node 2(Secondary Replica). Normal quorum(Not shared disk)
Server Platform: HyperV
OS: Windows server 2008 R2 64 bit with SP1
RDBMS: MS SQLSERVER 2012 64 bit with SP2
when I am doing testing Failover method between two nodes. automatic failover not happened.
Just shutdown Node1 and try to connect at client side by using AG Listener name but not succeeded, also Cluster name and AG Listener name are not pinging, Second node2 cluster service is not started by automatically due to as below errors. So how will connect client and overcome this issues? Any modification need to be done on both side WSFC and AlwaysOn SQL? for achieving and automatic failover.
Cluster network 'Cluster Network 1' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Client side got connected once Node1 get started again also cluster services started.
Hi everybody
Error [364] The Messenger service has not been started - NetSend notifications wi
I am having this error from agent. Does anybody have any idea what this error means or is it sevear or not?
Thank you
asa.:)
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
Thanks in advanced!
CS4Ever
Whenever i change the SA password to anything else, my SQL Agent services
like jobs, alerts starts falling, and if i attempt to stop and then restart
sql agent service, it will not start again.
My server uses sql authentication for everything...
help...
thanks
vinod
Hello, I am having a problem with my sql server agent service not working. I have done some research from earlier postings and still having no luck with getting it up and running.
Problem:
"Could not start the SQLSEVERAGENT service on local computer. could be an internal Windows errow or service error.
2006-05-09 14:23:55 - ! [298] SQLServer Error: 6, Specified SQL server not found. [SQLSTATE 08001]
2006-05-09 14:23:55 - ! [298] SQLServer Error: 11001, ConnectionOpen (Connect()). [SQLSTATE 01000]
2006-05-09 14:23:55 - ! [000] Unable to connect to server '\PROBLEMTRACK'; SQLServerAgent cannot start
2006-05-09 14:23:55 - ? [098] SQLServerAgent terminated (normally)
I have reset the password for the 'sa' account and running it and got error: Error 18456: login failed for user Specify a different account to be used.
But when I try it only provides me with the 'sa' account.
My primary goal is to run some DMP ion the databases that I have on the server.
Any help would be appreciated.
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 RelatedWhat is the best way to monitor , if the SQL Server Agent is running or not and send out an EMail if the any of the SQL Server Services stops?
Thx
Venu
Here is an odd one:
I switched my SQLSERVERAGENT service to use the Local System Account.
I stopped and restarted the service.
Both the Services window and Enterprise Manager show the SQL Server Agent is running. But when I try kicking off a job I get the following message:
Error 22022: SQLServerAgent is not currently running so it cannot be notified of this action.
Any clues as to why the agent could be running, but not know that it is running?
Hi all,
I'm new to sql server administration so please show some understanding!
I installed sql server 2000 personal edition (upgrated to sp4) on an windows xp pro OS, but I cannot get the sql server agent service running. I get a message " the service did not start due to a logon failure". The server is my local pc, I'm using windows authentication and the login is "domain/loginname" where domain is my pc name.
Does it have to be installed on a server OS to have this service running?
Thanks George
I just learned I can deploy and schedule jobs to run SSIS packages (via job/sqlagent) without the Integration Service (agent) itself actually running alongside (or on) the server. (Double-click on manifest, deploy IS package to server, create job/job step to run IS package, watch it run even when integration service is completely disabled)
Other than convenient viewing, configuring, and RMC running w/in SQL Server Mgmt Studio 2005, why then do I need the integration service running on a production box at all? When do I really need the IS service itself?
In our (finance) world only (a) an act of God or (b) a DBA can touch production databases/servers. Allowing anyone to connect to yet another service - in this case, an integration service - to meddle w/ a package would be a no no, so...
1) Could I trouble someone for a concrete, critical reason why the DBA should enable it on a production server. Speed? Caching? Peace of mind knowing everything is piled onto and neatly running on the server?
2) On a more minor note, if I'm deploying a package to be housed solely w/in MSDB, is there anyway to prevent the prompt of a file location during deployment, i.e. the creation of an empty directory that would otherwise hold package dependencies if I were running it as a file?
We'd like to deploy only to MSDB (I know all the pros/cons w/r/t saving dtsxs to files v. msdb) and keep deployments clean (read: all in one place). DR is via SAN-to-SAN replication with, among other things, msdb cleanly getting replicated. We would very much like to avoid having to worry about (more) file/directories sitting out on a server share to be replicated to DR (it seems the default is to allow deployments to directories on the SQL server instance itself..ugh) Any architectural insights on this would be appreciated.
Kind Regards,
Jim
When I run sp_delete_job to delete the whole job inside,
will the job steps, job schedules and job servers of that job will be deleted automatically also?
so, do i need to run sp_delete_job only?
or need sp_delete_jobstep, sp_delete_jobschedule and sp_delete_jobserver also?
Hi,
If we were to assign permissions to a backup agent such as Backup Exec to backup the databases on the SQL server, what role would give the least amount but sufficient permissions to perform the backup? I know domain admin would make the agent a local admin and therefore allow it to back up the database but is there a role available to allow backup only?
Please note that I'm referring to a domain account used by Backup Exec to directly backup the databases rather than sql server agent.
Thanks.
what is considered best practice for privileges etc on the sql agent service account and long term need for that account to run ssis packages? I tried to understand and appreciate the article at http://www.microsoft.com/technet/prodtechnol/sql/2005/newsqlagent.mspx but felt like either it was overkill or I wasnt getting it.
I'm thinking of using SQL Server Agent Service for my PDA app. But, I want to use different accounts for SQL Server and SQL Server Agent Service. How can we do this in SQL Server 2005? Do we do this when installing it? Thanks
View 3 Replies View RelatedTo run a remainder service that shoots a mail once everyday to all users of a subscribed service satisfying a pre-determined criteria, I'm planning to use a Sql Server Agent Job. In the first step of the Job, I'll have a stored procedure that gets all the records matching that criteria & store it in a table.
In the next step, I want a Windows Service (as there need not be any interface & my project requires easy deployment & minimal manual intervention) to fetch the records from the above table & shoot mails to users of the subscribed service. Several thousand mails may have to be sent this way. In order not to strain Sql server & also avoid extended stored procedures due to safety reasons, I'm considering using this windows service.
I want to know
1) how to make the Sql Server Agent execute the Windows service?
2) abt code or resources on how to write a vb.net Windows service that will work through a recordset & send mails.
3) from a perfomance point of view, if this method is feasible? If not, what are the other efficient alternatives.
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.
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 RelatedHi,
When I click on SQL Server agent I get the "Unable to start service error".
It says serivce started and stopped.
Anybody having any clue on what's going wrong. Please let me know.
Regards,
HV
Am trying to run SQL Server Agent with a service account which is not in the Administrators group. Have done the following -
1. Removed the service account from the Administrators group on the machine
2. Assigned sysadmin privileges to the service account
3. Added it to the SQLServer2005SQLAgentUser$ComputerName$MSSQLSERVER role
4. Through SQL Configuration Manager assigned this account to the SQL Server Agent service
However, this does not start the Agent as a service. What is it that is missing?
I am trying to upgrade my default instance from SQL Server 2000 Standard to SQL Server 2005 Standard. I get to the service authentication window and hit my first problem. On that window, there is a dropdown box where you should be able to choose the default instance service AND the SQL Server Agent service and set the authentication information for both of those services. That's the way it is in my test environment. However, on my production server, when I click that dropdown box, only the instance appears, and not the agent. Why?
I tried the upgrade this past weekend and ran into this problem. After researching it and not finding anything out about it online, I decided to just go forward anyway since I had lots of backups and copies of everything. The upgrade appeared to go ok, but the agent service wouldn't start. It gave the usual message when you try to start a service that doesn't have anything to do, like the Performance Logs and Alerts service. When I looked at the agent in SQL Server Management Studio, it had (Agent XPs Disabled) next to it. So I researched this and found how to enable it. For some people online, this allowed them to start the agent service, but of course that didn't work for me. Finally in my research online I found that some individuals had a lot of missing system tables in their MSDB and Master databases after the upgrade due to some of the SQL scripts that are part of the upgrade process not running properly. So I compared my system tables and SP's against another SQL 2005 instance I have, and sure enough, there appears to be a lot of missing tables. It was at that point I decided to just restore everything and try again later.
My point in writing that second paragraph is to ask if that was all due to the fact that the SQL Server Agent wasn't listed in the upgrade wizard like it should have been? Or maybe the fact that it wasn't in that dropdown box was evidence of a deeper problem? Is it likely that if I do whatever it is I need to do to make the agent appear in the upgrade wizard that my missing system tables and agent service not starting problems would probably not be an issue anymore? And why would the agent not be appearing in the upgrade wizard?
Thanks for your help!
I have six stored procedures that I have to run hourly during the day. When I schedule them into separate SQL jobs (they must run concurrently), the percent CPU of Sqlagent90.exe process goes way up, eventually pegging out the overal CPU usage on the server. When I run the six stored procedures concurrently from query windows in SQL Server Management Sudio, the overall CPU usage stays very low.
Is there something about the SQL Server Agent that inherently adds CPU overheard? Thanks in advance ....
hi, can anyone explain, how to execute package with sql server agent:
the problem is::
i made a integration service package (in visual studio 2005). When I 'm in visual studio and do "execute" the package it works well. Then I build a dtsx file. When i double click on it, it opens and if i do execute, it works well.
I want to execute the package every week automatically. I write a job in SQL server agent, in Steps I choosed Type=SQL server Integration service packege, then General->packacge source -> file system, and then wrote where the dtsx file is (which was built). "Run as" I choose my user name.
then i'm trying to start a job, but it fails, and writes "The package execution failed."
What I'm doing wrong.
(sorry for my english)
The SQL Server Agent (MSSQLSERVER) service on server started and then stopped. If i Manually start the services also SQL Server Agent services are stopping automatically.Though I selected Auto Restart SQL Server Agent if it stops unexpectedly, The services are stopping automatically.TCP/IP protocol was enabled for port 1433.Are there any setup I missed?
View 5 Replies View Related