Error While executing a SSIS package which contains a script task through SQL Server Agent job

Hi,
I have a SQL Server 2012 SSIS package with a script task along with other tasks [data flow, execute sql tasks ]. When I manually executed the job through BIDS, its completed successfully.
Then I have automated the execution of the package through SQL Server Agent Job. But when I executed the package through SQL Agent job, it runs successfully for all the tasks except script task. When it comes to execute the Script Task, it is getting failed
with the below error message.
"Error: 2012-08-29 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
I have installed the SSIS on the 64-bit environment and SSIS service is running. Also I tried to run the job through 32 bit [job option] but I am getting the above error in all cases.
Any help will be greatly appreaciated !
Thanks,
Navin
- naveen.reddy

Hi Arthur,
My script task access the excel files in a network share, refresh them all and save them. When I execute the ETL manually or thru DTEXEC, it is executing successfully. I am facing the issue when I am executing thru SQL Agent Job only. Logging also showing
the same error.
"Error: 2012-08-23 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
- naveen.reddy

Similar Messages

Error while executing SSIS package which contains Script component through SQL Server Agent Job

Hello All,
I have written one SSIS 2012 package which is fetching records from CSV and put it into staging DB and from staging DB , using SSIS script component task, I am inserting data into Dynamics CRM. So far it is working fine when
I manually execute SSIS package.
but when I run the SSIS package using SQL server agent job, I encounter below error. After seeing below error at step "Insert TLM Headers Script Component " I understand that it is failing at script component which I have used in SSIS package,
but I am not sure what is the cause behind that? please advise.
Error:
Executed as user: domain\user account. Microsoft (R) SQL Server Execute Package Utility Version 11.0.5556.0 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 1:21:41 PM Error: 2015-02-25
13:21:45.94     Code: 0xC0047062     Source: Insert TLM Headers Script Component [205]     Description: System.ServiceModel.FaultException: The server was unable to process the request due to an internal
error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to
the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.    Server stack trace:      at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message
reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)     at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage
methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception
e)    at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)     at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100
wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket) End Error Error: 2015-02-25 13:21:45.94     Code: 0xC0047022     Source: Insert TLM Headers SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Script Component" (205) failed with error code 0x80131501 while processing input "Input 0" (215). 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. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:21:41 PM Finished: 1:21:45 PM Elapsed: 4.009 seconds. The package execution failed. The step failed.
Thanks
Pankaj

domain\user account has not proper rights
That being said, often SSIS jobs require a proxy to be runnable and this is how you make one up
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Arthur
MyBlog
Twitter

Error: Failed to acquire connection while exporting a file using SSIS package through SQl Server Agent job.

Hi Team,
I am running a sql server job which is loading data to a sharepoint document library.File is an excel format and is getting loaded
when executed through SSDT solution .But when i am using an SQL Agent job to pick up the file it doesnt get the path and agent job fails with the error "Failed to acquire connection".I have deployed the SSIS Package through SQL Server 2012 deployment
methodologies.
I am not able to trace the error of loading data from a sharepoint library.library. Sql agent jobs works fine when i give local path.The
account which is running the sql agent job is the same who has access to document library.I also tried to run the job through proxy account. I am using a xml configuraion to store my credentials.I am able to palce the same file to a network drive in the same
server through sql server agent job. The only problem is when I am trying to load the file to a sharepoint folder.
Thanks,
Arsa..

Is that the WebDAV method that you are suggesting here to map the n/w drive?
Its kind of webdav but you will be using windows nw drive to store data
yes, I am able to create the file to D: , but didn't check with the C:.
Try with c:, as c: require special permisssions
If this helped you resolve your issue, please mark it Answered

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

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

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

Error while executing procedure in TOAD which contains parameter and dblink

Hi all,
I am getting error while executing the following code in TOAD and APEX.
It contains parameter( start_date and end_date) and dblink(@TO_FUT).
When I hardcode the parameter values, It works fine.
When I dont give hardcoded values in the procedure, the error comes.
When I comment the lines whereever parameter comes, still the error comes.
I am not sure whether it is parameter issue or dblink issue or some other issue
Is anybody having any clue about this error?
Your help is very much appreciated.
The code:
CREATE OR REPLACE PROCEDURE PROC_ENR_ACC(START_DATE DATE,END_DATE DATE)
AS
BEGIN
EXECUTE IMMEDIATE 'TRUNCATE TABLE OUTPUT_TABLE';
INSERT INTO OUTPUT_TABLE
(FIRST_NAME ,LAST_NAME,HID ,EFF_DT,CID,PLAN, FLAG)
SELECT
TEMP1.FIRST_NAME,
TEMP1.LAST_NAME,
TEMP1.HID,
TEMP1.EFF_DT,
TEMP1.CID,
TEMP1.PLAN,
NVL((SELECT 'Y'
FROM FADMIN.MEMI_TABLE@TO_FUT MEMI
WHERE MEMI.MEME_CK = TEMP1.MEME_CK
AND MEMI.TXN_EFF_DT = TEMP1.EFF_DT
AND MEMI.PBP = TEMP1.PLAN
AND MEMI.MEMI_TXN_CD IN ('AC','RE')
AND MEMI.MEMI_SEQ_NO = (SELECT MAX (MI.MEMI_SEQ_NO)
FROM FADMIN.MEMI_TABLE@TO_FUT MI
WHERE MI.MEME_CK = MEMI.MEME_CK
AND MI.TXN_EFF_DT = MEMI.TXN_EFF_DT
AND MI.PBP = MEMI.PBP
AND MI.MEMI_TXN_CD IN ('AC','RE')
AND MI.MEMI_INTF_STS = 03 )),'N') AS FLAG
FROM
( SELECT
M1.FIRST_NAME ,
M1.LAST_NAME ,
M1.HID ,
M1.EFF_DT,
M1.CID,
M1.PLAN ,
(SELECT MEME.MEME_CK
FROM FADMIN.MEME_TABLE@TO_FUT MEME, FADMIN.GRGR_TABLE@TO_FUT GRGR
WHERE MEME.M_HIN = M1.HID
AND MEME.GRGR_CK = GRGR.GRGR_CK
AND GRGR.GRGR_ID = M1.GRGR_ID
)AS MEME_CK
FROM FADMIN.METR_TABLE@TO_FUT M1,
( SELECT M3.HID, M3.EFF_DT FROM FADMIN.METR_TABLE@TO_FUT M3
WHERE M3.TYPE IN ('60','61')
AND M3.REPLY IN ('117','118')
AND TRUNC (M3.METR_TRANS_DT) BETWEEN START_DATE AND END_DATE
AND M3.SYIN_INST = (SELECT MAX (M4.SYIN_INST)
FROM FADMIN.METR_TABLE@TO_FUT M4
WHERE M4.HID = M3.HID
AND M4.TYPE IN ('60','61')
AND M4.REPLY IN ('117','118')
AND TRUNC (M4.EFF_DT) = TRUNC (M3.EFF_DT))
) TEMP
WHERE M1.TYPE IN ('60','61')
AND M1.REPLY ='011'
AND TRUNC (M1.METR_TRANS_DT) BETWEEN START_DATE AND END_DATE
AND M1.SYIN_INST = (SELECT MAX (M2.SYIN_INST)
FROM FADMIN.METR_TABLE@TO_FUT M2
WHERE M2.HID = M1.HID
AND M2.TYPE IN ('60','61')
AND M2.REPLY ='011'
AND TRUNC (M2.EFF_DT) = TRUNC (M1.EFF_DT))
AND M1.HID = TEMP.HID (+)
AND M1.EFF_DT = TEMP.EFF_DT (+)
AND TEMP.HID IS NULL
UNION
SELECT
M1.FIRST_NAME ,
M1.LAST_NAME ,
M1.HID ,
M1.EFF_DT,
M1.CID,
M1.PLAN ,
(SELECT MEME.MEME_CK
FROM FADMIN.MEME_TABLE@TO_FUT MEME, FADMIN.GRGR_TABLE@TO_FUT GRGR
WHERE MEME.M_HIN = M1.HID
AND MEME.GRGR_CK = GRGR.GRGR_CK
AND GRGR.GRGR_ID = M1.GRGR_ID
)AS MEME_CK
FROM FADMIN.METR_TABLE@TO_FUT M1
WHERE M1.TYPE IN ('60','61')
AND M1.REPLY IN ('016', '017', '022', '023')
AND TRUNC (M1.METR_TRANS_DT) BETWEEN START_DATE AND END_DATE
AND M1.SYIN_INST = (SELECT MAX (M2.SYIN_INST)
FROM FADMIN.METR_TABLE@TO_FUT M2
WHERE M2.HID = M1.HID
AND M2.TYPE IN ('60','61')
AND M2.REPLY IN ('016', '017', '022', '023')
AND TRUNC (M2.EFF_DT) = TRUNC (M1.EFF_DT))
)TEMP1 ;
END;
The error:
ORA-00918: column ambiguously defined
ORA-02063: preceding line from TO_FUT
ORA-06512: at "PROC_ENR_ACC", line 5
ORA-06512: at line 5

Okay
Here's the code formatted
CREATE OR REPLACE PROCEDURE PROC_ENR_ACC (START_DATE DATE, END_DATE DATE)
AS
BEGIN
   EXECUTE IMMEDIATE 'TRUNCATE TABLE OUTPUT_TABLE';
   INSERT INTO OUTPUT_TABLE (FIRST_NAME,
                             LAST_NAME,
                             HID,
                             EFF_DT,
                             CID,
                             PLAN,
                             FLAG)
   SELECT   TEMP1.FIRST_NAME,
            TEMP1.LAST_NAME,
            TEMP1.HID,
            TEMP1.EFF_DT,
            TEMP1.CID,
            TEMP1.PLAN,
            NVL (
                 (SELECT   'Y'
                  FROM   MEMI_TABLE MEMI
                  WHERE       MEMI.MEME_CK = TEMP1.MEME_CK
                  AND MEMI.TXN_EFF_DT = TEMP1.EFF_DT
                  AND MEMI.PBP = TEMP1.PLAN
                  AND MEMI.MEMI_TXN_CD IN ('AC', 'RE')
                  AND MEMI.MEMI_SEQ_NO = (SELECT   MAX (MI.MEMI_SEQ_NO)
                                          FROM   MEMI_TABLE MI
                                          WHERE   MI.MEME_CK = MEMI.MEME_CK
                                          AND MI.TXN_EFF_DT = MEMI.TXN_EFF_DT
                                          AND MI.PBP = MEMI.PBP
                                          AND MI.MEMI_TXN_CD IN ('AC', 'RE')
                                          AND MI.MEMI_INTF_STS = 03)
                  ),'N') FLAG
   FROM (SELECT   M1.FIRST_NAME,
                  M1.LAST_NAME,
                  M1.HID,
                  M1.EFF_DT,
                  M1.CID,
                  M1.PLAN,
                  (SELECT   MEME.MEME_CK
                   FROM   MEME_TABLE MEME, GRGR_TABLE GRGR
                   WHERE       MEME.M_HIN = M1.HID
                   AND MEME.GRGR_CK = GRGR.GRGR_CK
                   AND GRGR.GRGR_ID = M1.GRGR_ID) MEME_CK
         FROM   METR_TABLE M1,
                (SELECT   M3.HID, M3.EFF_DT
                 FROM   METR_TABLE M3
                 WHERE   M3.TYPE IN ('60', '61')
                 AND M3.REPLY IN ('117', '118')
                 AND TRUNC (M3.METR_TRANS_DT) BETWEEN START_DATE AND END_DATE
                 AND M3.SYIN_INST = (SELECT   MAX (M4.SYIN_INST)
                                     FROM   METR_TABLE M4
                                     WHERE   M4.HID = M3.HID
                                     AND M4.TYPE IN ('60', '61')
                                     AND M4.REPLY IN ('117', '118')
                                     AND TRUNC (M4.EFF_DT) = TRUNC (M3.EFF_DT))
                 ) TEMP
         WHERE   M1.TYPE IN ('60', '61') AND M1.REPLY = '011'
         AND TRUNC (M1.METR_TRANS_DT) BETWEEN START_DATE AND END_DATE
         AND M1.SYIN_INST = (SELECT   MAX (M2.SYIN_INST)
                             FROM   METR_TABLE M2
                             WHERE       M2.HID = M1.HID
                             AND M2.TYPE IN ('60', '61')
                             AND M2.REPLY = '011'
                             AND TRUNC (M2.EFF_DT) = TRUNC (M1.EFF_DT))
        AND M1.HID = TEMP.HID(+)
        AND M1.EFF_DT = TEMP.EFF_DT(+)
        AND TEMP.HID IS NULL
        UNION
        SELECT   M1.FIRST_NAME,
                 M1.LAST_NAME,
                 M1.HID,
                 M1.EFF_DT,
                 M1.CID,
                 M1.PLAN,
                 (SELECT   MEME.MEME_CK
                  FROM   MEME_TABLE MEME, GRGR_TABLE GRGR
                  WHERE       MEME.M_HIN = M1.HID
                  AND MEME.GRGR_CK = GRGR.GRGR_CK
                  AND GRGR.GRGR_ID = M1.GRGR_ID) MEME_CK
        FROM   METR_TABLE M1
        WHERE   M1.TYPE IN ('60', '61')
        AND M1.REPLY IN ('016', '017', '022', '023')
        AND TRUNC (M1.METR_TRANS_DT) BETWEEN START_DATE AND END_DATE
        AND M1.SYIN_INST = (SELECT   MAX (M2.SYIN_INST)
                            FROM   METR_TABLE M2
                            WHERE   M2.HID = M1.HID
                            AND M2.TYPE IN ('60', '61')
                            AND M2.REPLY IN ('016', '017', '022', '023')
                            AND TRUNC (M2.EFF_DT) = TRUNC (M1.EFF_DT))
        ) TEMP1;
END;
/When posting code if you put {noformat}{noformat} (with the curly brackets and in lower case) above and below it you can preserve formatting.
To your original question...
Is the link name supposed to be variable?
What do you mean by 'hard coding' the values, do you mean in the procedure itself so you'd actually PROC_ENR_ACC();?
What happens when you run this?DECLARE
start_date DATE;
end_date DATE;
BEGIN
start_date := '01-JAN-2009';
end_date := '01-FEB-2009';
PROC_ENR_ACC(start_date, end_date);
END;
I need to know exactly how to recreate your error...
Cheers
Ben
http://www.munkyben.wordpress.com
+Don't forget to mark replies helpful or correct+ ;)

Fetch SSIS error through SQL Server Agent JOB

Hi,
I am trying to fetch eventmessages from catalog.eventmessages view in SSISDB inside a sql job which executes a package. This utility is supposed to send an email with the description of failure reason and step whenever the JOB fails. But I could not find
a way to reference a package in SSISDB with the corresponding JOB through SQL query.
sysjobsteps stores the step info, but how can I refer to the SSIS package using the info from this table or any other table. Please provide an expert view for this problem.
Regards
Mohit

sysjobsteps stores the step info, but how can I refer to the SSIS package using the info from this
table or any other table
Can you try like this?
SELECT e.package_name,e.message
FROM msdb.dbo.sysjobsteps js
inner join SSISDB.catalog.event_messages e
On js.command collate database_default like'%\' + e.package_name collate database_default + '%'
--WHERE e.event_name ='OnError'
Uncomment the WHERE clause if you want to specifically look for errors
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

SSIS running through SQL Server agent Job Fails --SQL Server 2012

Hi All,
I am getting the below error.
Executed as user: sak\thiru. ...ion 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 3:31:17 PM Error: 2014-03-07 15:32:22.46 Code: 0xC0202009 Source: CommonDataSource
Connection manager "TESTDB" Description: 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 11.0"
Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.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 11.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ". End Error Error:
2014-03-07 15:32:43.58
The package execution fa... The step failed.
I checked namedpipes, ports,services, SqlBrowser all are running fine.
share your views.
Thanks
Thiru
Thiru

Hi Thiru,
The error messages are rather general and the issue may occur due to various causes. You can check the “Connect Time” setting of the Connection Manager "TESTDB", and increase its timeout value.
If the issue persists, maybe it occurs because the Windows Firewall or certain anti-virus software blocks the RPC dynamic range of TCP Ports between SQL Server and Domain Controllers. In this case, temporarily disable third party anti-virus software, or
configure RPC dynamic port allocation to work with firewalls referring to the following KB article
http://support.microsoft.com/kb/154596.
In addition, the issue may be related to the SQL Server that the OLE DB Source adapter connects to. You can check the SQL Server log to see if any error occurs at that time.
Hope this helps.
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 give an error if execute through SQL server agent

I have created a SSIS package in BIDS 2012. If i execute this package through sql server agent it gives the below error:
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: 11:19:47 AM Error: 2015-01-20
11:19:47.83 Code: 0xC0016016 Source: Sub_Hadoop_aggregation 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: 2015-01-20 11:19:47.94 Code: 0xC0016016 Source:
Sub_Hadoop_aggregation 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: 2015-01-20 11:19:48.04 Code: 0xC0016016 Source: Sub_Hadoop_aggregation 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: 2015-01-20 11:19:48.92 Code: 0xC00291EC Source: alter_keys Execute SQL Task Description: Failed to acquire connection "mstr_warehouse". Connection may not be
configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:19:47 AM Finished: 11:19:48 AM Elapsed: 1.42 seconds.
The package execution failed. The step failed.
so i have change some properties in our package like protectionlevel change from encrypted to dontsavesensitive. After that i have created configuration file for the package and use that configuration file. It executes the package through sql server agent
smoothly.
Thanks
Azhar Khan

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 JOB ERROR - SSIS PACKAGE

Hi ,
I have a SQL server agent job which runs SSIS package as the daily job. The SSIS package contains multiple child package. Its a master package which calls other SSIS package. The master package calls 23 SSIS packages, few of the packages runs in parallel.
I am getting the below 2 different errors more frequently. It fails only in the production server, I scheduled the job in UAT server, it did not fail. Also when we run the master package with out sql agent job, it did not fail.
Error 1 :
R6025 - pure virtual function call. The return value was unknown. The process exit code was 255. The step failed.
Error 2 : The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
We tried browsing for the answers ,no luck. It failing in live , so we need to run the package manually in live server every time.
Please help me to resolve this issue. Thanks in advance.
Regards,
Dhivya Sivakumar

Hi Vijeth,
Thanks for your reply.
1) Run the Package manually and check whether it runs successfully. -
No Failures. Package completed succesfully
2) If Step 1 is successful,
a) Point the same package to the UAT database and run it and check whether it runs successfully or not. -
We tried to schedule the package almost for 1 month. No failures in UAT.
b) In UAT database, point to the Production database and run the package. - I am not sure, if i can do this.I will try and let you know the result.
These steps will help us identify whether the problems lies within the package or the Environment.
3) Run the Package manually in production Environment using dtexec utilily. -
No Failures. Success.
4) Check the ID used to run the SQL Agent job and modify to an account with elevated permissions or GRANT more permissions to the existing ID. -
The account used currently is having all the privileges. Its the most powerful user in live DB.
Regards,
Dhivya S

SSIS package fails under SQL Server Agent job

Hi All
I have designed a SSIS package to encrypt a file using Cipher (EFS) it works fine from BIDS & Package Execution Utility.
But SQL Server Agent job is failing to do this. I am getting the error as
" In executing C:\Windows\System32\Cipher.exe /e /a C:\Test.txt at "",The Process Exit code was 1 while the expected was 0."
Please help me.
Thanks

Two things that usually come to mind when this happens from BIDS locally to the SQL Agent are
1. Security is not
adequate under the SQL Agent Service Account
Rule the security problem out by setting up a proxy account that you know ahs security to run the needed tasks in the package. Either that or give the service account the permissions needed.
2. 32bit BIDS development and running under a 64bit Platform in your SSIS installation
This can be fixed by selecting run in 32bit more or running the package with the 32bit installed version of DTEXEC found in the Program Files (x86) folder where you installed tools.
Next, setup logging in the package so you get a more detailed error message. Event handlers on the tasks will be much more detailed using the OnError event. you can write that to either a flat file with a data flow in the event handler or simply
insert the event into a table using the ? as the parms. If you need assistance setting that up, here are basic steps for a SQL Server table
1) Select the task and click the event handler tab in BIDS
2) Select OnError event handler in the list
3) Click the enable link and drag a Execute TSQL Task over to the window
4) Create a table in your SQL Server database (create one so you don't litter your user DBs if needed)
5) Open the task and add the connection as needed. Then add this statement
INSERT INTO dbo.TableYouCreated
(PackageName, SourceName, EventInfo)
VALUES (?,?,?)
6) Go to parameter mappings and add 4 new mappings as following
System::PackageName
Input
nvarchar
0
System::SourceName
Input
nvarchar
1
System::ErrorDescription
Input
nvarchar
2
Save and reimport the package and then the event of the errors should insert into the table in detail
Ted Krueger
Blog on lessthandot.com @onpnt on 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 fails with error : The package execution returned DTSER_FAILURE (1).

Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
at Teradata.Client.Provider.WpMessageManager.CheckForError()
at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
at Teradata.Client.Provider.WpLogonManager.Action()
at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
at Teradata.Client.Provider.TdConnection.Open()
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
Elapsed: 6.692 seconds. The package execution failed. The step failed.
SQL Server agent job fails with above error, Please let me know process tohandle it.
Thanks,
Vishal.

The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

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

While i am trying to start the sql server agent job getting the error

Hi,
when ever i am trying to executing the sql server agent job's through manual that time i am getting the below error.

Hi,
when ever i am trying to executing the sql server agent job's through manual that time i am getting the below error.
I searched net for this type of error and found that Latest SP can fix this issue.See below link
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/12181324-bc51-41a5-a8a5-608bfe2725e9/could-not-load-type-smoagentjobbasecollection?forum=sqlsmoanddmo
Can you also refer to this link
http://www.sqldbadiaries.com/2010/12/20/could-not-load-file-or-assembly-error-while-using-tdp-makes-a-come-back/
Also please see this connect also
http://connect.microsoft.com/SQLServer/feedback/details/280907/sql-agent-job-actions-fail-from-job-activity-monitor
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Error While executing a SSIS package which contains a script task through SQL Server Agent job

Similar Messages

Maybe you are looking for