JOB in Sql Server Agent should run multiple times.

Hi Guys,
I have a ETL SSIS job in Sql Server Agent, Which should run multiple times.
1. For Example : I scheduled a job at 10:00 PM, If the job fails at 10:00 PM it should run automatically again at 10:10 PM, if the job fails again at 10:10 PM then the job should run at 10:40 PM.
If the job gets success at first attempt i.e 10:00 PM, then it should not run at 10:10 PM.
Note : The time difference between jobs is 10 minutes and 30 minutes. And i know that we can run the job at regular intervals.
Thanks in advance

Just add retry attempts to whatever number you want (2 as per your original explanation) in Job step properties as below
Have a logic to include a delay of 10 mins . You can make use of WAITFOR function for that
see
http://www.mssqltips.com/sqlservertip/1423/create-delays-in-sql-server-processes-to-mimic-user-input/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Similar Messages

Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1

I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
Error: 17750, Severity: 16, State: 0.
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).

Hi JFriedley,
According to your error message, there might three reasons for this issue.
xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
files.
There is a similar issue about error 17750, you can review the following article.
http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Schedule SSIS packages as job in SQL Server Agent errors

Hi, I am using SQL Server 2008 R2 and created few SSIS packages and schedule them using SQL Server Agent and every time I try to schedule packages via SQL Server Agent my jobs keep failing. I am using domain/ione as the owner and when I invoke the job on
ServerA let's say and the job gets executed by domain/ServerA$ and fails as it does not have enough privileges. How do I fix this issue firstly without the proxy and why is the job being executed by domain/ServerA$ when the owner & user who invokes
it is domain/ione?
Thanks in advance............
Ione

Hi Ione,
The owner of any SQL jobs should be SA or any other non-expiring account
If you do not want the proxy used, then add the needed priveleges.
The owner of the job is one, the SSIS step gets executed by the account the Agent is running under.
Arthur
MyBlog
Twitter

Using the SQL Server Agent for the first time

I have set up several jobs to run automatically throughout the day. Each job just does one thing: executes an SSIS package.
The packages themselves run perfect when I test them in Visual Studio 2005, but when the SQL Server Agent tries to run the job I am getting failed jobs.
Is there any tutorials or walkthroughs that can teach my about using the SQL Server Agent? If I wanted extensive help troubleshooting my SQL Server Agent problems which part of the message boards would I post that too?
Thanks for the info!

Anyone?
I really need some resources for SQL Server Agent 2005.
Refer these links,
http://technet.microsoft.com/en-us/library/ms141701(v=sql.90).aspx
http://stackoverflow.com/questions/10489392/permissions-issue-running-ssis-package-from-sql-job
Regards, RSingh

Sql Server Agent last run duration in minutes

Hello Forum Members,
Can you please advise me on this:
There are 5 sqlagent jobs and they run many times in a day ranging from 10 seconds to 1 hour. I would like to know the duration of run in minutes during their last run.
Kind Regards,
Sqlquery9

Hi
This isn't as easy as it should be due to the job duration in sysjobhistory being stored as an INT, so you need to extract the hours,mins,seconds and add them together.
Here's an example:
SELECT rec_job.job_name,
run_duration/10000 hrs, --hrs
run_duration/100%100 mins, --mins
run_duration%100 secs, --secs,
((run_duration/10000) * 60 ) +
(run_duration/100%100) +
(CASE when run_duration%100 > 29
THEN 1
ELSE 0
end) Total_mins ---total mins
FROM msdb.dbo.sysjobhistory jh
INNER JOIN ( select j.job_id, MAX(h.instance_id) instance_id, MAX(j.name) job_name
FROM msdb.dbo.sysjobhistory h
INNER JOIN msdb.dbo.sysjobs j on h.job_id = j.job_id
WHERE step_id = 0 --overall outcome
AND j.name IN
( 'Job Name 1',
'Job Name 2',
'Job Name 3',
'Job Name 4',
'Job Name 5')
GROUP BY j.job_id
) rec_job ON rec_job.instance_id = jh.instance_id
The code above assume that any duration of 30secs or over will be counted as one minute, you can fill in the job names that you're interested in.

SQL Server Agent Job intermittently running for packages on SSISDB

I created an SSIS package to pull data from OLAP Cube and push it into SQL Server using SSIS 2o12. I deployed the same on the SQL Server SSIS DB and created a SQL Server Agent Job to run the package. I have an account configured to run the job (not by
creating proxy in the job, but SQL Server Agent is running under that account), that has access to the OLAP Cube. The job is running sometimes and failing sometimes. Why the job behaving weirdly. Any help on the issue will help me a lot. I am using SQL Server
2012 SP1 enterprise edition (11.0.3000.0) (if it helps). The error message which pops up when it fails is :
OLE DB Source failed the pre-execute phase and returned error code 0xC0202009
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05.
An OLE DB record is available. Source: ""Microsoft OLE DB Provider for SQL Server 2012 Analysis Services."" Hresult: 0x00000001 Description: ""Error Code = 0x80040E05, External Code = 0x00000000:."".
"

Hi,
You are using Execute SQL Task to run a MDX query, right? If so, here is an approach/workaround for your reference. If the MDX query doesn’t have parameters, you can create a view in SQL running the MDX query and make the Execute SQL Task to get data
from that view. If the MDX query has parameters, you can try a Function and create a stored procedure, and then set the Execute SQL Task to execute that stored procedure.
Regards,
Mike Yin
TechNet Community Support

Running multiple SSIS packages using SQL Server Agent question.

I have a multitude of SSIS packages I want to run using SQL Server Agent. What would the best practice be for running these jobs using SQL Server Agent? One job per package or running all pakages from one job? If you have an answer can
you explain the technical reasoning behind your answer? Thanks in advance.
Stan Benner

Hi, maybe a bit more analysis will give a better answer
Do all the packages have to run in sequence? (if yes, single job better)
Can the list of packages to be executed be grouped by dependency (ex package 1,2 and 5 must run in sequence and can be executed by one job, while package 3,4 are not dependent on package 1,2 and 5 can be run by a separate job).
Can any jobs be run in parallel?
How often will the package execution sequence change?
How will you deploy your packages and job? (the more jobs to create the more install script needed and upgrade scenarios become messy).
My personal preference:
I create ONE ssis package which is executed by ONE sql agent job. lets call this 'PackageExecutionWrapper.dtsx'
PackageExectionWrapper then contains multiple 'Execute Package' tasks for the packages you want to execute.
In the package you can apply any package execution rules - which packages have to run after the other, which packages can run concurrently, which packages should only run if previous succeeded.
If you need to change the sequence, simple, just update the PackageExecutionWrapper package.

SQL Server Agent Job Failing on Job Step

Hi,
Firstly, apologies if this post has been made in the wrong group. Running SQL Server 2012. I'm attempting to add a SQL Server Agent Job which calls a stored procedure that sends a Database Mail message. The SQL Server and SQL Server Agent
both run under the NT AUTHORITY\NETWORK SERVICE account. The Database Mail service has been enabled, and a public profile created. When running the stored procedure manually, I receive no errors - everything runs as expected and I do receive an
email containing the expected information.
I've created the job, job step, job schedule, attached the schedule to the job, and assigned the job to server, all using T-SQL without error. I've also enabled the mail profile on the SQL Server Agent, and I know that part is working because when
the job fails, I get an email notification of the failure.
I've checked the command text in the job step and parsed it within the SQL Job Step Edit window to confirm, it shows as parsing correctly. However, when I manually run the job itself, I get the following:
Execution of job failed. See the history log for details.
I check the history log and it shows:
[474] Unable to refresh Database Mail profile Database Mail Profile. (reason: ) (Not a typo, the history log shows no reason)
[260] Unable to start mail session.
[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
The command text on the failing job step is as follows:
DECLARE @date [varchar](10)
SET @date = CAST(GETDATE() AS [varchar](10))
EXEC [dbo].[GetExceptions]
@company = 'MyCompany',
@checkDate = @date
With regard to the date value being passed as varchar: This stored procedure is used to check for exceptions against multiple databases on this server (hence the company parameter) via dynamic SQL. I'd much prefer to use proper data typing but this
is the only way I could get it to work.
Does anyone have any suggestions on anything else I could check, or insights into why this is failing? Any help is greatly appreciated!
Best Regards
Brad

I am not sure if this really helps but I would do follow the below steps:
1. make sure sql server agent has database mail enabled(rigt click on server agent--properties--alert system--enable database mail and choose right profile.) and RESTART THE SQL SERVER AGENT.(i know you said it i working, but sometimes, restart the
sql server agent might fix)
2. check agent error log and check if any error messages.
3. run the command text you mentioned in sql server and see if it is working.(i know you said it is working but just to make sure).
4. make sure sql server agent service user has permissions to run database mail in msdb. check this https://msdn.microsoft.com/en-us/library/ms186358.aspx
5. Check the output from select * from msdb.dbo.sysmail_log and if it says anything
6.it does not look like the job log is getting truncated but to make sure, get the job step output to a text file.to do this, edit the job step and on the job step properties click on advanced, enter path to the output file. this will give the complete
output for the step.
Hope it Helps!!

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

SQL Server Agent available on Azure?

I would like to delete records from an database table on Azure when the table reaches a certain size.
I would normally do this by scheduling a stored procedure job using SQL Server Agent.
Is the SQL Server Agent available on databases held on Azure?
Should I use an alternative approach?
Thanks
Stew

Hello ,
Please take look on :
Scheduling job on SQL Azure
We can execute sql procedures on Azure based on our need (schedule configuration).
Create a mobile service.
Create a scheduler. Mention the database to be used for this.
Configure the scheduler for the frequency.
Click on tab Script. The script can be written in java script or .net. The script should have the code to run a proc.
I used below code to run dbo.ExecuteDataRequest procedure Azure database.
function Execute_Process_Request() {
      console.log("Executing ExecuteDataRequest...");
      mssql.query('Exec dbo.ExecuteDataRequest',{
        success: function(results){
        console.log("Finished the Process Request job.");
         error: function(err) {
           console.log("error is: " + err);
Find the new user added which will run the scheduler (Under Login folder of Security of Azure db server). Need to grant execute permission to the new user on the database where we need to execute the job.
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 Server Agent ... Relation with BizTalk.

Hi All,
I know that there are jobs in SQL Server Agent which are used to perform some activity on scheduled basis like Purging,backup etc...
what happens if SQL server agent service is in Stop mode(is it mandatory to have it started) and does it have any relation with BizTalk BAM.
Praj Dixit

Yes, you have to make sure the SQL Server Agent is running on the SQL Server. When the SQL Server
Agent is stopped, the built-in BizTalk SQL Server Agent jobs that are responsible for database maintenance cannot run. This behaviour causes database growth, and this growth may cause performance issues.
SQL Server Agent jobs except the MessageBox_Message_Cleanup_BizTalkMsgBoxDb job should be enabled and running successfully.
You can learn about the SQL Server Agent jobs at Description of the SQL
Server Agent jobs in BizTalk Server
Regarding BizTalk BAM,
Yes Backup BizTalk Server Job takes the backup of BAM Primary Import, SQL NS as
well as other BizTalk databases. The BAM Analysis database, BAM Star Schema Database and Tracking Analysis Server database store content in SQL Server Analysis Services cubes. The Backup BizTalk Server job does not back up these databases. Instead, to
backup these databases, it uses SQL Server Analysis Manager.
I found this utility (BizTalk Monitoring
Automation Utility) very useful to automate the monitoring of
your BizTalk environment. If you have liberty to go with a paid tool,
BizTalk360 a monitoring and support tool is the one for you.
Rachit

Error when execute a package from SQL Server Agent

We have the next problem:
When we execute a package from a Job of SQL Server agent, it shows the success messege, but reviewing the results, the package didnt do all the tasks.
When we run it mannually by MSIS the package, it shows the success message and it works fine.
The workflow of the package is :
1) Shrink the databases (executing a sql file)
2) Backup the databases (Back up Database task of MSIS)
3) Rename the files to .BAK extension (by the Foreach loop container and fyle system task)
4) Execute command to compress the it (by a .bat)
5) Move the compress file to another location (by another Foreach loop)
Manually run correct, but when is a a SQL AGent Job that execute the package it does only the first 2 steps.
we are ussing Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (coffee) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
We are using a user with administrator privilegies
Cheers

Can you check if account running package has proper access. You may need to define a proxy account for that.
See
http://www.databasejournal.com/features/mssql/article.php/3789881/Proxy-Accounts-in-SQL-Server.htm
http://gqbi.wordpress.com/2014/01/30/setting-up-a-proxy-account-to-run-sql-server-integration-services-ssis-2012-packages/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SQL Server Agent Failed to decrypt protected XML node

I'm getting the below error when trying to run sql server agent to run an SSIS package. I've updated folder security to allow sql server agent access, but cannot get the package to execute within SQL Management Studio. The package runs find in SSIS.
11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 12:12:00 PM Error: 2014-11-30 12:12:02.65 Code: 0xC0016016 Source: LoadStgProspects Description:
Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that
the correct key is available. End Error Error: 2014-11-30 12:12:03.88 Code: 0xC0016016 Source: LoadStgProspects Description: Failed to decrypt protected XML node "DTS:Password" with error
0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2014-11-30
12:12:04.74 Code: 0xC0209303 Source: LoadStgProspects Connection manager "Excel Connection Manager" Description: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver
is not installed<c/> run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
End Error Error: 2014-11-30 12:12:04.74 Code: 0xC020801C Source: Load prospect files Prospect xls [231] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection
method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error:
2014-11-30 12:12:04.74 Code: 0xC0047017 Source: Load prospect files SSIS.Pipeline Description: Prospect xls failed validation and returned error code 0xC020801C. End Error Error: 2014-11-30 12:12:04.74
Code: 0xC004700C Source: Load prospect files SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-11-30 12:12:04.74 Code: 0xC0024107 Source:
Load prospect files Description: There were errors during task validation. End Error Error: 2014-11-30 12:12:04.74 Code: 0xC00220DE Source: LoadStgProspects Description: Error
0xC0012050 while loading package file "C:\Users\Jim\Documents\Visual Studio 2010\Projects\SSISTraining\SSISTraining\LoadStgProspects.dtsx". Package failed validation from the ExecutePackage task. The package cannot run. . End Error DTExec:
The package execution returned DTSER_FAILURE (1). Started: 12:12:00 PM Finished: 12:12:04 PM Elapsed: 4.337 seconds. The package execution failed. The step failed.,00:00:04,0,0,,,,0

Hi selfdestruct80,
According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
According to my knowledge, the package may not run in the following scenarios:
The current user cannot decrypt secrets from the package.
A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
A task or a connection manager requires that the current user account has correct permissions.
According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
/FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

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

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

JOB in Sql Server Agent should run multiple times.

Similar Messages

Maybe you are looking for