Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

Hi,
how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
This question has worried me for days.
Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
Or just an new solution instead of using the catalog.deploy_project?
best wishes from Qingyuan Lee.

Sorry, my description may be confusable.
I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
In fact,  I don't care about the authority.
I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
so, using EXECUTE AS to change the execution context is accaptable.
The requirement for a Windows Authentication Account makes sense.
I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
Thanks very much for your help.

Similar Messages

  • Is it possible to deploy SharePoint or its Service Applications on: multiple DB-Servers and multiple SQL Instances?

    Hello Forum,
    We have a SharePoint 2013 farm (Enterprise edition) that uses one single SQL Server 2012 (Standard edition). That statement means: All my SharePoint DBs e.g. (Config, Admin, Content, and Service Apps) DBs are hosted and running onto one single instance e.g.
    Server1\SQLInstance1.
    We have some new requirements to install and configure BI tools such as: PerformancePoint services and PowerPivot. BI tools require either SQL Server 2012 Enterprise or BI editions, and we do NOT want to upgrade our current SQL Server1\SQLInstance1
    Instead, We have other separate SQL Server instance which is enterprise edition let's name it (ServerX\InstanceX) that is running standalone, and we are thinking or using it, and my 2 questions are:
    1) Can we use this other separate
    SQL Server instance which is enterprise edition to host the create and hosts the DBs of PerformancePoint services and PowerPivot ?
    2) My second question is the same: Can I create PerformancePoint services application in my SharePoint farm, But in the Database Server field, I fill up
    the details of the other DB server ServerX\InstanceX  which is the one that is SQL
    enterprise edition ? Will this work ?
    Any official Microsoft resources/links tell that it is possible to deploy SharePoint or its service applications on multiple DB-Servers and multiple SQL Instances?

    Thank you Alex and Anil,
    What are the ramifications of that?
    I mean, Assuming that I have created such a farm where most of SarePoint DBs in Standard SQL instance while the PerformancePoint service application and others e.g. PowerPivot and reporting service are deployed and configured onto other Enterprise SQL instance.
    Are there any recommendations or concerns that you would like to draw my attention to ?

  • What is the most common way of deployment of SSIS package?

    Hi everybody,
    I am new to SSIS. I have created an SSIS package in development server. I want to deploy it to production server. What is the most common and efficient way of deployment? Please let me know the procedure in details.
    Thanks in advance.
    Regards,
    Anujit Karmakar
    Anujit Karmakar Sr. Software Engineer

    Hi Anujit,
    SSIS deployment is nothing but just to copy the .dtsx files from DEV to PROD. (Either file system or SQL Server)
    File system deployement is the common way of SSIS deployment
    1. File system deployment using manifest file
    http://sivasqlbi.blogspot.in/2012/05/ssis-step-by-step-process-of-creating.html
    2. SQL Server deployment using manifest file
    http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
    3. By using Command line
    http://www.mssqltips.com/sqlservertutorial/215/command-line-deployment-tool-for-ssis-packages/
    If you are working on SQL Server Data Tools (2012), then you need to go through below article
    http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-1-of-2/
    -Vaibhav Chaudhari

  • Ssis 2012 parallel execution of ssis packages using catalog database hangs

    i have a simple ssis package in 2012 where I am executing several data flow tasks in parallel using sequence containers, however very often the sql job just runs forever although all the tables have been loaded or I cant see whats going on, the job neither
    fails nor succeeds, just goes on executing,is there an issue with executing several data flow tasks in parallel, why does the job continue to run forver, how to troubleshoot and fix the error, please guide, are there any issues using the catalog db execution,
    is that the reason this behavior is showing?

    multiple execute sql tasks within sequence containers running to execute the ssis packages deployed in ssisdb in sunchronous mode using the catalog database execution model
    all of the ssis packages that have the data flow taks retrieve data from source to 3 different tables.
    some of them push data into the same table.
    please let me know if you need more information.
    the job just runs forever, looks like all the data flow tasks ran and it is still running, because I don't see an increase in the row count of the tables, I may be wrong, if I check the execution status, 1 task does not show as succeeded, I don't know why
    thanks  a lot for ur help, ur help is much appreciated nik

  • Error running SSIS package to do with encrypting/decrypting password. Help needed.

    Getting this error. Can anyone shed some light? This is the first promote since 2009. Protection level of the package is 'EncryptSensitiveWithPassword' I'm new at SSIS so don't assume I know anything.
    10/30/2014 16:11:06,HPAddress_Export,Error,0,SSQLTST01\SSQLTST02,HPAddress_Export,(Job outcome),,The job failed. 
    The Job was invoked by User AHCCCS\Administrator.  The last step to run was step 1 (Step 1).,00:00:02,0,0,,,,0
    10/30/2014 16:11:06,HPAddress_Export,Error,1,SSQLTST01\SSQLTST02,HPAddress_Export,Step 1,,Executed as user: AHCCCS\svcssqltst01. ....00.5324.00 for 32-bit 
    Copyright (C) Microsoft Corp 1984-2005. All rights reserved.   
    Started:  4:11:06 PM  Error: 2014-10-30 16:11:07.05    
    Code: 0xC001405F     Source:      
    Description: Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information. 
    End Error  Error: 2014-10-30 16:11:07.37    
    Code: 0xC001405F     Source:      
    Description: Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information. 
    End Error  Error: 2014-10-30 16:11:07.79    
    Code: 0xC0202009     Source: HPAddress_ExportPackage Connection manager "SQL.HealthPlanAddressChanges.hpac"    
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D. 
    An OLE DB record is available.  Source: "Micros... 
    The package execution fa...  The step failed.,00:00:02,0,0,,,,0

    Hi,
    From the error message “Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information.“, it seems that the error is caused by the password to decrypt
    an encrypted XML node was not specified or incorrect.
    Besides, the EncryptSensitiveWithPassword Protection level means user should use a password to encrypt only the values of sensitive properties in the package. To open the package in SSIS Designer, the user must provide the package password. If the password
    is not provided, the package opens without the sensitive data and the current user must provide new values for sensitive data. If the user tries to execute the package without providing the password, package execution fails.
    So in order to resolve this issue, we should provide the password when executing the package. When you execute a package with this setting using DTEXEC, you can specify the password on the command line using the /Decrypt password command line argument.
    Reference:
    Access Control for Sensitive Data in Packages
    Securing Your SSIS Packages Using Package Protection Level
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Trying to Execute Catalog SSIS Package using Catalog stored proc by a Master SSIS package inside a Loop

    Hi Guys ,
    To Execute Packages deployed in Catalog , I have created a wrapper SP  which internally calls  catalog SP  ( below is the code )
    ALTER PROCEDURE [Publish].[usp_ExecutePackages]
                  @PackageName NVARCHAR(255) 
           ,      @ProjectFolder    NVARCHAR(255) 
           ,      @ProjectName NVARCHAR(255) 
    AS    
    BEGIN
    SET NOCOUNT ON;
    DECLARE @Execution_id BIGINT ;
    EXEC [SSISDB].[catalog].[create_execution] @package_name
    = @PackageName
    ,   @execution_id
    = @Execution_id OUTPUT
    ,   @folder_name
    = @ProjectFolder
    ,   @project_name
    = @ProjectName
    ,   @use32bitruntime=
    True;
    EXEC [SSISDB].[catalog].[set_execution_parameter_value] 
    @execution_id,  
    @object_type=50, 
    @parameter_name=N'SYNCHRONIZED', 
    @parameter_value=1
    EXEC [SSISDB].[catalog].[start_execution]            @Execution_id
    Since i have multiple Packages , I am looping through list of PackageName and trying to pass package names to this SP by ExecureSQLTask inside ForLoop Container . But it errors out saying 
     "Cannot access the package or the package does not exist. Verify that the package exists and that the user has permissions to it.
    BUt same Execute SQL task , if i keep it outside the ForLoop Container it works perfectly fine . 
    I am  clueless , Please Please HELP me ASAP :( 
    Question :
    How is that possible to execute same SP with same parameter outside Container , But not in SEQUENCE or FORLOOP or FOREACH Container ?
    Also 
    How to make a master package to execute SSIS deployed packages via TSQL using catalog stored proc ?
    Please help me out .
    Thanks 
    Prasanna Selvaraju

    Hi , 
    After debugging i am getting parameter values as  
    {Extract - ARTL.dtsx\r\n} Unable to evaluate the expression.
    Why do i get  \r\n which i dont want in parameters .
    Actually i pick the values of package name from a custom table . I check it there are no spaces in the cell.
    Any IDEA WHY ? Please help
    Finally it worked to call Wrapper Class for EXEC [SSISDB].[catalog].[create_execution]
    stored procedure .
    Basically , ERROR MESSAGE is culprit
     "Cannot access the package or the package does
    not exist. Verify that the package exists and that the user has permissions to it. 
    Above Message : causing us to think
    its an Access issue , But actually when you pass parameter incorrectly even a " " space or "\n" extra to value, you will get that error .
    Nothing related to access problem .
    Actually , In the parameter which i was passing :
    {Extract - ARTL.dtsx\r\n} --> String with Enter / Carriage Return and Break line was there 
    I have removed the Enter in that variable value .
    Now its WORKING FINE ! Hurry :D :) 

  • SSIS package not able to connect to XLSX file under SQL Agent Job

    I have a very simply package using an Excel connection to an XLSX file.  It's a straight read of the file and import onto a table. 
    The package works fine in Visual Studio 2008 development and also runs fine when executing on the (server I copied it to) under Integration Services.    
    However, under a SQL Agent, the package (32-bit is checked) can not acquire the connection to an excel file.   I use UNC pathing to the file.  I've read other posts about similar problems and tried various scheduling options (including Owner of
    job).   
    I even tried a to trigger it with a command-line which did not work: 
    "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTEXEC.exe" /sq "\our packages\My_XLSX_File_Import" /SERVER myserver /X86  /CHECKPOINTING OFF /REPORTING E
    All errors are:   "DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209302." 
    I can certainly post more, if someone can help.   Sorry, but I am not getting the right help form those posts.   
    Please, are there any hints at how I can get the Agent job to work? 

    All errors are:   "DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209302." 
    I can certainly post more, if someone can help.   Sorry, but I am not getting the right help form those posts.   
    Please, are there any hints at how I can get the Agent job to work? 
    Ensure that below correct drivers are installed on your target server because I see that file is
    .xlsx
    Microsoft Access Database Engine 2010 Redistributable
    Please refer:
    http://microsoft-ssis.blogspot.co.in/2014/02/connecting-to-excel-xlsx-in-ssis.html
    Cheers,
    Vaibhav Chaudhari
    MCP, MCTS, MCSA (SQL Server 2012)

  • A compare SSIS package checked out with TFS version in VS 2012 no longer shows messagebox 'The files are identical'

    Hello,
    Recently I have had started work on a development system that has VS 2012 and SQL Server Data Tools For VS2012. One thing that annoys me is the fact that a source comparison between a checked out package and the version stored in TFS
    no longer displays the message 'The files are identical', but instead opens the text editor with 2 panes for both sources as if there were differences, with sliders at the right side that do not show any differences (everything in B&W of course). A simple
    message like we had in VS2008 'The files are identical' would suffice to me. On the other hand when you check in the files with VS 2012 and they had not changed then the source control system warns that it did not make any changes since the files
    were identical. Why did the VS 2012 team fix something that worked ? Is there some advantage that I am missing?
    Jan D'Hondt - Database and .NET development

    I did not see such an option, I asked around, appears nobody knows, but I admit there could be a way.
    I still suggest opening an MS Connect so somebody from the development team would respond.
    Arthur My Blog

  • Deploying a copy of existing database with a different name on the same server

    I am a developer(an inexperienced one) trying to understand what is the best way to deploy a brand new database with
    the exact same schema as an existing DB on the same server, but with a different name. I want to preserve the data in all reference tables which I can do by having the relevant post-deployment scripts run after the deployment. 
    What I can't understand is how the project should be set up to deploy database Customer_2 if database Customer_1 exists on
    this server - the Visual Studio project contains DB Customer and I need to find a way to be able to deploy Customer_N (but without creating N identical DB's in the project). I checked a ton of articles and blogs, and feel dumb asking this question but haven't
    been able to understand it yet. Any help would be appreciated.

    Hello,
    Maybe the TargetDatabase and the DeployToDatabase properties can help you.
    http://www.asp.net/web-forms/tutorials/deployment/web-deployment-in-the-enterprise/deploying-database-projects
    You can deploy multiples databases from one project if you want, as explained on the following
    post:
    http://stackoverflow.com/questions/1544966/gdr-deploying-multiple-database-targets-with-one-project
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Error when deploying SSIS package in 2012

    Hi,
    I am trying to deploy a SSIS package to 2012 version. But i am getting error as  below,
    TITLE: SQL Server Integration Services
    There was an exception while loading Script Task from XML: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
    The system cannot find the file specified.
    File name: 'Microsoft.VisualStudio.Tools.Applications, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
       at Microsoft.SqlServer.IntegrationServices.VSTA.VstaHelper.<CleanUp>b__1b()
       at Microsoft.SqlServer.IntegrationServices.VSTA.MtaExecution.Run(Action action)
       at Microsoft.SqlServer.IntegrationServices.VSTA.VstaHelper.CleanUp()
       at Microsoft.SqlServer.VSTAHosting.VSTAScriptingEngine.DisposeVstaHelper()
       at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.MigrateVSTA21ScriptProject(XmlElement elemProj, IDTSInfoEvents events)
       at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)
    There are 4 packages of same version,  i get this error only for 2 packages and other 2 am able to deploy successfully. Can someone tel mewhat would be the issue.
    the same package is successfully deployed from my colleague machine.
    Mano

    Hi Manon,
    According to the error message, the packages that cannot be deployed should include Script Task/Component. But the package that can be deployed without problem include Script Task/Component, right? If so, the issue should occur because certain Visual Studio
    Tools for Applications (VSTA) Runtime has been installed:
    Microsoft Visual Studio Tools for Application x64 Runtime3.0
    Microsoft Visual Studio Tools for Application x86 Runtime3.0
    You can check it from the Programs and Features panel. Then, you can install the exact VSTA Runtime from the
    \redist\VSTA\runtime\ folder of the SQL Server install media.
    Reference:
    https://connect.microsoft.com/SQLServer/feedback/details/776248/could-not-load-file-or-assembly-microsoft-visualstudio-tools-applications-core
    Regards,
    Mike Yin
    TechNet Community Support

  • Individual SSIS Package deployment in SQL server 2012

    Hi,
    I am developing the SSIS packages in sql server 2012.
    I want to know how we can deploy individual SSIS packages as I will be editing the required packages if need be then I have to deploy that package only instead of entire project deployment.
    Please help me on this.
    Regards,
    Ramu
    Ramu Gade

    Hi Ramu,
    According to your description, you want to deploy a single package instead of entire project in SQL Server 2012.
    In SQL Server 2012, the unit of deployment to the SSIS catalog is a SSIS Project. Each SSIS project contains one or more SSIS packages. We couldn’t directly deploy a single package in Project Deployment Model.
    To work around this issue, we can refer to the following suggestions:
    SSMS-->Integration Service Catalogs-->SSISDB-->Your project-->projects. Right click on the projects, and choose "Import Packages...". Then make use of the Project Conversion Wizard to select the packages that you want to deploy, deploy
    the generated .ispac file to SSIS Catalog.
    The command line tool DTUTIL.EXE which can be used to deploy SSIS packages.
    References:
    SQL Server 2012 - Project Deployment Model - Deploy a single package
    Command line deployment tool for SSIS packages
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

    I am working in a Product based company.
    We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
    I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
    I have used "Script Component" in my package.
    We will take only DTSX package file to the customer places and run using SQL Agent Job daily. 
    Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
    Who are all(Customer Environments) using SQL 2012, I am facing the below issue 
    The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
    Still the same package is running fine for some of the customers having SQL 2012.
    I am getting the above error only for few customers.
    Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

    Hi Katherine,
    I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
    Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
    Here is my Simple .net code
    /* Microsoft SQL Server Integration Services Script Component
    *  Write scripts using Microsoft Visual C# 2008.
    *  ScriptMain is the entry point class of the script.*/
    using System;
    using System.Data;
    using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
    using Microsoft.SqlServer.Dts.Runtime.Wrapper;
    [Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
    public class ScriptMain : UserComponent
        public override void PreExecute()
            base.PreExecute();
              Add your code here for preprocessing or remove if not needed
        public override void PostExecute()
            base.PostExecute();
              Add your code here for postprocessing or remove if not needed
              You can set read/write variables here, for example:
              Variables.MyIntVar = 100
        int counter = 0;
        public override void Input0_ProcessInputRow(Input0Buffer Row)
            if (counter == 0)
                counter = Convert.ToInt32(Row.JurisCount);
            Row.JurisKey = counter;
            counter = counter + 1;
    PAVAN MSBI

  • SQL SERVER - Error while executing SSIS package on specific environment : Connection manager - The specified module could not be found

    I have deployed my SSIS packages on SQL 2008 server.
    I have a .bat file which will invoke these packages and also the bat file is placed in the server where the SSIS packages are deployed.
    Scenario 1:
    I double clicked on the bat file to invoke the SSIS packages and ; this executed successfully
    Scenario 2:
    I have used the IBM Tivoli work scheduler(TWS)  to invoke the bat file which in tern will invoke the ssis packges; 
    but when i do this i am getting the below error
     Code: 0x8007007E
       Source: SSIS_Master_Event_Data_Transfer Connection manager "Config DB"
       Description: The specified module could not be found.
    Config BD is a connection manager which will get the connection string from the config file of the SSIS package.
    Please help me to resolve this issue.
    Regards,
    Prakash

    Check you TWS jobmanrc.cmd configuration file.   You may need to add a PATH environment variable in that file that includes your SQL Server file locations.   When TWS jobs are executed, they may not be executing with the same
    PATH variable as when you execute the SSIS outside of TWS.

  • 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 compiled successful, in SQL Server Integration Service package executed sucessful, But fail to run in MS SQL Job Scheduler

    Hi Everyone,
    I having a problem to transfer data from MS SQL 2005 to IBMAS400. Previously my SSIS was running perfectly but there is some changes I need to be done in order for the system to work well. Considers my changes are minimal & just for upgrades (but I did
    include DELETE statements to truncate AS400 table before I insert fresh data from MS SQL table to the same AS400 table), so I compile my SSIS package & it run successfully & I passed it into MS SQL Integrated Service as 1 of the packages & manually
    executed the package & the result is the same, that mean it was successful again but when I try to run it in a MS SQL Job Scheduler, the job failed with these message shown below as extracted from the job View history. 
    Date today
    Log Job History (MSSQLToAS400)
    Step ID 1
    Server MSSQLServer
    Job Name MSSQLToAS400
    Step Name pumptoAS400
    Duration 00:00:36
    Sql Severity 0
    Sql Message ID 0
    Operator Emailed
    Operator Net sent
    Operator Paged
    Retries Attempted 0
    Message
    Executed as user: MSSQLServer\SYSTEM. ... 9.00.4035.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    
    Started:  today time  
    Error: on today time     
    Code: 0xC0202009     Source: SSISMSSQLToAS400 Connection manager "SourceToDestinationOLEDB"     
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. 
    Error code: 0x80004005.  An OLE DB record is available.  
    Source: "IBMDA400 Session"  
    Hresult: 0x80004005  
    Description: "CWBSY0002 - Password for user AS400ADMIN on system AS400SYSTEM is not correct ".  End Error  
    Error: today     
    Code: 0xC020801C     
    Source: Data Flow Task OLE DB Destination [5160]     
    Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "DestinationClearData" failed with error code 0xC0202009.  There may be error messages posted before
    this with more information on why the AcquireConnection method ca...  The package execution fa...  The step failed.
    So I hope somebody can shed some hints or tips for me to overcome time problem of mine. Thanks for your help in advance. As I had scoured thoroughout MSDN forums & found none solution for my problem yet. 
    PS: In the SQL Integrated Services when I deployed the package I set the security of the packages to Rely on server... 
    Hope this will help.

    Hi Ironmaidenroxz,
    From the message “Executed as user: MSSQLServer\SYSTEM”, we can see that the SQL Server Agent job ran under the Local System account. However, a Local System account doesn’t have the network rights natively, therefore, the job failed to communicate with
    the remote IBMAS400 server.
    To address this issue, you need to create a proxy account for SQL Server Agent to run the job. When creating the credentials for the proxy account, you can use the Windows domain account under which you executed the package manually.
    References:
    How to: Create a Credential
    How to: Create a Proxy
    Regards,
    Mike Yin
    TechNet Community Support

Maybe you are looking for