Sql server agent is not highlighting start and stop options

I configured snapshot replication , after that sql server agent is not highlighting start and stop options in instance.
But I can start & stop it in services.msc
how I can solve this?

Hi,
Can you post exact error message.
Also refer below article, may be similar issue like yours.
How to start SQL Server Agent when Agent XPs show disabled
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
Praveen Dsa | MCITP - Database Administrator 2008 |
My Blog | My Page

Similar Messages

What SQL Server Agent jobs are currently running and for how long

Is there a way to tell what SQL Server Agent jobs are currently running and for how long? View history isn't working in my case because it's only showing completed jobs. John Schroeder

You can use the "Job Activity Monitor" for doing this. Do the following steps. It will open up the Job Activity Monitor.
1.    In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
2.    Expand SQL Server Agent.
3.    Right-click Job Activity Monitor and click View Job Activity.
4.    In the Job Activity Monitor, you can view details about each job that is defined for this server.
In Job Activity Monitor page, we have column called Status. It will indicate whether job is executing or idle. Last Run column will give you the last invocation time of this job.
Use the following link for further reference.
http://msdn.microsoft.com/en-us/library/ms187449.aspx
Thanks,
Sateesh.
Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

SQL Server Agent Jobs- Not running

Team,
We have a production database hosted on SQL Server 2008R2 SP2(10.50.4000). We have application jobs which are scheduled and basically have packages called from this job. These jobs were running all good till yesterday and it has stopped working since yesterday
even though its enabled. Manual runs are successful. Other jobs are running fine.
Checked the Owner of these jobs and the account is SQL Server account which is a proxy account. It had enforce password policy. I have removed that and reset the password to original. However it didnt work.
The last change on this server was windows patching which was performed last week. Apart from that the SQL Server agent service was changed. This is a clustered environment.
The last resort is restart the agent, however would like to get some inputs before I perform this action.
Please let me know your valuable inputs.
Regards,
Sharath

If job is not executed at all, that is, there are no entries in the job history, check:
1) The job is enabled.
2) The schedule(s) is enabled.
3) The scdedule does not have an end date has has passed.
4) And that all other conditions on the schedule says that the job should run.
Erland Sommarskog, SQL Server MVP, [email protected]

Sql server agent not starting

I installed sql server 2008 r2 sp2
sql server agent is not allowing me to start it.
I run SSCM right click agent but start,stop menus are disabled

i have only one sql instance named SQLEXPRESS
The SQL Server Agent is installed with the Express Edition of SQL Server, but it's not a Feature of the Express Edition, therefore you can't start the Agent.
See
Features Supported by the Editions of SQL Server 2014
Olaf Helper
[ Blog] [ Xing] [ MVP]

SSIS Package Runs OK Manually But Not From SQL Server Agent...Permissions?

I have a problem where I have an SSIS package (SQL Server 2005) that won't run properly from SQL Server Agent, but it runs fine when kicked off manually from Integration Services -> Run Package or when run in debug from Visual Studio.
The first step in the package checks for the existance of a file via a script task. The script looks like this...
Code Block
Public Sub Main()
Dim TaskResult As Integer
Dim ImportFile As String = CStr(Dts.Variables("BaseDirectory").Value) + CStr(Dts.Variables("ImportDirectory").Value) + CStr(Dts.Variables("ImportFile").Value)
If Dir(ImportFile) = "" Then
Dts.TaskResult = Dts.Results.Failure
Else
Dts.TaskResult = Dts.Results.Success
End If
Return
End Sub
This script runs fine and the file is seen as expected when I run the package manually. But as a step in a SQL Server Agent job, it doesn't see the file.
The SQL Server Agent service is set to start up / log on as a Local System Account. I've also tried setting up a credential / proxy (using an account that I know can see and even move / rename the file) to run the job as but that didn't seem to help.
The package is being run from SQL Server (stored in MSDB) and is set to rely on SQL Server for sensitive information, so I don't think that's an issue; other packages are set up like this in terms of sensitive data and run fine.
Any ideas why my script can't "see" the file I'm looking at when it's kicked off by SQL Server agent? I've looked and looked...I can't seem to figure this out. I would really appreciate any help you might be able to offer up.

If the variables are fine, then I think it is very likely that this is security related. Since the Agent is running under the local system account, have you verified that the local account can access the file? When you tried the proxy account, are you positive that it was set up properly, and that the account had the permissions to read the file?
Another thing to check - is this a local file or is on another computer? If it is on another computer, make sure you are using a UNC path and not a mapped drive.

Agent statistics and SQL server agent

We have CUCCX 5.02 and CUCM 6.1
When agents try to look their "Agent statistics report" in CAD there is no data. And status of this report is "Inactive". All other reports are active.
In CCX "control center" I see that "CRS SQL server Agent - this service is invalid" and "Cisco Desktop LDAP Monitor Service - this service is invalid".
We have problem only with Agent statistics report. Historical reporting - work fine.
What could be the reason?

Hi
Please see this tech note in order to restore the services that have failed:
http://www.ciscosystems.com/en/US/products/sw/custcosw/ps1846/products_tech_note09186a00808278d8.shtml
Regards
Aaron
Please rate helpful posts...

SQL Server Agent

Hello
I am using SQL Server 2012 Express with advanced services however I cannot connect to the SQL Server Agent. The Instance is local and the SQL server Agent service is installed and has the correct permissions.
According to http://www.microsoft.com/en-gb/download/details.aspx?id=29062 SQL server agent should be available.
Reporting services is greyed out and should also be available in this version.
Regards
Ray

Hello
I am using SQL Server 2012 Express with advanced services however I cannot connect to the SQL Server Agent. The Instance is local and the SQL server Agent service is installed and has the correct permissions.
According to http://www.microsoft.com/en-gb/download/details.aspx?id=29062 SQL server agent should be available.
Reporting services is greyed out and should also be available in this version.
Regards
Ray
SQL Server agent is not present in express edition.YOu might see agent XP in sp_configure but acctual SQL server agent is not present.This feature is not provided by Microsoft for express edition.There is nothing mentioned about agent in link you posted.It
does have reporting feature
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Execution of a batch file within SSIS fails in Sql Server Agent Job

Hi All,
I have an SSIS Package, which simply runs a batch file , the code for the batch file is
MOVE \\cambosnapp01\Claims\Analytics\NICB\CurrentAlerts\* \\cambosnapp01\Claims\Analytics\NICB\AlertsArchive
If i run the SSIS package manually it runs fine and moves all the files, however if i run the package through a Sql Agent Job it fails with the following error
The directory "\\Cambosnapp01\Claims\Analytics\NICB" does not exist
This is where the batch file is located, i am not able to understand if the SSIS package is running fine then why not the sql agent job?
I also tried to create a sql agent job using Operating System(CmdExec) and i copied my batch file code in the command i am running it as SQL Server Agent Service Account , and here it fails as
Executed as user: CAMELOT\svcDW. Access is denied. Process Exit Code 1. The step failed
Does this mean this user doesnt have the rights to excute a batch file? how did this user even come up i am not running it from this user i am running it from SQL Server Agent Service Account . I dont know who is that user and if he even has the rights to
execute a batch file.
Can someone please help me with any solution for this? either first way or second way anything works fine for me.
Thanks

Hi SQLDEV,
According to your description, you are experiencing the issue "The directory "\\Cambosnapp01\Claims\Analytics\NICB" does not exist" when run the SSIS package
in SSMS by using SQL Server Agent, right?
In your scenario, since you can run the package in SSDT manually. So as per my understanding, the issue can be caused by that the Services Account of your SQL Server Agent do not have the permission on that folder. To avoid this issue, you can set the folder
permission for your SQL Server Agent account or change the services account to an account who have the corresponding permission. Please refer to the link below to see the details.
https://msdn.microsoft.com/en-us/library/bb727008.aspx
https://msdn.microsoft.com/en-us/library/ms345578.aspx
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Starting and Stopping an FMS Instance?

Hi there,
I'm sorry if this issue has already been answered somewhere else, but my Google skills are up to par and I was unable to find a documented resolution to this problem within the last few days. Opening a new topic was my last resort.
I am designing a live-streaming system for a client. We've been running an instance 24/7 for the last month and my client just received an enormous bill for that.
Basically we need to be able to start and stop the instance as needed. When I check the checkbox next to it in the Management Console and click on Instance Actions, Stop and Start are greyed out. I am allowed to Terminate and Reboot the instance, but I'd like to keep my same instance and simply turn it on and off in between live streams. I've read that the Start and Stop options are disabled because my instance is not stored on an EBS volume, and that running FMS on an EBS volume is not supported. Must I leave the instance running all the time in order to get around having to set it up each time I need it? Is there any sort of workaround or widely accepted answer for this?
Thanks again.

Hi Smit,
I believe you are talking about FMS AWS instance and you may be using a centos 4.0.2 instance AMI or lower?
Well ... earlier, options for stopping a centos AWS image was not available, but recently they are there in place, so I suppose if you use a new centos 4.5.1 AMI then probably you can start stop the aws instance on yuor will. Give ut a shot and let me know.
Regards,
Shiraz Anwar
I again cross-checked and found that you were right, start and stop is not supported there .... an alternative method is to take a snapshots of the runinng instnace and terminate that instance after that, later you can use your snapshot to attach to the EBS volume to run your system again. You may need to use the Elastic IP address, because you wont like your users to update each time you terminate the old instance, and create new instance from snapshot. I have never used it in this way, but this is one of the approach.

SQL Server Agent Log showing errors [298] SQLServer Error: 10061, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL

Hi All,
I have started receiving this error in the logs for the last 10 days and the Schedules Jobs for the database have stopped running. My MS CRM application is working fine.
Can anyone guide me what could be the problem.
Date                      17/4/2014 2:04:20 PM
Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct
and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
Date                      17/4/2014 2:11:55 PM
Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error
has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online. [SQLSTATE 08001]
Date                      7/4/2014 11:00:31 AM
Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error
has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online. [SQLSTATE 08001]

Check this link
http://social.msdn.microsoft.com/Forums/en-US/906da9b5-2482-468c-a424-ae099da2d96b/sql-server-agent-service-account-error?forum=sqlsetupandupgrade
Regards, RSingh

Sql Server Agent not starting automatically in failover in a clustered environment.

Hi,
We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
server. In the Sql Server Configuration manager we find that service of
the Sql Server(database engine) as got a start mode as manual being
an instance in the 2 node cluster. When the node in which the service is
running fails the the Sql Server service gets started in the other node. However
we find that the Sql Server Agent service(whose start mode is also in manual)
does not get started automatically in the other node along with the Sql Server
service.Why does the cluster service do not start Sql Server agent service as well.
Should we make the Sql Server agent service start mode to be automatic
instead of being manual as it is now? Thanking you in advance
Binny Mathew

Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
leave it as manual
Satish Kartan www.sqlfood.com
I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
online, when a failover happens.
Satish Kartan www.sqlfood.com

SQL Server could not be started: Reason- SqL Server Agent must be able to connect to SQL servwe As sytem Administrator

There is no http:// on one of the tool bars that allow me to log on. Warning appears: SQL Server Agent must be able to connect to SQL server as System Administrator. We bought this computer at a flee market and it already had names as administrators on it. How can I change my name to be administrator?

There is no http:// on one of the tool bars that allow me to log on. Warning appears: SQL Server Agent must be able to connect to SQL server as System Administrator. We bought this computer at a flee market and it already had names as administrators on it. How can I change my name to be administrator?

SQL Server Agent and SSIS

I created a SSIS package that litterally just export a view onto a server. The database, ssis and location are all on the same server. When I run the SSIS package in SSIS works perfectly. When I run it in SQL it doesnt work. I have read way to many articles
trying to figure out how to fix this. The best was something about a proxy. I really just want to run the package through as a JOb through SQL Server Agent. Any directions would be great.
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 3:15:00 PM Error: 2015-03-05
15:15:00.41 Code: 0xC0011007 Source: {A9456201-8A74-44C9-839F-1CD3CC02637F} Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will
be posted. End Error Error: 2015-03-05 15:15:00.41 Code: 0xC0011002 Source: {A9456201-8A74-44C9-839F-1CD3CC02637F} Description: Failed to open package file
"C:\Users\lasadmin\Documents\Visual Studio 2010\Projects\Integration Services Project1\Integration Services Project1\Package.dtsx"
due to error 0x80070005 "Access is denied.". This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name when calling LoadPackage
or the specified XML file has an incorrect format. End Error Could not load package "C:\Users\Documents\Visual Studio 2010\Projects\Integration Services Project1\Integration Services Project1\Package.dtsx" because of error 0xC0011002.
Description: Failed to open package file "C:\Users\Documents\Visual Studio 2010\Projects\Integration Services Project1\Integration Services Project1\Package.dtsx" due to error 0x80070005 "Access is denied.". This occurs when
loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name when calling LoadPackage or the specified XML file has an incorrect format. Source: {A9456201-8A74-44C9-839F-1CD3CC02637F}
Started: 3:15:00 PM Finished: 3:15:00 PM Elapsed: 0.015 seconds. The package could not be found. The step failed.
thanks
bryan

No I am still a bit confused.
1.) I created both Jobs as the admin.
2.) The NT Service\SQLSERVERAGENT is by default for whatever reason is running the job when I scheduled
it.
3.) Just so that I could try and run the job I tried to follow the article that was given in the first post. I got to the second script and I get the below error.
Msg 14529, Level 16, State 1, Procedure sp_add_proxy, Line 45
Proxy "ARSHADALI-LAP\SSISProxyDemoUser" is not a valid Windows user.
Msg 14262, Level 16, State 1, Procedure sp_verify_proxy_identifiers, Line 51
The specified @proxy_name ('SSISProxyDemo') does not exist.
Is there a more simpler way this seems almost like over kill.
bryan
Is that domain machine or is it in work group?
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

Error trying to run SSIS Package via SQL Server Agent: DTExec: Could not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object

Situation:
SSIS Package designed in SQL Server 2012 - SQL Server Data Tools
Windows 7 - 64 bit.
The package (32 bit) extracts data from a SQL Server db to an Excel Output file, via an OLE DB connection.
It uses 3 package variables:
*) SQLCommand (String) to specify the SQL Statement to be executed by the package
Property path: \Package.Variables[User::ExcelOutputFile].Properties[Value]
Value: f:\Output Data.xls
*) EXCELOutputFIle (String) to specify path and filename of the Excel output file
Property path: \Package.Variables[User::SQLCommand].Properties[Value]
Value: select * from CartOrder
*) VarObjectDataSet (Object) to hold the data returned by SQL Server)
Property path: \Package.Variables[User::VarObjectDataSet].Properties[Value]
Value: System.Object
It consists out of 2 components:
*) Execute SQL Task: executes the SQL Statement passed on via a package variable. The resultng rows are stored in the package variable VarObjectDataSet
*) Script Task: creates the physical output file and iterates VarObjectDataSet to populate the Excel file.
Outcome and issue:The package runs perfectly fine both in SQL Server Data Tools itself and in DTEXECUI.
However, whenever I run it via SQL Server Agent (with 32 bit runtime option set), it returns the errror message below.
This package contains 3 package variables but the error stating that a package variable can not be set, pops up for the VarObjectDataSet only. This makes me wonder if it is uberhaupt possible to set the value of a package variable
of type Object.
Can anybody help me on this please ?
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 6:40:20 PM DTExec: Could
not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object. Started: 6:40:20 PM Finished: 6:40:21 PM Elapsed: 0.281 seconds. The package execution failed. The step failed.
Thank you very much in advance
Jurgen

Hi Visakh,
thank you for your reply.
So, judging by your reply, not all package variables used inside a package need to be set a value for when run in DTEXEC ?
I already tried that but my package ended up in error (something to do with "... invocation ...." and that error is anything but clearly documented. Judging by the error message itself, it looks like it could be just about anything. that is why I asked my
first question about the object type package variable.
Now, I will remove it from the 'set values' list and try another go cracking the unclear error-message " ... invocation ...". Does an error message about " ... invocation ..." ring any bells, now that we are talking about it here ?
Thx in advance
Jurgen
Yes exactly
You need to set values only forthem which needs to be controlled from outside the package
Any variable which gets its value through expression set inside package or through a query inside execute sql task/script task can be ignored from DTExec
Ok I've seen the invocation error mostly inside script task. This may be because some error inside script written in script task. If it appeared after you removed the variable then it may because some reference of variable existing within script task.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Excel Import Fails in SQL Server Agent Job but not when executed in BIDS

We have a SQL Server agent job that has ran successfully for the past 6 months. It started failing about a week ago. I don't believe anyone installed anything on the server. The proxy account used to run the job is an admin on the server.
I've tried everything I can think of or that I found on searches. I even changed the connection manager from an Excel source to using an Microsoft office 12.0 Access Database Engine OLEDB connection and it still runs in BIDs and not as an agent job.
I also setup my LANID as a proxy account to see if the job would run (checking security) -- and it fails with the same error.   I also made sure the path is
\\server\share rather than a drive letter. Any ideas?
The package is executed in 32 bit mode. The package still runs fine in BIDS (where BIDs is opened on the server) but fails in the SQL Agent job with:
Executed as user: xxxxxx\xxxxxx. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 9:00:00 AM Error: 2014-12-01 09:00:02.46
Code: 0xC0202009     Source: xxxxxx Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE
DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "External table is not in the expected format.". End Error Error: 2014-12-01 09:00:02.65
Code: 0xC020801C     Source: Load File to Staging Excel Source [43]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager
"Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-12-01 09:00:02.77
Code: 0xC0047017     Source: Load File to Staging SSIS.Pipeline     Description: Excel Source failed validation and returned error code 0xC020801C. End Error Error: 2014-12-01 09:00:02.90
Code: 0xC004700C     Source: Load File to Staging SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2014-12-01 09:00:03.02     Code: 0xC0024107
Source: Load File to Staging      Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:00:00 AM Finished: 9:00:03 AM
Elapsed: 2.761 seconds. The package execution failed. The step failed.

I logged on to the server with the account that the SQL Agent runs under and ran the following from a command
line to execute the package:
"D:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\DTEXEC.exe" /FILE
"\"K:\SSIS\xxxxxx\xxxxx.dtsx\"" /CHECKPOINTING OFF
/REPORTING EWCDI /X86
I wanted to see if it was a security issue with the agent account account - but
this ran fine.
I then updated the SQL Agent job to use an operating system command instead
of a SSIS package on the job step. This fails...
The issue is definately with the SQL Server Agent

Sql server agent is not highlighting start and stop options

Similar Messages

Maybe you are looking for