How to find who has changed SQL Server Agent 'Job History' settings.

Hi all,
I was searching from couple of days to know is there a way to find out who has changed the SQl agent property settings.
Like if someone unchecks the SQL Agent History settings how i can find who has done that change?
I searched for trace flags but there is nothing related to it, i searched for system tables and views of msdb but nothing which can give this information, even didn't find any audit setting that can monitor these activities.
My sql version is SQL Server 2008. Please throw your ides on how to track the sql agent history setting changes!!!
Thanks In Advance!!!!
VVinayPrasad

Hi,
You might be able to AUDIT the execute on that SP but its not giving exactly what has been changed... i guess you are getting what i am looking for...
whatever the property might be changed it only shows the sp name thats it.... but not the exact sql statement executed on background
VVinayPrasad
First of all: It's not about me, it's about you. And it's not a might, its a given fact. I
tested it for you.
Second: your question was:
>>I was searching from couple of days to know is there a way to find out
who has changed the SQl agent property settings.
>>Like if someone unchecks the SQL Agent History settings how i can find who has done that change?
So please first clear up, what you really need.
Third: instead of Auditing I already gave the advise to use Tracing (be it SQLTrace or Extended Events). Both will give you the exact statement. SQLTrace may be easier on SQL2008
Please try all of the provided first before doing guesswork.
Andreas Wolter (Blog |
Twitter)
MCM - Microsoft Certified Master SQL Server 2008
MCSM - Microsoft Certified Solutions Master Data Platform, SQL Server 2012
www.andreas-wolter.com |
www.SarpedonQualityLab.com

Similar Messages

How to run Exe file through Sql server agent job

Hello All
i have 2 servers
1.Application Server
2.Database server
Application server has a .exe file so i wanted to run this exe file through SQL server agent job from database server.
What is the process for run this Exe file
Can you plz suggest me step by step process
Kamal

While i'm trying to implement this below method
Step1 : Right Click SQL Server Agent. Select New -> Job. This will open a wizard to schedule a new
job.
Step2 : Select Steps from options given on the left side of wizard. This is the main place to set your
exe\program as a running step. Give some name to this step, Select Operating System (cmdexec) for the Type and give the full path of exe in Text box for Command.
ex:\\10.11.00.98(your application serverIP)\ch.exe
Thanks vanchan-Please
mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
I got this below error
Message
Executed as user:NJROSJ345\SYSTEM. The process could not be created for step1 of job
(Reason:Access is Denied)The step failed.
But i have sys admin rights on the both the servers
Kamal

Want to change the SQL Server Agent Job History Text Files Location

We have SQL Server 2014 installed on a couple servers, but they were not consistent on directory paths during the installs. I am trying to get the servers to all match.
On one server, SQL Server the Agent Log and Job History files were being written to [H:\Data Root Directory\MSSQL12.MSSQLSERVER\MSSQL\Log].
I want to change that to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log] to match the other server.
I have ALREADY gone into SSMS - [SQL Server Agent] - [Properties] and changed the "Error Log " "Fle Name" to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\SQLAGENT.OUT]. And that is working great.
In [SQL Server Configuration Manager] - [SQL Server (MSSQLSERVER)] - [Properties] - Startup Parameters entries have been changed to the new path (-d, -e, and -l), and under [Advanced] both Data Path and Dump Directory are pointing to the new path.
In [SQL Server Configuration Manager] - [SQL Server Agent (MSSQLSERVER)] - [Properties] - [Advanced] Dump Directory is pointing to the new path.
However, the job's History text files are still being written to the old path.
There is no setting in the Jobs or the Maintenance Plans that controls the history file location.
I have searched the registry and changed three settings from the old path to the new path. The registry does NOT contain any more references to the old path.
I rebooted the server, but when the jobs run their history text files are still be written to the old path.
Does anybody have any ideas?? Thanks

I checked the [Job] - [Step] - [Advanced ] - "Output File", and the field is blank.
I then reviewed all the tabs and left menu items in the Job...I cannot find any where the references the old path.
I then went to the Maintenance Plan and checked every thing there. Still cannot find what is referencing this old path.
SQL Server is also still writing xel files to this old path...if that offers any clues.
The text file being generated is the recap of the Job run. Starts with this:
Microsoft(R) Server Maintenance Utility (Unicode) Version 12.0.2430
Report was generated on "xxxxxxxxxxxxxxx".
Maintenance Plan: SQL_Backups_Log
Duration: 00:00:03
Status: Succeeded.
Details:
Thanks for the ideas....

SQL Server Agent - Job History not being recorded (SQL Server 2005)

I have been trying to get to the bottom of an issue with SQL Server Agent not recording any job history. I am using SQL Server 2005 on a single Windows Server 2008 machine (i.e. no other domain controllers/active directory servers).
The SQL Server Agent service is configured to 'Log On As' NT user account 'sqlagent'. The jobs themselves are executed successfully (all 'Transact-SQL' type steps actually use the 'sa' account) however the there is no actual job history to be found for any
of the jobs -- in the SQL Activity monitor, the 'Last Run Outcome' is always 'Unknown' and the 'Last Run' date is always 'Never' for all jobs; in the SQL Job History Viewer there are no entries for any instances of a job being executed.
The 'sqlagent' NT user account ia a member of the 'Administrators' NT group; the 'Administrators' group appears under Security > Logins on the database server. I have another server that also uses the same setup with a 'sqlagent' NT user account, on that
database server the 'sqlagent' user account appears under Security > Logins and the SQL job history works correctly. I have attempted to add the 'sqlagent' to the Logins on the affected server using the SQL Server Surface Area configuration but this operation
returns an error, detailed below.
Additionally, I have attempted to use the built-in NT system account 'NETWORKSEVICES' to run the SQL Agent Service but this also results in exceptions in the error log and no job history being recorded. The entries in the error logs are very similar to those
from the 'sqlagent' NT user account but instead the user is referred to as 'NT AUTHORITY\ANONYMOUS LOGON' in the error logs, again these are detailed below.
Many thanks in advance for anyone's time and help with this issue!
Arthur
The following errors are raised in SQL Server Agent > Error Logs each time a job is executed:
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
If the SQLAgent service is configured to use the NT system account 'NETWORKSERVICE' then the following errors are returned instead:
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
I have tried granting the 'sqlagent' NT user account with SysAdmin Server Role privaledges using the SQL Server User Provisioning tool in SQL Server Surface Area Configuration, but this always throws the following, similar error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Error: 18452)
===================================
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
Server Name: 127.0.0.1,1344
Error Number: 18452
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at sqlprov.SysAdminServerRole.ProvisionInstance(Instance instance, String userName)
at sqlprov.ProvisionTask.Provision(Instance instance, String userName)
at sqlprov.MainForm.ProvisionTasks()

Hi Rama,
Thanks for your reply. I have run the query you specified and can see only one entry with "NTLM" in the auth_scheme column, all of the rest have "SQL". It figures that the entry with "NTLM" is relating to the one NT user account that can successfully log
in to the service (as mentioned in my reply to Nag above, this is the NT user account that installed the service on the machine). I have also executed the same query on the other machine that I mentioned in my original post and this contains two "NTLM" entries,
I'd assume that these relate to the NT user that installed the software and the correctly working "sqlagent" NT user account that is correctly logging the job history on that machine.
I think the problem is very much to do with granting access to new NT user accounts, as per the KB article that you have quoted above. In this case, it is not relating to scenarios 1 or 2 as these relate to SQL Server logins and this issue is about a Windows
Authentication login. As I mentioned to Nag above, I am unable to grant any NT user accounts with access to the service however the NT accounts are all defined locally on the same machine as the SQL server is installed (i.e. there is no domain controller,
active directory controller, etc) so I don't understand how the Windows login cannot be verified.
Any further advice on the issue would be greatly appreciated, please let me know if there is any more information I can provide to help diagnose the problem.
Many thanks!
Arthur

How to find who has created the condition records

hi all,
in POF1 condition records were created.for material and plant.how to find who has created condition records for the material and plant.
is there any way to find who has created please help me out.
thanks
sunny

Hi,
There are two ways of finding the who has created the ondition record.
01. This is through the sales order-> Item details level-> condtion Tab----> Select the condition type and click on dispaly condition record below in the same creen. Then Goto tab on the menu and select the overview of the condition record. After do so you will have the details of diffrenr tabs. In this you need to select the Administrative data for the person who had created the condition record.
02. Goto T. Code VK13 and give your condition type for which you need to find the person created the record. Select the header details tab for the person who had created the record.
Hope this is fine with you.
Bye & Enjoy SAP.
Koganti

How to find who has created the determination records for packaging instruc

how to find who has created the determination records for packaging instructions in POF1.
need to find the user details from POF3.
can any one plz suggets me.

Sunny,
Go to POF1 click on determined record -> Display -.> enter-> F8 then -> double click on the record for which you want to see the responsible person ->click on admin. data tab here u will find the responsible person. hope u got the right answer.
Ravi Thapliyal
IdhaSoft

SQL Server Agent Jobs error for Slowly changing dimension

Hi,
I have implemented Slowly changing dimension in 5 of my packages for lookup insert/update.
All the packages are running good in SSDT. And when i deployed the project to SSISDB and run the packages all are running successfully. But when i created a job out of that and run the packages, then 3 packages ran successfully and 2 packages failed.
When i opened All Execution Report. I found the following error:
Message
Message Source Name
Subcomponent Name
Process Provider:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description:
"Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "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.". An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".
Process Provider
Slowly Changing Dimension [212]
Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source query and deployed again and run, then the job succeeded. more than 15,000 failed.
And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded.
Now i am not able to figure out, what exactly is the problem with Slowly changing dimension task for more than 15,00 records in SQL Server Agent Job run?
Can anybody pls help me out.
Thanks
Bikram

Hi Vikash,
As i have mentioned in the above post, below 2 scenarios:
"Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source
query and deployed again and run, then the job succeeded. more than 15,000 failed.
And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded."
That means i am able to connect to sql server.
But if i change the 1st scenario and read 4,00,000 records, the job fails and shows the above mentioned error.
Similarly in the 2nd scenario, if i implement SCD look up, the job fails and shows the above mentioned error.
And i am consistently reproducing this.
Thanks
Bikram

How to stop SQL Server Agent Job if Stored Procedure returns value 0

I have SQL Server 2012 SSIS.
I have 2 SSIS packages.
I have created SQL Server Agent Job for running packages.
I have created steps. If first step have run succesfully next step is run.
I have need to add new logic.
I have validation stored procedure, which validate DB table values and returns 1 or 0.
I would like to create logic where first of all this SP is runned. Return value of SP determines if steps are run or not.
I was thinking to use Execute SQL Task for running SP.
If value 1 is returned, then run rest of Tasks is run.
If value 0 is returned, what should I do so that Job is stopped? I need assistance!
I want current step to stop never moved to next step.
Is there any SSIS tasks, which can stop the Job?
Or should I make Step for running validation SP?
How to do so that if value 0 is returned stop Job.
Kenny_I

Please refer the below link:
http://technet.microsoft.com/en-us/library/aa260308(v=sql.80).aspx
Please read Remarks carefully!!!
Remarks
If a job is currently executing a step of type CmdExec, the process being run (for example, MyProgram.exe) is forced to end prematurely. Premature ending can result in unpredictable behavior such as files in use by the process being held open. Consequently,
sp_stop_job should be used only in extreme circumstances if the job contains steps of type CmdExec.
Permissions
Execute permissions default to the public role in the
msdb database. A user who can execute this procedure and is a member of the
sysadmin fixed role can stop any job. A user who is not a member of the
sysadmin role can use sp_stop_job to stop only the jobs he/she owns.
When sp_stop_job is invoked by a user who is a member of the
sysadmin fixed server role, sp_stop_job will be executed under the security context in which the SQL Server service is running. When the user is not a member of the
sysadmin group, sp_stop_job will impersonate the SQL Server Agent proxy account, which is specified using
xp_sqlagent_proxy_account. If the proxy account is not available,
sp_stop_job will fail. This is only true for Microsoft® Windows® NT 4.0 and Windows 2000. On Windows 9.x, there is no impersonation and
sp_stop_job is always executed under the security context of the Windows 9.x user who started SQL Server.

How to run a SQL Server Agent job step on certain days/frequency

I've a SQL Server Agent job. One of the requirement is that a particular step should only run on certain frequency i.e. Certain Date and time. Any suggestions how can that be done?
GBM

yes
1. Make first step as a Transact SQL step. Keep command as below
IF DAY(GETDATE()) = <Your date value>
AND DATEPART(hh,GETDATE()) = <your time hour)
AND DATEPART(minute,GETDATE()) = <your time minute)
SELECT 1
ELSE
RAISERROR 'Job cant be run at this time'
Then for job step properties set the following properties in advanced tab
This would make sure it will quit the job without executing other core steps untill it reaches the required day and time
You can add more conditions in IF based on requirement like if you want time to be on certain second or month to be particular value etc
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

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.

HOw to avoid DeadLocks when you schedule a Sql Server Agent Job and calling SSIS packages

Hi All,
I have scheduled 2 packages in in Sql Server Agent jobs .
First job which is having Package 1 executing at 11 AM and where I am inserting the data in the table.
Second job which is having Package 2 executing at 12 AM and where I am updating the data in the table based on the first job inserted records.
When I am executing my first job it taking more time and executing till 12 AM and from 12 AM my job 2 also starting ,so getting deadlocks conflicts because inserting happening from job1 and updating happening from Job 2.
How to avoid deadlocks and fix the issue.
Please Suggest .
Thanks & Regards,
Anand

Hi Anand,
Here is another solution, you can set the Job 2 not to run based on a schedule, and create another SQL Server Agent Job which starts at 12 AM and run with a specified time interval to execute a SQL statement in which you do the following steps:
1. Get the status information of Job 1 using the statement:
DECLARE @i int;
EXEC @i = msdb.dbo.sp_help_job @job_name = ‘Job Name'
2. If the value of @i is 1 which means the status of job 1 is success and current time is, then start the job 2. So, the statement is as follows:
IF @I = 1
EXEC msdb.dbo.sp_start_job @job_name= ‘Job Name’
Regards,
Mike Yin
TechNet Community Support

How to pass values to SQL server Agent Job which internally calls SSIS

Hi,
I have a requirement where i need to call remotely SSIS package from ASPX. After following MSDN form, I have creaed one SQL server agent job and calling that job from ASPX. I am ablt call SQL server agent job from ASPX. Only issue i am facing is: I need
to pass 2 variables from ASPX to SQL Agent job so that from Job i can map the same to SSIS Package.
I am using system SP (sp_start_job) for calling SQL server agent job as mentioned in MSDN forum.
below is the code , which i am using to call SQL serve agent job.
Code:
SqlConnection
jobConnection;
SqlCommand jobCommand;
SqlParameter jobReturnValue;
SqlParameter jobParameter;
int jobResult;
                jobConnection =
new
SqlConnection("Server=ServerName;Initial
Catalog=msdb;Integrated Security=SSPI;user id=username;Password=password");
                jobCommand =
new
SqlCommand("sp_start_job",
jobConnection);
                jobCommand.CommandType =
CommandType.StoredProcedure;
                jobReturnValue =
new
SqlParameter("@RETURN_VALUE",
SqlDbType.Int);
                jobReturnValue.Direction =
ParameterDirection.ReturnValue;
                jobCommand.Parameters.Add(jobReturnValue);
                jobParameter =
new
SqlParameter("@job_name",
SqlDbType.VarChar);
                jobParameter.Direction =
ParameterDirection.Input;
                jobCommand.Parameters.Add(jobParameter);
                jobParameter.Value =
"ImportCMTData";
                jobConnection.Open();
                jobCommand.ExecuteNonQuery();
                jobResult = (
Int32)jobCommand.Parameters["@RETURN_VALUE"].Value;
                jobConnection.Close();
switch (jobResult)
case 0:
Console.WriteLine("SQL
Server Agent job, RunSISSPackage, started successfully.");
break;
default:
Console.WriteLine("SQL
Server Agent job, RunSISSPackage, failed to start.");
break;
Console.Read();
Thanks
Pankaj

"3-4 concurrent users are calling the SSIS package from ASPX page" this is not a proper design
If the data is being ingested than it is likely that this concurrency will lead to one of the packages die
What you shell do is to just queue the data ingress/processing.
In general, again, packages should not be called from ASP web pages, SSIS is ETL-server side technology there is nothing signalling back to the user whether it was successful. The proper way is to write a REST service or alike.
Arthur
MyBlog
Twitter

SSIS Package Fails when Scheduled as a SQL Server Agent Job

I have an SSIS package that runs without any problems when executed through BIDS.
However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
My question is - what is the advised way of doing this?
Thanks
Gary

Hi Garyv.King,
When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
For more detailed information about the issue, please following this KB article:
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
http://support.microsoft.com/kb/918760
You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
The following 4 issues are common encountered in the SSIS forum.
1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
2. Data source connection issue.
3. File or registry access permission issue.
4. No 64-bit driver issue.
For more information about it, please see:
How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc
Thanks,
Eileen

SQL server agent job running as Agent Service Account whose service account does not have r/w access but is still able to write?

Hi. I am newer to SQL server security and am reviewing some of our SQL server's configuration to make sure the services are running under accounts with least privilege. I have a SQL server 2012 instance whose Agent service is configured to run
under an AD user account named 'SQLServices'. The jobs on this server are configured to run as 'SQL server agent service account', which means they should execute as user 'SQLServices'. The jobs are set up to execute SSIS packages which read and
write to a database on the same server where the agent job is scheduled and SSIS package installed (all on same server). The jobs are currently executing without error and are reading writing data correctly. Upon close examination, it turns out the
SQLServices account is not assigned to the 'sysadmin' role and had no users mapped to any databases on this server. How are these jobs working? I verified in profiler that the login name indeed is 'SqlServices'. I also verified
that SQLServices login has no database access by remote-ing onto the server and trying to log into the DB, and access was denied as expected. According to the literature, the Agent service needs to be a member of 'sysadmin role' but I am reading
some cases where that is not necessarily the case. So this is not so concerning. What is concerning is that the login 'SQLServices' had no access to the databases on that server yet it is reading and writing to the databases as if it does.
The only thing I can think of is maybe jobs run as 'SQL server agent service account' on the same server as the databases it r/w to somehow has some kind of default access. What am I missing here? Any input would be helpful.

After 2 days on this forum I found the answer to my own question. In retrospect, I should have posted this under 'SQL Server Security', but I didn't know it existed.
The 2 threads below explain that Sql agent actually runs using SID (service) NT SERVICE\SQLSERVERAGENT if you chose that when you installed. This will automatically create an associated login NT SERVICE\SQLSERVERAGENT in SQL server with sqladmin
role. This is the login that Agent uses to connect to the local instance of SQL server. If you changed to domain account to run the service during install or after using config manager, basically NT SERVICE\SQLSERVERAGENT is still
used to connect to your local instance behind the scenes (even though you will still see your domain user as account), and the domain account is used to reach outside the server.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for
https://social.technet.microsoft.com/Forums/sqlserver/en-US/b83a52fd-fe11-4c28-a27b-88be8ae79f2a/how-do-i-change-sql-server-agent-service-account-to-nt-servicesqlserveragent?forum=sqlsecurity

Management Studio Fails when added Integration Services step to SQL Server Agent Job

Hi,
I have two new servers I've setup with Windows Server 2012, SQL Server 2012 SP1, Visual Studio 2012 SP4. I've previously been on SQL 2008 and VS 2008 so this is new to me.
I am finding SSMS is throwing an exception on both machines when i do the following:
1. Go to SQL Server Agent | Jobs
2. Create a new Job.
3. Select Steps and click New Step
4. Change the job type to SQL Server Integration Services Package.
Following error occurs:
TITLE: Microsoft SQL Server Management Studio
The type initializer for '<Module>' threw an exception. (SqlManagerUI)
ADDITIONAL INFORMATION:
The C++ module failed to load.
(DTEParseMgd)
Index was outside the bounds of the array. (DTEParseMgd)
I also find if I take an existing job with SSIS package steps and attempt to edit those steps the same message appears. This issue happens on both my servers as they have been configured almost identically. This doesn't occur when selecting any other job
type.
I've also tried installing cumulative update 8 in a hope that this may fix it but with no success.
As my entire environment is based around SQL Agents running SSIS i'm a little bit concerned, especially since I have some tight deadlines getting these servers running.
I have found nothing relating to this issue. Any help greatly appreciated.
Simon
Below is the detailed error message:
===================================
The type initializer for '<Module>' threw an exception. (SqlManagerUI)
Program Location:
   at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition.Microsoft.SqlServer.Management.SqlManagerUI.IJobStepPropertiesControl.Load(JobStepData data)
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.UpdateJobStep()
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.typeList_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
   at System.Windows.Forms.ComboBox.set_SelectedItem(Object value)
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeStepCombo()
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeData()
   at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.OnInitialization()
   at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SetView(Int32 index, TreeNode node)
   at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SelectCurrentNode()
   at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.InitializeUI(ViewSwitcherTreeView treeView, ISqlControlCollection viewsHolder, Panel rightPane)
   at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
   at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(ISqlControlCollection control, IServiceProvider provider)
   at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.editJobStep_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.RunDialog(Form form)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at System.Windows.Forms.Form.ShowDialog()
   at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
The C++ module failed to load.
(DTEParseMgd)
Program Location:
   at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
   at .cctor()
===================================
Index was outside the bounds of the array. (DTEParseMgd)
Program Location:
   at _getFiberPtrId()

Hi,
I hadn't installed CU3 however as a test i tried installing CU4 and this didn't help. Since my first emails i have more issues that have brought a complete hault to the upgrade project.
If i double click on a package to run it manually I basically get the same issue. This means i have no way of running any packages except throught VS.
I've also found that regardless of the order of the software installs it still fails. It's related to SP1 of SQL and SP4 of VS.
I'm on Server 2012. When install in the following order SQL 2012, SQL SP1, VS2012, BIDS, VS SP4 i have no problem until VS SP4 is installed. If i install VS SP4 then BIDS it also fails at the last step. If i install all the VS and BIDS software first, then
SQL then SQL SP1 it fails at the SQL SP1 step.
This means i could actually install everything and either ignore the SQL SP1 or the VS SP4 and i'd be fine however this is not really a solution as i will never be able to patch the software and once live this is very dangerous.
I am still surprised there is no obvious solution to this. I'm only installing MS software on a fresh box and only installing 5 pieces of software (including the SPs). I would have though if this was an issue others would have come across it too.
Has anyone else installed all these components and got them working on the same OS. I believe early on in my testing i installed these in Windows Server 2008 and didn't have the issue.
Regards.
Simon.

How to find who has changed SQL Server Agent 'Job History' settings.

Similar Messages

Maybe you are looking for