SSIS configuration Not Working With SQL agent Job

Hi,
I have created an SSIS configuration table in SQL Server where in I store all connection strings. This configuration is enabled within my package. To make even the DB where I store connection strings, I have an environment varibale. I thus have 2 configurations
in the following order:
1. env variable: Points to the DB where in my connection strings would be stored.
2. SQl Server configuration:where I actually, store the connection strings.
However , when I try to execute the package, it seems the SQL Server agent does not read from the Configuration tables at all.
Can someone let me know how to enable this from within SQL Server agent? I do not store connection strings in a file, so I can't add any files within the configuration tab.
Please let me know as to how do I enable configurations stored within SQL tables from SQL Server Agent jobs. I am using SQL Server 2008.

Todd,
Yes, I have enabled the configurations from within the package. When I open the package from BIDS, I do see information stating that package is trying to read from the environment variable and from the SQL Server.
However, when the same package is used in a SQL Agent job, in the data sources tab, I see the connection string which I have set manually within the package, not the one which it should read from the Configuration table.
E.g. in the design of my package, I am using Server A with Credential1, but within the Configuration table, against the same Connection, for the Same Server , I have stored Credential2.
It should read the Credential2, as I have configuration enabled (as I can also verify from the messages within BIDS, upon opening the pacakge).
However, it just reads the same Credential1, which has been supplied at design time.
Not sure how can I access the Configuration stored within the SQL table from a SQL Agent job

Similar Messages

Database Mail not working with SQL Server Agent

I'm running SQL Server 2005 Standard edition 64 bit with SP2 on a 64 bit machine.
Database mail does not work with SQL Server Agent. When I configure SQL Server Agent to use database mail the test email button is greyed out and inactive therefore I cannot send emails using operators or for jub success failure etc.
I've read that there was supposed to be a fix for this with SP1 but I have SP2 and still receive the same problem. Please can somebody help as I do not wish to use SQL Mail as a work around due to this becomming redundant in future versions of SQL Server.
Kind Regards

The problems solved
steps:
1)we create a mail profile at at Managment->Database Mail ,of SQL Managment
2)we set this account as "default" at Managment->Database Mail -> Configure Database Mail -> Manage profile security
3)At tab "Alert System" of SQL Server Agent properties , we check the "Enable mail profile" , Mail System=Database Mail, Mail profile = "the profile we already create"
4)we create a new operator at "Operators" of sql agent, where at "notification options" -> "Email name" we put the mail where we want to sent the agent the mails at failured job
5)We go at a specific job, at tab "Notifications" ,we check the "email" check box and then we choose the operator we just create, at the text box next to check box.
I hope not to forget something
Thank You all for the help

Odi os command not working with agentservice agent.

dear all,
odi os command not working with agentservice agent but with local agent it work fine.. and user is administrator.
kindly solve it
Regards
Naseer

Hi,
you referred to oscommand, so are you executing a .bat fille? if yes, where exactly does the .bat file reside, local machine or on network share?
Also, follow these couple of documents, they may be helpful to you.
859215.1 and 424703.1
Regards
Srikanth

SSIS error authenticating proxy with SQL Agent

Hello,
I'm a BI Analyst (not DBA) and I've asked our IT department for access to SSIS and SQL Server Agent to deploy packages to import data from Oracle nightly and transform it into a dataset in SQL Server 2012 using SSIS.
I've written several packages, deployed these to a SQL Server. These run fine when ran locally through Object Explorer > Integration Services Catalog > SSIDB by right clicking/execute.
However our DBA has set up an SSIS Proxy that I can use in conjunction with SQL Server Agent to run these packages. However, when I try to use this proxy I get the error message:
'Unable to start execution of step 1 (reason: error authoenticating proxy ad\[name removed], system error. The username or password is incorrect. The step failed.'
I've tried packages with security for 'dontsavesensitive' and 'encryptsensitivewithuserkey' but neither work. I'd like to rule anything out that I'm not doing, however I think it is a permissions issue (happy to be proven wrong though).
Can anyone offer suggestions for next steps please?
Thanks,
ZP

Hi V,
Thanks again.
I went to the general tab and it is all greyed out and the credentials box is empty - though I can click on the button with three dots on. However, it just takes me to a credentials form but doesn't give me any options to select from. The box for SSIS is
ticked though.
It is all greyed out - I presumed this is because I haven't got permissions to set what the proxy can do?
I tried select * from sys.credentials - didn't return any information (zero rows).
I'm (mostly!) convinced the packages are fine - I've created several simple packages to demonstrate the same thing to our DBA and these simple packages all run fine when executed directly through SSMS but never work through SQL Agent with SSIS Proxy. His
thinking is that its because I need to run them with security as 'dontsavesensitive' but these dont work either.
Do you know if I should be asking for a specific permission/credential?
Thanks!

SSIS package is failing in SQL agent job with webserviceTaskException: Service Description cannot be null

Hi All
we are using webservice task in our ssis package and the package is successful in SSDT . when we created SQL job using that package it is failing with webserviceTaskException: Service Description cannot be null.
we have given access to web service for ssis proxy account and have access on wsdl file folder and given access to temp folder .
what would be the reason for the failure?
Surendra Thota

Hi Surenda,
As per my understanding, the error message is too general. In order to troubleshoot this issue, we should view the detail error message about this job. For more details, please see:
Troubleshooting Jobs
SQL Server Agent Error Log
Besides, since when you call a Microsoft SQL Server Integration Services (SSIS) package outside a SQL Server Agent job step, the SSIS package runs successfully. However, if you do not modify the SSIS package, then execute it via SQL Server Agent job step,
it fails. The scenario always related to the user account that is used to run the package under SQL Server Agent. Please also verify that the account has access to the Web site or to the Web Service Description Language (WSDL) file for HTTP connection manager.
References:
SSIS package does not run when called from a SQL Server Agent job step
Example using Web Services with SQL Server Integration Services
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Alerts not working with direct agent?

I'm aware of
this issue with the SQL Intelligence pack and direct agents, which I'm also experiencing, but Alerts don't seem to be working with my direct agents either. I switched the handful of servers I had reporting under the old gateway model to direct agents
last week, and added 6 new direct agent servers, I know some of those new servers have the same hotfix alerts that I'm seeing from the old ones, but I have not received a new alert since 11/26 when I switched everything over, and when I login to the portal
and view alerts I receive:
"No gateway or SCOM management group detected. Op Insights required a gateway or SCOM management group in order to analyze data and generate alerts"
Followed by a link to the deployment guide, when I read the deployment guide for direct agents there no mention of an SCOM deployment requirement.
Any suggestions? Is anyone who is configured with direct agents successfully receiving alerts?

Indeed. Configuration Assessment 'alerts' are disabled with Direct Agent. Please look at the answer given here
https://social.msdn.microsoft.com/Forums/azure/en-US/8241918e-41f4-4429-9a5f-962e96908878/repeated-closed-alerts-emails-on-closed-alerts-in-opsinsight?forum=opinsights with regards to those 'alerts': we are moving away from 'alerts' for configuration-related
issues, and replacing them with those 'Recomendations' shapes (like the SQL Assessment). Those weren't 'alerts' in the first place - those were *proactive* recommendations. For new accounts with only Direct agents, those are not even produced and those screens
are unavailable. We think of 'Alerts' in the SCOM sense: server is down, needs immediate action even at 2am.
In this sense, we think of 'Alerts' as something that should be user-defined and based on searches where you can determine what to alert for, against any type of data - see this idea here
http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519198-long-running-saved-searches-or-scheduled-that-ca

Dynamic Configuration not working with Integrated Configuration

Hi All,
Dynamic Configuration works fine in PI 7.3 when Classical Configuration is used. However the same does not work using Integrated Configuration.
Scenario :
SOAP -->SOAP Synchronous scenario in PI 7.3 (Dual Stack).
Trying to save a value from Request mapping using dynamic configuration and use the same in response mapping.
UDF Code :
Request Mapping :
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey Variable = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "Variable1");
conf.put(Variable, a);
Response Mapping :
DynamicConfigurationKey Variable = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "Variable1" );
string1 = conf.get(Variant);
Note : Using Integrated Config(AAE Processing) - Response header does not have DynamicConfiguration header node , but Classical Configuration has that.
Regards,
Parimala
Edited by: ParimalaE on Mar 1, 2012 1:33 PM

For us this is what we had:
This didn't work (getInputParameters is the newer stuff that doesn't work):
DynamicConfiguration dc = (DynamicConfiguration)container.getInputParameters().getValue(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey dck = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","TServerLocation");
dc.put(dck,"https://xyz.api-salesforce.com/services/Soap/c/26.0/0DFa00000008jis");
return "";
This works for us(we had to remove getInputParameters):
DynamicConfiguration dc = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey dck = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","TServerLocation");
dc.put(dck,"https://xyz.api-salesforce.com/services/Soap/c/26.0/00D3000000001X0");
return "";

ForEach Loop Container Mapping Variable From SSIS Package Not Working In SQL-Server StoredProcedure

I have an SSIS package that uses a ForEach Loop Container to enumerate Excel Files in a dir. I also have a Task Flow that inserts data from those Excel files into SQL-Server.
Im trying to insert the file names into a column into the same table in SQL-Server by using a mapping variable in my StoredProcedure.
Im having trouble with my MappingVariable at the end of the script with red squigglies. The following is my StoredProcedure script.
CREATE PROCEDURE [dbo].[Insert_F_STG_v2]
-- Add the parameters for the stored procedure here
@Hrs float,
@Type nvarchar(100),
@SN nvarchar(100),
@Op nvarchar(100),
@[USER::CurrentFileName]
AS
BEGIN
SET NOCOUNT ON;
INSERT INTO [CRM_RC].[dbo].[F_StgTbl]
[Hrs],
[Type],
[SN],
[Op],
[Report_Date]
VALUES
@Hrs ,
@Type,
@SN,
@Op,
@[USER::CurrentFileName]
END
The last @[USER::CurrentFileName] in the Values block at the bottom of the script is the one giving me issues.
The following is the error:
Msg 102, Level 15, State 1, Procedure Insert_F_STG_v2, Line 95
Incorrect syntax near 'USER::CurrentFileName'.

This seems to be the solution, but get the following exception:
[Derived Column [2]] Error: The "Derived Column" failed because truncation occurred, and the truncation row disposition on "Derived Column.Outputs[Derived Column Output].Columns[Derived Column 1]" specifies failure on truncation. A truncation error occurred
on the specified object of the specified component.
AND: [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Derived Column" (2) failed with error code 0xC020902A while processing input "Derived Column Input" (3). The identified component returned
an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.

Back arrow does not work with SQL Server Reporting Services Reports. When one pages back from a sub report the back action appears to skip moving to the previous step. IE 8 works fine?

I have a SSRS report that has a parameter driven drop down list to select a catagory for a report to run a summary for the category in Report Manager. When the report runs there are links to a sub report with more detailed information about the category summary. Firefox runs everything correctly up to this point.
When I try to back arrow from the sub report Firefox skips the summary report page and reverts to the initial page where the sub category can be selected to run the summary report.
Can you help? IE8 works well with this but has severe spped issues with reports that contain multiple selection parameters. Firefox handles the multiple parameters very fast but has the page back issue.

I have a SSRS report that has a parameter driven drop down list to select a catagory for a report to run a summary for the category in Report Manager. When the report runs there are links to a sub report with more detailed information about the category summary. Firefox runs everything correctly up to this point.
When I try to back arrow from the sub report Firefox skips the summary report page and reverts to the initial page where the sub category can be selected to run the summary report.
Can you help? IE8 works well with this but has severe spped issues with reports that contain multiple selection parameters. Firefox handles the multiple parameters very fast but has the page back issue.

LcsCDR & QoEMetrics Purge and Usage Summary SQL Agent Jobs

Hello.
On our SQL instance that hosts the LcsCDR & QoEMetrics databases I have the following SQL Server Agent Jobs:
LcsCDR_Purge
LcsCDR_UsageSummary
QoEMetrics_Purge
QoEMetrics_UsageSummary
I'd like to know if anyone else has these same jobs on their instances as it's unclear looking at the job descriptions, when they were created, and the code they run if these are part of the core Lync system or something that has been set up randomly
afterwards.
One thing I do know is that these jobs don't work correctly when you use database mirroring. I will elaborate on this if/when I can find out any more information about them first.
Thanks

Thank you for the reply.
The problem with these jobs is that when they attempt to run against a database which is a mirror, it causes the job to fail. That would not seem to be a big deal right, except our policy (and many other SQL shops I imagine) is to send e-mail notifications
each and every time a SQL agent job fails on any server, not just those associated with Lync.
As it stands these jobs are not configured on either the principal or mirror server to notify anyone as I’d get an e-mail every hour on the hour from the mirror server telling me that a job has failed (even though it didn’t actually need to do anything
) giving the impression something is wrong somewhere. This is quite a common trap to fall into with SQL Agent jobs and database mirroring.
Remember that because as Lync uses automatic failover either server could be the mirror at any given time so there is no mileage in setting the e-mail notifications on just the server that is currently the principal.
What this job should do then is when it attempts to run on the mirror, check if it’s the mirror first and if it is then do nothing instead of failing each time. This will enable e-mail notifications to be set up on the jobs on both servers, so when
the job fails we know there is potentially a genuine problem to be investigated.
Each job contains two steps, I’ll use the QoEMetrics_UsageSummary as the example.
The code in step 1 is this, which causes the job to error out if it is attempting to run against the mirror.
declare @_MirroringRole int
set @_MirroringRole = (
select mirroring_role
from sys.database_mirroring
where database_id = DB_ID('QoEMetrics')
if (@_MirroringRole is not NULL and @_MirroringRole = 2) begin
raiserror('Database is mirrored', 16, 1)
end
else begin
print ('Database is not mirrored')
end
I re-wrote this job to run in one-step like this, which runs from the master database, which as I mentioned above doesn’t make the job error out when it realises it’s trying to run against a mirror.
DECLARE @_MirroringRole INT
SET @_MirroringRole = ( SELECT mirroring_role
FROM sys.database_mirroring
WHERE database_id = DB_ID('QoEMetrics'))
-- if this is not a mirrored database or it's the principal, attempt to run usage summary op
IF (@_MirroringRole IS NULL OR @_MirroringRole = 1)
BEGIN
DECLARE @_Sql NVARCHAR(4000)
SET @_Sql =
'USE [QoEMetrics];
DECLARE @_UpdatingSkipped INT
EXEC dbo.RtcRegularMaintainDatabase @_UpdatingSkipped = @_UpdatingSkipped output'
EXEC (@_Sql)
END
ELSE -- if the database is a mirror, don't do anything
BEGIN
PRINT 'there is nothing to do, the database is a mirror'
END
The same logic can be applied to the other 3 jobs and I was intending to suggest it as a connect item, except there doesn’t seem to be a section for Lync so I will contact product support and see what they think.
Thanks again.

[SQLSTATE 42000][Error 4834] - SQL Agent Job failing

Hello,
I have started getting the below error message on a bulk insert job that has been running over several months.
Error is:
Executed as user: domain\svc_sql. You do not have permission to use the bulk load statement. [SQLSTATE 42000] (Error 4834). The step failed.
Domain\svc_sql is also service account for SQL Server. Both the SQL server and SQL agent are running under this account and it has sysadmin and bulkadmin privileges.
Bulk insert is from csv file in a folder for which domain\svc_sql has full permission.
I've now ran out of ideas.
Could anybody advise?
Many thanks,
Mohan

Hi Mohan,
According to the error message, it can be caused by that when SQL Server Agent performs EXECUTE AS USER, you are by default sandboxed into the database, and therefore you don't have access to server-level tasks.
To work around the issue, as Praveen’s post, you can set the database TRUSTWORTHY to ON, however it might cause some security issues. For more details, please review this article:
Giving Permissions through Stored Procedures Ownership Chaining, Certificates and the Problematic EXECUTE AS.
Personally, I recommend you create the bulk insert job as a CmdExec job which uses SQLCMD to run scripts. For more information about CmdExec job, please review this article:
Create a CmdExec Job Step.
There is also a discussion about the error 4834 in the following thread.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/48621876-11a0-468c-95b4-2a682f0134aa/bulk-insert-not-working-through-an-agent-job
Thanks,
Lydia Zhang

Error with SSIS package running as SQL Agent job

I have a strange issue.
I have a SQL Agent job that execute 5 steps, each step is an SSIS package that imports a CSV file to a temp table, then executes a SQL script to update a production table.
This job runs every 3 mins, every day, and has been for over a year.
Every once in a while it will start failing on step 2. Sometime it only happens for a couple of runs, other times I have to restart the SQL server. Once it corrects itself, it could be months before it happens again, but usually happens every
few weeks.
The error in the job history is: "Unable to bulk copy data. You may need to run this package as an administrator"
Obviously I have all the permissions correct, as it was running successfully every 3 mins before this error suddenly starts. I'm at a loss as to what the problem is. It is always on step 2, which is identical to step 1 except its a different CSV file
going to a different table. As I typed this, it failed twice, then was successful afterwards.
Any ideas where to look for further information? I've checked the event viewer and looked in the SQL logs, nothing stands out at this time.

Hi Kerberos35,
It seems to be caused by the UAC feature which makes SSIS use the low-permissions token of the administrator Windows account under which the job runs. This issue is described in the following KB article:
http://support.microsoft.com/kb/2216489/en-us
To resolve the issue, you can install the latest service pack for your SQL Server. To work around this issue, you can also use one of the following two methods:
Method 1: Replace the SQL Server Destination components in the Data Flow Tasks that are failing with OLE DB Destination components that point to the same SQL Server connection manager.
Method 2: Create a SQL Server Agent proxy by using a Windows account that is not a member of the local Administrators group after you assign Create Global Objects permissions to that account.
To do this, follow these steps:
Click Start, point to Administrative Tools, and then click Local Security Policy.
Expand Local Policies, and then click User Rights Assignment.
In the details pane, double-click Create global objects.
In the Local Security Policy Setting dialog box, click Add.
In the Select Users or Group dialog box, click the user accounts that you want to add, click Add, and then click OK two times.
Regards,
Mike Yin
TechNet Community Support

SSIS ETL does not pick the file from Share point when it execute through SQL Agent job

I have created one SSIS packages, which pick the file from the Share point document library. its work successfully, once it execute through the VS project application.
But when i create a job in SQL Server Agent for this package then it does not pick the file and job getting fail.
Just for more update, SQL Server has been install in Cluster mode and using BIDS 2012 with SQl Server 2012.

Hi PriyankGupta,
SQL Server Integration Services is not cluster awareness, and does not support failover from one cluster node to another. So, in your clustered environment, make sure SSIS is installed on each node in the cluster. In other word, SSIS must be installed on
the server where the SQL Server Agent job is created.
If you use any third party task/component or drivers, make sure they are installed on the SQL Server Agent job server. Besides, also pay attention to the protection level of the package as well as 32-bit or 64-bit runtime mode of the package. For more information,
please see:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job
If the issue persists, please post the error message in the job history for further analysis.
Regards,
Mike Yin
TechNet Community Support

How to Create a SQL Agent Job For A SSIS Package with Sql Server Authentication

Hi ALl,
I have a SSIS package which basically has a data flow task in which i pull the data from one server and copy it into another server and my source server is the one where i dont have windows authentication and i have to only use a sql server authentication
. This package runs fine if i click the server connection properties type the password and save it.
Now, my task is to set up a sql agent job which basically uses a proxy account and takes this package from the file system and runs it.But when i try to run this package, its failing with an error saying
"Login Failed For rpt5user" where rpt5user is the username for my sql server authentication of the source connection.
Can someone please help me with any suggestions on how to do this?
I have heard that we can achieve it by using xml config file which i have never used and i am trying to google around but for no luck.
So, If someone can please throw any suggestions or ideas on this it would be great.
Thanks

You need to add password as a config item and set it from the file source or sql table
see this as an example
http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

How to pass parameters to sql agent job run configured ssis package

Hi all,
I have a big problem at my small project.
I build my SSIS package that get its variables values from a configuration file..
and when i build a SQL agent job to run this package in a schedule i set the values of variables in it .. but in run-time the package still get its parameters from the configuration file !??
any help please ?

>SQL agent job to run this package in a schedule i set the values of variables in it
One way, setup a configuration table for the package. Let the package read the values for the variables from there.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SSIS configuration Not Working With SQL agent Job

Similar Messages

Maybe you are looking for