Advice on SSIS package running in a procedure

Hi guys, I'm struggling with a situation like this:
I got a SQL job Obava, within the job I have got two package ( I mean I set up two package on cascade). If I run
EXEC
msdb.dbo.sp_start_jobN'Obava'
SSMS returns
Job 'Obava' started successfully.
But nothing happens. If I run the package directly everything is ok ( even the mail sent to myself).
Any thoughts why? Thanks

Is the package in a remote path? Is the path given local path of the folder? Are you configuring the job in the same machine? Also does the account executing the package from the job has access to the path where package resides?
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

Problem in package run inside stored procedure

i have ssis package to import data from excel to database.
package is running correctly inside BIDS.
but when i run package under stored procedure it is giving error :
Error:   Code: 0xC0014023
   Source: loop sheets in excel
   Description: The GetEnumerator method of the ForEach Enumerator has failed with error 0x80040E21 "(null)". This occurs when the ForEach Enumerator cannot enumerate.

Hi BI_DEV_19,
Does the package connects with network resources? If so, try set the job step to run under a proxy account that is created based on a domain account. In BIDS, the package runs under the Windows account that you log onto the operating system.
The error message “The GetEnumerator method of the ForEach Enumerator has failed with error 0x80040E21” may occur because the ADODB.dll file is corrupted or missing. You can check whether the ADODB.dll exists in the following folder:
C:\program files (x86)\Microsoft.NET\Primary Interop Assemblies
In this situation, you can back up the existing ADODB.dll file, and copy one from another machine to this server.
Regards,
Mike Yin
TechNet Community Support

Getting error code 1 when calling SSIS package from a stored procedure (SQL Server 2008 R2)

Hello,
I am trying to execute a SSIS package from SQL Server 2008 R2 stored procedure but getting error code 1 (as per my knowledge, error code description is as below:
0 The package executed successfully.
1 The package failed.
3 The package was canceled by the user.
4 The utility was unable to locate the requested package. The package could not be found.
5 The utility was unable to load the requested package. The package could not be loaded.
6 The utility encountered an internal error of syntactic or semantic errors in the command line.
Details:
I have a stored procedure named "Execute_SSIS_Package" (see below sp) which executes 'Import_EMS_Response' SSIS package (when I execute this package directly from SQL Server BID it works fine it means package itself is correct) and calling
it from SQL as:- EXEC Execute_SSIS_Package 'Import_EMS_Response'.
Here I receives error code 1.
Can anyone help me to resolve this issue please?
Thanks in advance!
CREATE PROCEDURE [dbo].[Execute_SSIS_Package]
@strPackage nvarchar(100)
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
DECLARE @cmd VARCHAR(8000)
DECLARE @Result int
DECLARE @Environment VARCHAR(100)
SELECT @Environment = Waarde
FROM Sys_Settings
WHERE Optie = 'Omgeving'
--print @Environment
SET @strPackage = '"\W2250_NGSQLSERVER\BVT\' + @Environment + '\' + @strPackage + '"'
SET @cmd = 'dtexec /SQL ' + @strPackage + ' /SERVER "w2250\NGSQLSERVER" /Decrypt "BVT_SSIS" /CHECKPOINTING OFF /REPORTING E'
--print @cmd
EXECUTE @Result = master..xp_cmdshell @cmd, NO_OUTPUT
--print @Result
END

It has something to do with the security.
E.g. cmdshell is not enabled or the caller has not rights over the package.
There could be a syntax error, too.
I suggest you make the package runnable off a SQL Agent job then trigger the job from the stored proc with
sp_start_job <job name>
Arthur
MyBlog
Twitter

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.

SSIS package runs from BIDS and by Executing package, but failing with Job

I have SQL Serve 2012 SSIS. I have problems to run from SQL Server Agent Job.
Steps runs SSIS package without configuration file. Package Run64BitRuntime is False in BIDS.
Package is runned by SQL Server Agent Service Account.
Server does not have Office 2010/2013 installed. Should it be installed?
ERROR1:
Description: The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered.
If the 64-bit driver is not installed<c/> run the package in 32-bit mode.
ERROR2: (here SSIS package is trying to import XML source, but cannot file file)
Description: An error occurred with the following error message: "Could not find file 'D:\Integration\Metadata\'.".
Kenny_I

Hi Kenny,
It seems like you are using Excel as source file right? If yes, then please follow below steps:
Edit the job step and Check the option: Use 32 bit run time. Below is the screenshot for the same.
Please let me know for any questions.
Thanks, Madhu

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 Package "running" in Job History?

My first post to Technet fora: Hello to everyone!
Last March our DW-system was migrated from SQL Server 2005 to SQL Server 2008 R2. Several SQL Server Agent jobs using SSIS packages were also migrated. The packages were converted from 2005 to 2008 with Visual Studio conversion tools.
After the migration several (but not all) of these jobs show a peculiar behavior in 'View Job History'.
As you can see the job history consists of two rows. But the lower one - from Execute Package Utility - has the green 'arrow head', as if it were still running.
In the Selected Row Details Pane, however, everythig seems to be ok:
Message
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 8:00:02
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 8:00:02
Finished: 8:00:03
Elapsed: 1.482 seconds
Is this something to be concerned about? The job seems to work just fine (a simple sql query, results to flat file).

Welcome to the fora :)
Strange, everything indicates the job finished, except for that little icon.
I would ignore it and classify it as a visual glitch, but I understand it can be annoying.
MCTS, MCITP - Please mark posts as answered where appropriate.

SQL 2012 SSIS package runs from the command line (dtexec.exe) and completes right away ...

Hi
I’m upgrading our SSIS packages from SQL 2005 to SQL 2012 .
Everything is working fine in Visual Studio, but when I’m submitting dtexec.exe it’s finishing right away in the command line (the actual execution takes long time).
It looks to me that as the return code doesn’t pass properly.
As I have depending tasks how I can make sure all jobs will be executed in the proper order.
(We never had this issue in SQL 2005)
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn>dtexec.exe /ISSERVER "\"\SSISDB\Direct_Prod\Direct_SSIS_Package
\DD_Load_Customer.dtsx\"" /SERVER TORSQLSIS01 /ENVREFERENCE 2
Microsoft (R) SQL Server Execute Package Utility
Version 11.0.2100.60 for 32-bit
Copyright (C) Microsoft Corporation. All rights reserved.
Started: 10:21:55 AM
Execution ID: 21138.
To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report
Started: 10:21:55 AM
Finished: 10:21:56 AM
Elapsed: 0.766 seconds

As per MSDN /ENVREFERENCE argument is used only by SQL Server Agent
see
https://msdn.microsoft.com/en-us/library/hh231187.aspx
below part is what it says
/Env[Reference] environment reference ID
(Optional). Specifies the environment reference (ID) that is used by the package execution, for a package that is deployed to the Integration Services server. The parameters configured to bind
to variables will use the values of the variables that are contained in the environment.
You use /Env[Reference] option together with the /ISServer and the /Server options.
This parameter is used by SQL Server Agent.
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

SSIS Package runs from the Package executer and from BIDS but not from the sql agent schedular

Hi Experts,
I have 2 packages :
1. Main Package -For each loop package
2. Sub Package - As we need to collect the information from several other DB with same table structures .
The Main Package calls the Sub Package and loops through several linked server (9 of them ) .
From last 2 weeks the scheduler is running on time but no data is loaded into our destination DB .
Daily i need to manually run the package .
The SQL Agent task is scheduled using the service account from which the sql server was installed on the server so it has the full privledges.
If i run the Main package from the BIDS i see 2 messages related to the configuration of xml no error message and executes fine.
If i run the Package from the execute package utility it runs fine.
Now if the package is scheduled for a nightly load it executes fine successfully no error message also in the Job History
but when i check for the data loaded on that day no data loads up in the destination DB . Due to this behavior of the sql agent even if am on leave i have to login on to the server and exec manually so if at times i forget the exec we are in big trouble
Please experts help me in troubleshooting the issue.
Thanks
Priya

Hi Visakh16 ,
We are using a service account to run the package .. Earlier in the BIDS i was getting the error crypotgenic
something password .. I googled out and changed the security : Protection Level : Dont save Sensitive
information . So that error now its not showing in the BIDS
And how is login mapping done for the linked servers? You've configured a mapped login for the service account also?
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

How to Execute SSIS package through MySQL Procedure

Hi Everyone,
How to Execute SSIS package from MySQL Stored Procedure.
Please share your suggestions on this.
Regards,
Vaishu

I am not sure whether you have SSIS license version installed in the system where MYSQL is there. In order to run SSIS package we need to have DTEXEC executable file and it comes with SSIS license version.
An SSIS package can be executed from command prompt as,
C:\>dtexec /f E:\package.dtsx
I am not expert in MYSQL however in TSQL we can run dos command or scripting language such as vbscript.
Similarly you need to check in MYSQL. This is MSSQL Server forum.
Refer
http://www.ehow.com/how_8789576_call-ssis-package-vbscript.html
http://www.mssqltips.com/sqlservertip/1775/different-ways-to-execute-a-sql-server-ssis-package/
Regards, RSingh

Error while running the SSIS package from SQL DB to excel file - export option

hi all,
I have 4.6 million records in my sql db and i want to copy this into a excel file. for this i went to the db and rt click and export to command and started the ssis package running. but after
few minutes, it throws me an error that "error in transferring data into excel file."
Can anyone help me why this happened and the resolution ?
help is appreciated!
Copying to `excel1_Wbook` (Error)
Messages
Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x8007000E.
(SQL Server Import and Export Wizard)
Error 0xc0047022: Data Flow Task 1: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Destination - excel1_Wbook" (217) failed with error code 0xC0202009 while processing input "Destination Input" (228).
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.
(SQL Server Import and Export Wizard)
Error 0xc02020c4: Data Flow Task 1: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
(SQL Server Import and Export Wizard)
Error 0xc0047038: Data Flow Task 1: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Source - excel1_Wbook returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The
meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)

You need to split your data and create (at least 5) worksheet targets.
For example if you have a ROW_NUMBER column you can use for instance a
Conditional Split for something like:
ROW_NUMBER % 5 == 0 for Case 1 (excel 1)
ROW_NUMBER % 5 == 1 for Case 2 (excel 2)
ROW_NUMBER % 5 == 2 for Case 3 (excel 3)
ROW_NUMBER % 5 == 3 for Case 4 (excel 4)
ROW_NUMBER % 5 == 4 for Case 5 (excel 5)

DTEXEC does not fail when SSIS package fails

I need to run my SSIS 2012 packages through the catalog with DTEXEC. This works very well, except that if my SSIS package fails, DTEXEC does not fail. I need DTEXEC to fail, so my scheduler knows that there is an error.
I use the following command:
dtexec /ISServer "\SSISDB\MyFolder\MyProject\MyPackage.dtsx" /Ser MyServer /Par $Package::Partition;201412 /Env 5
When I check the status of the run in the Catalog, it is failed.
When I used SSIS 2008, I had no problem getting DTEXEC to fail when the packages failed.

I've had the same problem, and come up with the following prototype for a SQL Script which I run in our JAMS Enterprise Scheduler. It uses SSISDB stored procedures to start the SSIS package and polls every 5 seconds to report any messages, and final
status code of the package. JAMS parameters are delimited by << >> symbols, and will need to be changed for your scheduler/batch process. I guess the script could be converted to a stored procedure. I'm also hoping it will work with SQL High
Availability groups to ensure the SSIS package runs on the server that's hosting the active database.
DECLARE @execution_id BIGINT
DECLARE @status INT= 1
DECLARE @Event_Message_id BIGINT= 0
DECLARE @Last_Event_Message_id BIGINT= 0
DECLARE @message_time DATETIME2(7)
DECLARE @message NVARCHAR(MAX)
--Create a SSIS execution for the required SSIS package and return the execution_id
EXEC [SSISDB].[catalog].[create_execution] @package_name = N'<<pPackageName>>.dtsx',
    @execution_id = @execution_id OUTPUT, @folder_name = N'<<pSSISFolderName>>',
    @project_name = N'<<pSSISProjectName>>', @use32bitruntime = <<p32Bit>>, @reference_id = NULL
RAISERROR('Starting SSIS package <<pPackageName>> with execution_id %I64d on server %s',0,0,@execution_id,@@SERVERNAME) WITH NOWAIT
--Set the logging level 0-none, 1-basic (recommended), 2-performance, 3-verbose
EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id,
    @object_type = 50, @parameter_name = N'LOGGING_LEVEL',
    @parameter_value = <<pLogging_Level>>
--Start the package executing
EXEC [SSISDB].[catalog].[start_execution] @execution_id
WHILE @status IN ( 1, 2, 5, 8 ) --created (1), running (2), canceled (3), failed (4), pending (5), ended unexpectedly (6), succeeded (7), stopping (8), and completed (9).
    BEGIN
        WAITFOR DELAY '00:00:05'
    --Get the status to see later if we've finished
        SELECT @status = status
        FROM    SSISDB.catalog.executions
        WHERE   execution_id = @execution_id
    --Are there any event messages since we last reported any?
        DECLARE curEventMessages CURSOR FAST_FORWARD
        FOR
            SELECT event_message_id ,
                    message_time ,
                    message
            FROM    SSISDB.catalog.event_messages
            WHERE   operation_id = @execution_id
                    AND event_message_id > @Last_Event_Message_id;
        OPEN curEventMessages
        FETCH NEXT FROM curEventMessages INTO @Event_Message_id, @message_time,
            @message
        WHILE @@FETCH_STATUS = 0
            BEGIN
        --We've found a message, so display it - watch out for % signs in the message, they'll cause an error if we don't replace them
                SET @message = CONVERT(NVARCHAR(MAX), @message_time, 113)
                    + ' ' + replace(@message,'%',' percent')
                RAISERROR(@message,0,0) WITH NOWAIT
                SET @Last_Event_Message_id = @Event_Message_id --Make a note that we've reported this message
                FETCH NEXT FROM curEventMessages INTO @Event_Message_id,
                    @message_time, @message
            END
        CLOSE curEventMessages
        DEALLOCATE curEventMessages
    END
--@Status indicates that package execution has finished, so let's look at the outcome, and error if there's a problem
IF @status = 7
    RAISERROR('Package Succeeded',0,0)
ELSE
    IF @status = 9
        RAISERROR('Package completed',0,0)
    ELSE
        IF @status = 3
            RAISERROR('Package Cancelled',16,1)
        ELSE
            IF @status = 4
                RAISERROR('Package failed (see error message above)',16,1)
            ELSE
                IF @status = 6
                    RAISERROR('Package ended unexpectedly',16,1)
                ELSE
                    RAISERROR('Package ended with unknown status %i',16,1,@status)

SSIS package flow based on a scheduling configuration table.

I have a table called Tbl_Scheduler.
This scheduler table contains
scheduler id ,scheduler description,as shown below.
1 ,Runs between 10 th of current month and 20th of current month
2 ,Runs at last day of the month
3 ,Runs at first day of the month
Scheduler Id will come from first task(it is given in a configuration table),
second task should check this scheduler id on scheduler table and
verify whether the current run date is falling under the criteria,which is given as scheduler description.
If it is not,need to stop the package flow.
SSIS package is scheduled from SQL agent job in every 10 mins.Could you please let us know,how I can design the same.
Also please feel free to advise to change the table design.

Stopping running packages is a bad idea in general. You must specifically design a package for being stopped any time which isn't always possible, often not at all.
And running a package repeatedly in short intervals is not a SOP either.
To trigger a SSIS package run, the easiest would be via sp_start_job <name> once you have your package set up to run in Agent.
Arthur My Blog

SSIS packages are failing after upgrade to SQL server 2014

Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.

I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari

Find out why an SSIS package takes so long execute ?

Is there any guideline which shows how to find out why a package is taking "too long" to execute ? I guess one situation could be that an SQL query (if you have one) is taking too long. Perhaps the query could be optimized or perhaps its table
could use indexes. Any more scenarios which can make execution take too long ?

I guess it would be better to google "ssis package running slowly" or something like that and read each post to learn reasons for slow execution. Some links I got -
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/55f3bc47-675f-487f-8bc1-b9c9d6b2a0d9/-ssis-package-running-very-slow-writing-512kb-chunk-per-cycle-?forum=sqlintegrationservices
http://stackoverflow.com/questions/2678119/is-there-a-reason-why-ssis-significantly-slows-down-after-a-few-minutes
http://stackoverflow.com/questions/16181921/dataflow-task-in-ssis-is-very-slow-as-compared-to-writing-the-sql-query-in-execu
These ones caught my attention -
http://blogs.msdn.com/b/mattm/archive/2011/08/07/troubleshooting-ssis-package-performance-issues.aspx
http://sqlblog.com/blogs/rob_farley/archive/2011/02/17/the-ssis-tuning-tip-that-everyone-misses.aspx

Advice on SSIS package running in a procedure

Similar Messages

Maybe you are looking for