SSIS Jobs in SQL 2012

In SQL 2012 is it possible to execute SSIS packages from agent by invoking dtexec? In SQL 2008 I was running bunch of jobs that invoked dtexec.exe and called packages. I am not having much luck with it.
In SQL 2008 I was executing packages stored in SQL Server by executing a main package that lived on the file system. In my SQL Server Agent job I would execute the main package by using the command line below:
"c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtexec" /f "\\cis-sql2008\sql\MSSQL\JOBS\dataload\dataloadMain.dtsx"
What would be the equivalent of the command above in SQL 2012. I see that Microsoft has introduced deployment models and I am sort of confused between SSISDB and SSIS Catalog.
Any thoughts?
Thanks
SQL Pro

Hi sqlstar,
To run a package stored in SSISDB catalog database, we have three different methods:
Method 1: Create a SQL Server Integration Services Package type job step. We can select the Package source as “SSIS Catalog”, select the SSIS server, and navigate to the target package in the SSISDB Catalog.
Method 2: Create an Operating system (CmdExec) type job step. No matter in SSIS 2012 or another version of SQL Server, we use the
DTExec utility to execute a package (although SSIS runtime component is also required). For a package stored in SSISDB, we can still use the DTExec command lines to execute the package.
For example, in a CmdExec job step, we can use the following command line:
DTExec /ISSERVER "\SSISDB\ISProject\Package.dtsx" /SERVER "\."
Method 3: Create a Transact-SQL script (T-SQL) type job step. In the T-SQL script, we use the
catalog.start_execution stored procedure provided by SSISDB catalog database to start a package execution.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

Similar Messages

  • Not able to run the SSIS package in SQL Server Agent Job in SQL 2012

    Hi,
    I scheduled a job (SQL SERVER AGENT) which will call my SSIS package. This package will execute 5 packages in loop.
    When I execute this job I am getting error as below
    ============================================================
    Started  : 12:30:19 PM 
    Error  : 2014-01-23 12:30:20.37    
    Code  : 0xC00220EC    
    Source  : Execute Package Task     
    Description : Error 0x80070005. Failed to create an instance of empty child package.
        The Distributed Component Object Model (DCOM) configuration or the installation of SQL Server Integration Services,
        may be corrupted on your machine.  End Error 
    Error  : 2014-01-23 12:30:20.37    
    Code  : 0xC00220DE    
    Source  : Execute Package Task     
    Description : Error 0x80070005 while loading package file "D:\SSIS\RetailMobileApp\Staging_Pkg\stg_Category_Master.dtsx". Access is denied.End Error 
    DTExec  : The package execution returned DTSER_FAILURE (1). 
    Started  : 12:30:19 PM 
    Finished : 12:30:20 PM 
    Elapsed  : 1.123 seconds. 
    The package execution failed. 
    The step failed.
    ============================================================
    In the STEPS I have selected as follows:
    Type  : SQL Server Integration Services Package
    Run as: SQL Server Agent Service Account
    Package Source: File System
    What config I need to check here ? This job is not able to access the package stored in the folder.
    Sridhar

    Thanks for your reply. I had created credentials and used this while creating the Proxy account. With the Proxy account I am able to execute the Job Successfully. Concern here is I used my NT account to create this Proxy. Suppose If I left from the
    current project if some one is coming to this project later they need to change the credential with their NT account and run the JOB? Is this right way or we an create any other account in common? If so how?
    Sridhar

  • Running SSIS 2005 in SQL Server Job Agent 2012

    Hi Guys,
    I'm trying to create a job in SQL 2012 that calls an SSIS 2005 package, however i'm getting some issue.  I researched the issue a bit and got this link . The given link suggested to use dtexec as SQL 2012 try to convert it in the memory.
    I used the dtexec  but I'm still getting an issue.
    "Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility  Version 9.00.1399.06 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  4:11:19 PM  Error:
    2015-04-13 16:11:26.24     Code: 0xC0012024     Source: OTH Market Exist?      Description: The task "OTH Market Exist?" cannot run on this edition of Integration Services. It requires a higher level edition.  End
    Error  Error: 2015-04-13 16:11:26.24     Code: 0xC0012024     Source: Arcticle CSV Exist?      Description: The task "Arcticle CSV Exist?"
    cannot run on this edition of Integration Services. It requires a higher level edition.  End Error  Error: 2015-04-13 16:11:26.24     Code: 0xC0012024     Source: BV Market Exist?      Description:
    The task "BV Market Exist?" cannot run on this edition of Integration Services. It requires a higher level edition.  End Error  Error: 2015-04-13 16:11:26.51     Code: 0xC002F210     Source: No Input
    Files Email Execute SQL Task     Description: Executing the query "DECLARE @result int;  EXEC @result = security.dbo.spSendEmail  
    @Subject='[GFK Import & Export] - All Input Files Are Missing',  
    @Message ='Processing has been stopped due to missing input files',  
    @ToID =25,   @ccID =0,  
    @Attachment =''" failed with the following error: "Database 'security' does not exist. Make sure that the name is entered correctly.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly,
    It seems that I do need to upgrade my packages to run in SQL 2012 unless if there's another way without upgrading it that would be great.
    I just want to get the confirmation if possible or not
    Many thanks guys.

    Hi Vaibhav,
    I created 2 jobs. the first job calls a simple package that execute a single SQL. It ran
    successfully when I execute the said job using this command 
    DTEXEC /FILE "\"C:\TFS\WDSHE SSIS Packages from DTS\GFK_Test_package.dtsx\"" /DECRYPT stud10 /CHECKPOINTING OFF /REPORTING E
    2nd Job, calls a complex package which contains several execute process tasks. this job fails with the error mentioned at the top.
    Now, I modified the simple package in the first job and add an Execute Process Task.
    I'm started to get an issue
    Message
    Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility  Version 9.00.1399.06 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  4:51:57 PM  Error: 2015-04-13
    16:52:01.32     Code: 0xC0012024     Source: Unzip BV ZIP      Description: The task "Unzip BV ZIP" cannot run on this edition of Integration Services. It requires a higher level edition.  End Error  DTExec:
    The package execution returned DTSER_FAILURE (1).  Started:  4:51:57 PM  Finished: 4:52:01 PM  Elapsed:  4.212 seconds.  Process Exit Code 1.  The step failed.
    Have you had a similar issues before?
    I will try to install the SSIS service and see how I go. thanks for the link

  • Copying SQL Server Agent - Jobs in SSMS - 2012

    Hi,
    I am using SQL 2012 version.
    when i try to copy the existing sql agent job (job "X") (using, Script Job As--> Create To--> New query window) and paste it into different database it is giving me some errors as below. (this method is working fine with SQL 2005, but not
    with 2012)
    Error :
    @schedule_uid is not a parameter for procedure sp_add_jobschedule.
    Any other way of copying sql agent job in SQL 2012 ???
    Thanks

    See the below article which speaks about behavior changes in sql 2012
    http://technet.microsoft.com/en-us/library/ms143359.aspx
    it has section as below
    Changes to Behavior in Scripting a SQL Server Agent Task
    In SQL Server 2012, if you create a new job by copying the script from an existing job, the new job might inadvertently affect the existing job. To create a new job using the script from an
    existing job, manually delete the parameter @schedule_uid which is usually the last parameter of the section which creates the job schedule in the existing job. This will create a new independent schedule for
    the new job without affecting existing jobs.
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • SSIS Job is getting failed with an error "0x00000005 : Failed to compiled scripts contained in the package.

    Hi All. Could anyone resolve my issue.
    I was created a package with an Script task written in VB.Net.
    The Package was executing Successfully in BIDS.
    But when i tried to exceute the same using Sql server Agent Job, Its getting Failed with the below error message
    "Executed as user: Admin. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.2100.60 for 32-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  5:12:27 PM  Error: 2013-03-13 17:12:32.33    
    Code: 0x00000005     Source: Checking Alcon Files Checking Alcon Files     Description: Failed to compiled scripts contained in the package. Open the package in SSIS Designer and resolve the compilation errors. 
    End Error  Error: 2013-03-13 17:12:32.33     Code: 0x00000005     Source: Checking Alcon Files Checking Alcon Files     Description: BC30179 - enum 'ScriptResults' and enum 'ScriptResults' conflict
    in class 'ScriptMain'., ScriptMain.vb, 156, 22  End Error  Error: 2013-03-13 17:12:32.36     Code: 0x00000005     Source: Checking Alcon Files Checking Alcon Files     Description: The binary
    code for the script is not found. Please open the script in the designer by clicking Edit Script button and make sure it builds successfully.  End Error  Error: 2013-03-13 17:12:34.28     Code: 0x00000005    
    Source: Formating Excel Sheet Formating Excel Sheet     Description: Failed to compiled scripts contained in the package. Open the package in SSIS Designer and resolve the compilation errors.  End Error  Error: 2013-03-13 17:12:34.28    
    Code: 0x00000005     Source: Formating Excel Sheet Formating Excel Sheet     Description: BC30179 - enum 'ScriptResults' and enum 'ScriptResults' conflict in class 'ScriptMain'., ScriptMain.vb, 191, 22  End Error 
    Error: 2013-03-13 17:12:34.29     Code: 0x00000005     Source: Formating Excel Sheet Formating Excel Sheet     Description: The binary code for the script is not found. Please open the script in the
    designer by clicking Edit Script button and make sure it builds successfully.  End Error  Error: 2013-03-13 17:12:51.56     Code: 0x00000004     Source: Checking Alcon Files      Description:
    The binary code for the script is not found. Please open the script in the designer by clicking Edit Script button and make sure it builds successfully.  End Error  Error: 2013-03-13 17:12:51.56     Code: 0xC0024107    
    Source: Checking Alcon Files      Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  5:12:27 PM  Finished: 5:12:51 PM 
    Elapsed:  24.336 seconds.  The package execution failed.  The step failed."
    Please give some solution to this.
    Thanks in advance

    Are you editing this job in SQL 2012? Is it wrapping your paths in \"? Like for example does the command line tab on the step look like this:
    /FILE "\"D:\yourPathGoesHere.dtsx\""  /CONFIGFILE "\"D:\yourPathGoesHere.dtsConfig\"" /CHECKPOINTING OFF /REPORTING E
    That's the problem I had, and I resolved it by recreating the whole thing via SQL Script and getting rid of all those \" things. I think that is preventing SSIS from looking up the precompiled binaries for your Script Task. So you should edit the command
    line manually:
    /FILE "D:\yourPathGoesHere.dtsx"  /CONFIGFILE "D:\yourPathGoesHere.dtsConfig" /CHECKPOINTING OFF /REPORTING E
    Please write back whether that helps you. David Dye's answer didn't help me at all.

  • 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

  • MDW Upload failing on SQL 2012

    I've configured MDW data collection job on SQL 2012 server and the repository server is on SQL 2008 server. But the Upload job is failing on login failure error. The SQl 2012 agent job is taking domain\servername$ to run the job, even i change the account
    to another domain account, it still uses the same account to connect. 
    Is this expected behavior? is there any workaround?
    Thanks
    Jay

    Hi Jay,
    According to your description, you can post the error messages for analysis. In addition, it seems that your SQL Server Agent account (domain\servername$) on SQL Server 2012 has no privileges to access the Management Data Warehouse (MDW) database. By default
    the data collection upload job will run as the SQL Server Agent account, you need to make sure that the SQL Server Agent account has access to the MDW database if it has been configured on a remote server. To ensure this access, you can create a
    SQL Server Agent proxy account and add it to the dc_proxy database role for the msdb database.
    For more details, please review the following link:
    SQL Server 2008 Management Data Warehouse:
    http://msdn.microsoft.com/en-us/library/dd939169(v=sql.100).aspx
    Thanks
    Lydia Zhang

  • Pass Variable to SSIS Package through SQL JOB -2012

    So here is what i am trying to do. 
    I have a EXECUTE SQL Task - that executes a Stored Procedure with a Parameter. EXEC dbo.Procedure @Variable
    I have deployed this SSIS on Server - Now i want to pass different values to this variable using SQL JOB at different times. 
    How can i achieve this in SQL 2012. 
    Thanks

    Hi there,
    MSDN is pretty clear on that:
    Map Query Parameters to Variables in an Execute SQL Task
    If not there are tons of blog posts: http://sqlage.blogspot.ca/2013/07/ssis-how-to-pass-parameter-value-to-ole.html
    Arthur
    MyBlog
    Twitter

  • Issue with SSIS Custom Components - 64 bit SQL 2012

    Hello All,
    Our SSIS packages built on SQL 2008 R2 make use of some custom components. These custom components are installed as part of an MSI. The dll's are copied over to the Windows/assemble [GAC Folder] and also to the Program Files(x86)/SQL Server/110/DTS/* folder.
    The installation does not copy the dll's to the 64 bit program files folder.
    X:\Program Files\Microsoft SQL Server\110\DTS
    These packages are executed via SQL Agent jobs on a 64 bit SQL server and there does not seem be any issue.
    Now we are upgrading our servers to SQL 2012 and we have a new installer for the custom components as well. The new custom components use .NET Framework 4.0 and when installed the dll files get copied over to the Ms.NET 32 bit runtime GAC folder and also
    to the SQL Server DTS Folder in x86. The upgraded packages work only when we set the runtime mode to 32 bit. The packages successfully executes within the 32 bit dtexec utility, but when we try to run the same package using a 64 bit dtexec utility the
    process errors out with a component failed to load message. The package moves data between two SQL Server instances.
    The custom components have always been built for 32 bit runtime. I can run a older package through the dtexec utility (from the 64 bit folder in program files) and it does work without any issues. After the upgrade the package will only execute on
    a 32 bit utility. can someone help me understand this issue?
    Regards, Dinesh

    Thank you Arthur.
    i think we got the answer as well, as the .NET framework 3.0 installer copied the files over to the C:\windows assembly the dtexec utility [32 bit/64 bit] was able to load the components.
    Now with the new installer the files are copied to specific runtime gac folders as Arthur has mentioned. The 64  bit  utility does not find the dlls in the GAC whereas the 32 bit version will find them.
    Regards, Dinesh

  • 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

  • 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 job runs in designer but fails in SQL Agent - timeout error

    I have several SSIS packages that have been running without issue for well over a year. These jobs were imported into SQL Server and run on a schedule with SQL Agent.
    Over the weekend these jobs failed with the message:
    Description: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.  The statement has been terminated.  Source: .Net SqlClient Data Provider  Started:  8:13:01 AM 
    Finished: 8:13:31 AM  Elapsed:  30.155 seconds.  The package execution failed.  The step failed.
    When I look at the package history it doesn't even show that the job attempted to run over the weekend. As such I assume that the error is related to SQL Agent attempting to connect to the SSIS job.
    As stated in the title, the jobs run without issue in the designer.
    I did stop and restart SQL to see if that would have an effect - sadly it did not.
    I attempted to reload one of the packages. More specifically I re-imported it and allowed it to overwrite the existing project, This step completed ok and moved to the next step - deploy the project. It fails to deploy the project with the following error
    Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2218&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
    Server Name: XXXXXXX
    Error Number: -2
    Severity: 11
    State: 0
    Program Location:
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.SqlServer.IntegrationServices.Common.ObjectModel.SqlHelper.ExecuteSQLCommand(SqlStoreConnection storeConnection, CommandType cmdType, String cmdText, SqlParameter[] parameters, ExecuteType execType, Int32 commandTimeout)
       at Microsoft.SqlServer.Management.IntegrationServices.CatalogFolder.DeployProject(String projectName, Byte[] projectStream)
       at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeployExportProjectHelper.DeployProject(CatalogFolder folder, Project project)
       at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.Deploy(CatalogFolder folder, Project project)
       at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.DeployProject()
       at Microsoft.SqlServer.IntegrationServices.Deployment.DeployProjectPage.DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    ===================================
    The wait operation timed out
    It would seem to me that there is an environmental error, though I know of nothing that has changed. I don't know where to look. If you have seen this behavior before or have an idea, I welcome your input.
    Thanks
    Mike

    Hi Mike,
    Based on the error message, we can infer that the issue is caused by connection or command timeout.
    To work around this issue, we can increase the connection timeout and command timeout, buffer size and create two indexes in the SSISDB catalog to improve the performance. For more details, please see:
    http://capstonebi.blogspot.com/2012/09/ssis-2012-deployment-frustrations.html
    Reference:
    https://connect.microsoft.com/SQLServer/feedback/details/804901/ssis-2012-deploying-new-versions-of-large-projects-runs-into-a-timeout-during-deployment-into-ssis-catalog
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Run sql 2008 ssis package into sql server 2012 machine

    Hello,
    I have created a ssis package in sql server 2008 and use a job to execute it pointing to databaseA. works fine.
    Then, I place that package into a sql server 2012 machine and use a job to execute it in the same database, databaseA.
    The error I get is something like:
    can not use the old version in the new version machine.
    Is this really the case or am I doing something wrong please?

    Hi Arkiboys,
    Arthur is right that the error occurs because the SSIS 2008 package cannot be upgraded to SSIS 2012 package. When the SSIS 2008 package is called by SSIS 2012 dtexec utility tool, the package will be upgraded temporarily and the changes won’t be saved. Since
    your current SSIS 2008 package cannot be upgraded automatically, you can create the package from scratch in SSDT installed by SQL Server 2010. Another option isto open the SSIS 2008 package in SSDT or add the package to a SSIS 2012 project, then the upgrade
    will be performed automatically. Then, you can check the error message during the upgrade, which may help you to find the tasks/components that cause the upgrade failure. In this way, you can remove the tasks/components in question from the SSIS 2008 package
    and then upgrade the package, and then add the tasks/components in question in SSDT 2010.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here.
    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

  • Getting error while trying to upload the data in excel from SSIS package through sql agent job

    We are getting below errors.
    Error:
    The Microsoft Jet database engine cannot open the file '\\serversdev\Documents\QC Files\Prod.xls'. It is already opened exclusively by another
    user, or you need permission to view its data.
    Please suggest ASAP
    Regards,
    Ramu
    Ramu Gade

    Hi Dikshan Gade,
    According to your description, you want to upload data from excel to database, when you call ssis package through SQL Server Agent job, you got the error message.
    To troubleshoot the problem, please refer to the following steps:
    Validate that the account has permissions on the file and the folder.
    Verify that the file and the data source name (DSN) are not marked as Exclusive.
    Make sure SQL Server Agent Services service account has the permission to access the database.
    We 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. For more information about the issue, please refer to
    the following KB article:
    http://support.microsoft.com/kb/306269
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    Wendy Fu
    TechNet Community Support

Maybe you are looking for