Starting sql agent manually - operating rules

Hi We run std 2008 r2. Today after overriding the 1st step's behavior in a sql agent job to end and report success after completing successfully, I
1) rt clicked "start at step..." (saw the turning green arrow on rt pop up immediately)
2) highlighted 1st step on left pop up and then clicked ok, that made left pop up go away
3) perhaps incorrectly clicked ok on rt pop up where green arrow shows
I don't see anything in view history for that job.
But yesterday when it failed same smoke test I saw (and continue to see) that failure entry in history.
Before clicking ok on rt pop up I saw "success" in step 1 on that pop up which was way too fast for the pkg it calls.
I see evidence in the pkg's flat log file that it at least started but I don't see any evidence that the log is growing which makes me think I shouldn't have clicked ok on the rt sql agent pop up.
I did what I could to look for evidence in running pkgs on the IS server that the pkg is still running but cant come to a definitive conclusion.
What are the rules and behavior when it comes to that rt popup where the green arrow revolves and someone is starting a sql agent job manually? Is it synchronous or asynchronous with its spawned ssis pkg? If its synchronous and I'm not supposed
to touch it while its running, how do I know when its done if it shows success in the status column right away?

Is it possible the Job is still running? Run the command below to see if it is still exectuting
EXEC msdb.dbo.sp_help_job
@Job_name = 'Your Job Name'
https://msdn.microsoft.com/en-gb/library/ms186722.aspx
Please click "Mark As Answer" if my post helped. Tony C.

Similar Messages

Automatically start SQL Agent service after SQL Server service fails and starts.

Hi!
I have SQL Server 2008 R2 with two main services - SQL Server and SQL Agent.
I'll try to describe my situation. It happens very occasionally, but sometimes SQL Server service terminates unexpectedly. It's my log:
09/13/2013 10:46:21,Service Control Manager,Error,The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
09/13/2013 10:46:21,,Error,[359] The local host server is not running,,,,
09/13/2013 10:46:22,MSSQLSERVER,Error,The MSSQLSERVER service terminated unexpectedly.,Server,1073760843,,
09/13/2013 10:46:22,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #1)...,,,,
09/13/2013 10:46:27,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #2)...,,,,
09/13/2013 10:46:32,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #3)...,,,,
09/13/2013 10:46:32,,Error,[140] AutoRestart: The MSSQLSERVER service could not be restarted after 3 attempts,,,,
09/13/2013 10:46:32,,Warning,[360] SQLServerAgent initiating shutdown following MSSQLSERVER shutdown,,,,
As you can see, SQL Server service terminates unexpectedly. Then SQL Agent service tries to start SQL Server service. After unsuccessfully attempts to start SQL Server service, SQL Agent service stops itself. I have the option setting in SQL Server
service to start itself after unexpectedly stop within 2 minutes and it is works well. But I have to start my SQL Agent service after this manually. Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly and in this case I just want
to make the settings to start both of my services SQL Server and SQL Agent automatically after this. How can I set up this? How can I make my SQL Agent service starts after SQL Server service?

Hello,
SQL server agent service depends on SQL server service so unless SQL server service comes online agent will not come online so agent is depended on SQL server not the other wise.
Now is your server 2008 R2 patched to latest service pack (SP2).If not please upgrade it to latest SP.Some fixes are there in Sp which will subside this issue.Can you paste output of
select @@version
>>Then SQL Agent service tries to start SQL Server service.No this is not the case
>>Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly
Did you checked sql server errorlog and windows event log completely.Please do so and paste if you find some more info
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

The SQL Agent service is not running. This operation requires the SQL Agent service. (rsSchedulerNotResponding)

Hi,
I have started sql agent service on the SQL server but I still cannot subscribe. I have followed few instructions but no joy.
Can you please help?
Thanks,

Hi Mo,
According to your description, you want to subscribe a report with E-mail delivery extension, right?
In Reporting Services, since the E-mail delivery extension is not configured by default, if we want to subscribe reports with E-mail delivery extension, we should specify E-mail settings in Reporting Services Configuration Manager. Besides, we should specify
advanced settings in rsReportServer.config file. In your scenario, please make sure you have configured the E-mail delivery extension correctly. For more information, please refer to this article:
Configure a Report Server for E-Mail Delivery (SSRS Configuration Manager).
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Starting ssh-agent on login

ssh-agent is a blessing for convenient yet secure remote access, but the standard tool to start it up on login is in my opinion overly complicated. Keychain is a script in more than 1500 lines of code for doing essentially what I do in 8 lines. It does of course have tons more features, but I don't see any reason for all of that. Here's my /etc/profile.d/ssh-agent.sh, I hope somebody finds it useful:
# If the directory ~/.ssh/agent exists, ssh-agent is started automagically.
# The script first checks whether $HOSTNAME-sh already contains information
# about a running ssh-agent process, in which case nothing further is done.
# When necessary, which should only be once per reboot, ssh-agent is started
# and the two important variables are defined in $HOSTNAME-sh for use by
# future login sessions.
# Tip: Put '. /etc/profile' in your ~/.xinitrc and ~/.xsession
# This is a good idea not only because of this script.
if [ -d $HOME/.ssh/agent ]; then
[ -f $HOME/.ssh/agent/$HOSTNAME-sh ] && . $HOME/.ssh/agent/$HOSTNAME-sh
if ! [ -S "$SSH_AUTH_SOCK" ]; then
eval `/usr/bin/ssh-agent` > /dev/null
echo "export SSH_AUTH_SOCK=$SSH_AUTH_SOCK" > $HOME/.ssh/agent/$HOSTNAME-sh
echo "export SSH_AGENT_PID=$SSH_AGENT_PID" >> $HOME/.ssh/agent/$HOSTNAME-sh
fi
fi

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by BRETT GASTON ([email protected]):
After countless hours, I can get the command ./lsnrctl dbsnmp_start to start the Intelligent Agent. However, if I execute the command ./dbsnmp & the Intelligent Agent will start and I can then use dbsnmp_status and dbsnmp_stop as normal. I have tried relinking, reinstalling, deleting log and config files to no avail. Has anyone else had this problem?
Brett<HR></BLOCKQUOTE>
to start intelligent agents manually
$ lsnrctl
lsnrctl> help
dbsnmp_stop
dbsnmp_start
dbsnmp_statusd
lsnrctl>dbsnmp_start
lsnrctl>exit
or .........
lsnrctl dbsnmp_start # to start
lsnrctl dbsnmp_stop # to stop
lsnrctl dbsnmp_status # to view status
good luck
null

Unable to start SQL server agent service

hi,
We have 2 Node SQL Cluster that was working fine. Then We migrated the Linux DNS to Windows DNS successfully.Now restarted the SQL Server after it when we try to start the SQL Server Agent service its says the below msg while machine name and cluster
entries are in windows dns and resolving the IP to name and name to IP
Error msg: The MSSQLSERVER 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." error message.
But whenever we set the Linux DNS Server ip in SQL Servers then it successfully starts the service. Now i want to know why its happening and what are the requirements or DNS entries/SPN which we missing when we migrated the linux DNS to windows
dns
Sagar

I was experiencing this issue or one just like it on one of our SQL clusters (SQL Server 2008 R2, two node).
The fix for us was the database Security Login for: NT SERVICE\SQLAgent$<instancename> was missing. The actual service account assigned to the SQL Agent service was a valid domain account and we had the credentials correct in the service
configuration, so no changes were needed there.
Using SQL Server Management Studio we manually added this BUILT IN account ( NT SERVICE\SQLAgent$<instancename> ) to the instance, and then assigned it user role = sysadmin (to go along with the default role = public).
Once this was done, we tried to restart the clustered SQL Agent service and it started and remained started.
Hope this helps someone, we spent over a day pouring over the installation trying to find the cause.
This worked for me, thanks:-)

Error 17058 Unable to start a service account on MSSQLServer and SQL Agent

hi
I am intalling SQL 2008 standard with SP1 on a Windows Server 2003 R2 SP2.
I installed as "local service account" for MSSQLServer (SQL database engine) and SQL agent.
But I want to change to "service account" as [domain\svc_XXX] for MSSQLserver and SQL agent.
I add the [domain\svc_XXX] in local security policy - "Log as a service"
and also add in SSMS - Security - New Login (windows authentication.
When I started the MSSQLserver and SQL agent using the [domain\svc_XXX], I got an error 17058. Initerrlog: could not open error log file." Operating system error=3 (The system cannot find the path specified).
I don't know where else to look at..
Also, how do I find the cumulative service pack for SQL server 2008 standard?
thanks
Irene

Hi Irene:
By seeing your error message "When I started the MSSQLserver and SQL agent using the [domain\svc_XXX],
I got an error 17058. Initerrlog: could not open error log file." Operating system error=3 (The system cannot find the path specified)."
Please provide access to domain\svc_XXX on
log file directory.
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

Sql agent Operator not appearing in drop down box for job mail notification

I have created a new sql agent operator but operator is not appearing in the drop down box when setting up email notification for job failure?
SQL server 2008 r2
windows server 2008 r2
*Resolved deleted the existing job and recreated and then new operator was available in the dropdown box

Hi ghw,
Thanks for your post and glad to hear that the issue is resolved. Thanks for you posting your solution. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Notify more than 1 operator in a SQL Agent job

Hi Forum,
is there a way to notify more than one operator if a SQL Agent job fails?
TIA
Alex

Hello Alex,
If you are using a "maintenance plan" task "Notify operator" you can select several operators from a list.
In a SQL Server Agent job itself you can only add several operator for "warnings", but for the notifications like "finished" just one.
Olaf Helper ----------- * cogito ergo sum * errare humanum est * quote erat demonstrandum * Wenn ich denke, ist das ein Fehler und das beweise ich täglich http://olafhelper.over-blog.de

Maintenance Cleanup Task fails when executed with SQL Agent but dont if executed manually

Hello,
I have a job that fails with the following error if exectued via the SQL Server Agent but not if executed manually.
The error is:
Error: 2014-03-31 21:30:14.89 Code: 0xC002F210 Source: Maintenance Cleanup Task Execute SQL Task Description: Executing the query "EXECUTE master.dbo.xp_delete_file 0,N'\\erpfiles\b..."
failed with the following error: "xp_delete_file() returned error 2, 'The system cannot find the file specified.'". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly,
or connection not established correctly. End Error
I have checked and the user configured to run the SQL Agent has all needed accesses to the folder \\erpfiles\b....
Have you an idea to help me go further in my troubleshooting ? Or have you an idea to solve my problem ?
Thanks in advance

I think reason for this is the service account having no permissions on the specified folder path. Thats when you get this error most of the times. The user logged in might have access but please keep in mind that sql agent job makes use of service account
to execute the job which would still need access to the pat to delete the files
What you can do is add a proxy account and give it access to folder path and use it to execute the job
http://www.databasejournal.com/features/mssql/article.php/3789881/Proxy-Accounts-in-SQL-Server.htm
Alternatively you can give the service account access to the folder path.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

After change port for TCPIP PORT for default SQL Server instance (MSSQLSERVER), sql service and sql agent service did not started again

Hi
-when i install default instance MSSQLSERVER i added a domain account as a service account,
- when i change port for TCPIP PORT , and after sql service and sql agent service did not started again.
it thrown error
The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not start due to a logon failure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
but when i add domain\sqservice account in administrators group these services started,
1) here why this change behavior happened
2i changed the port 1500
adil

HI
the sql instance service is running with domain/sqlservice account ,
- i stopped the sql service service
- when i start it not started again and i found below error message
Domain and account: MOJPORTAL\spsqlservice
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this.
If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed,
check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7041</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2015-04-24T17:12:58.326973300Z" />
<EventRecordID>2177</EventRecordID>
<Correlation />
<Execution ProcessID="520" ThreadID="4044" />
<Channel>System</Channel>
<Computer>PORTALSQL1.mojportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">MSSQL$xSQL</Data>
<Data Name="param2">xxxL\spsqlservice</Data>
</EventData>
</Event>
adil

SQL Agent won't start

Hi,
I tried to start the SQL Agent on my SQL 2008 Server but got this error:
TITLE: Microsoft SQL Server Management Studio
Unable to start service SQLSERVERAGENT on server ACHSQL12. (mscorlib)
ADDITIONAL INFORMATION:
The SQLSERVERAGENT service on ACHSQL12 started and then stopped. (ObjectExplorer)
BUTTONS:
OK
Is there anything I should check?
Regards
Paul

You see the article for getting update :
Before you can start to use FILESTREAM, you must enable FILESTREAM on the instance of the SQL Server Database Engine. Enabling/configuring FILESTREAM is a bit different from configuring other SQL features because it involves making machine wide changes
and not only SQL instance changes. Also, FILESTREAM configuration has been changed for the February CTP to properly separate the Windows Built-in administrator and SQL administrator roles. In the November CTP, enabling/disabling FILESTREAM required Built-in
Admin privilege. Enabling FILESTREAM is now made up of 2 admin layers:
1-
The Windows configuration layer handles Windows related setup changes required for FILESTREAM. This requires built in administrator privilege. FILESTREAM settings in the SQL Configuration Manager (SQL-CM) represent this admin layer.
2-
The SQL configuration layer handles the setup changes required within the boundaries of the SQL instance. The SQL Admin can now use sp_configure/RECONFIGURE to handle this FILESTREAM configuration.
http://blogs.msdn.com/b/sqlserverstorageengine/archive/2008/03/03/filestream-configuration-and-setup-changes-in-sql-server-2008-february-ctp.aspx
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

SQL Agent wont start

I have recently bought a new a laptop running Windows 8 Pro and have tried to install SQL server 2008 and 2012 but all to the same effect the SQL agent wont start so I cant therefore connect to my database, I have tried everything on the forums but to no
avail I currently have 2012 version installed from this source: https://www.microsoft.com/en-gb/download/details.aspx?id=29062 first installing ENU\x64\SQLManagementStudio_x64_ENU.exe
then ENU\x64\SQLEXPR_x64_ENU.exe
The SQL agent wont start and currently returns with did not respond in a timely manner, the error logs dont present any useful information but can provide these if needed.
Please help I really need this to work if there is anything I have have missed please let me know and also if the is anymore information I can provide that will help thank you.

Hello,
As mentioned by jmcmullen, SQL Server Agent is a feature not available on SQL Server Express Edition.
Try the following workaround.
https://pianaro.wordpress.com/2012/12/05/how-to-schedule-jobs-in-sql-server-express/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Run SQL Agent Job in endless loop(When it's done, start over again)

Hi All,
There is an SQL Agent Job containing a complex Integration Services Package performing some ETL Jobs. It takes between 1 and 4 hours to run, depending on our data sources. The Job currently runs daily, without problems. What I would like to do now is to
let it run in an endless loop, which means: When it's done, start over again.
The scheduler doesn't seem to provide this option. I found that it would be possible to use the steps interface to go to step one after the last step is finished, but there's a problem using that method: If I need to stop the job, I would need to do that in
a forceful way. However I would like to be able to let the job stop after the next iteration. How can I do that?
Thanks in Advance...

Seriously I cant think of a reason for continuosly running a step like this
Do you mean you need to keep on polling db for something continuosly ?
If thats the requirement there's no need of continuosly calling the step
Instead of that you can include a loop with wait logic to keep on checking for your condition until it satisfies. You can WAITFOR clause for that
see an example here where I've implemented similar logic in SSIS
http://visakhm.blogspot.in/2011/12/simulating-file-watcher-task-in-ssis.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Cannot start SQL-SERVER-AGENT

Hellow friends. I have made a software that uses SQL-SERVER database at back end.. I want to use
express version of SQL-SERVER so i downloaded SQL-SERVER-2008 R2.. But i could not start
SQL-SERVER agent.
Can i still share database over the NEWTWORK
without starting SQL-SERVER-AGENT???

IS it possible to share database over a LAN using SQL server Express 2008.??
Or do EXPRESS-VERSION of sql server does not allow us to do so. ?
I find both 'yes' and 'no' answers when i google this question. Please i am in need of specific answer.
Just because you can get answer from forum dont start flooding it with same question.Below thread has same question see my reply, and reply to below forum only
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/eae75c95-6e98-413e-9e1d-206d95d893bf/cannot-start-sqlserveragent?forum=sqltools
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Agent don't start after a wrong reboot

While creating a SQL Agent job with his scheduling the server was rebooted for updates. The SQL Agent service does not restart with the following error. The job that was being created
there isn't in MSDB. What can you do?
thanks
Alessio
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
Server stack trace:
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.FindObjectExplorerFrame()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.GetObjectExplorer(Boolean activateWindow)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ShowError(Exception e)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Service.Start()
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ServiceActionHandler.EndInvoke(IAsyncResult result)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ServiceControlProgress.ActionCompletedHandler(IAsyncResult result)

Thank you. With your answer, from services.msc iI have seen thet the problem was on the account password.
Alessio
Hi theorangejuice,
I’m writing to follow up with you on this post. According to your description, there is an issue on the SQL Server Agent service account password. Was the problem resolved after modifying the password or selecting Local System Account option? If yes, I’d
like to mark this issue as "Answered". Please also feel free to unmark the issue, with any new findings or concerns you may have.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Starting sql agent manually - operating rules

Similar Messages

Maybe you are looking for