locked
Package execution on IS Server failed. Execution ID: 333122 RRS feed

  • Question

  • Hi,
    When I run JOB, the following error occurs:

    Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted
    09/03/2019 17:25:04,JOB,Error,,AP1,JOB,,,The job failed.  The Job was invoked by User user.  The last step to run was step 1 (OUT).,00:00:06,0,0,,,,0
    09/03/2019 17:25:04,JOB_,Error,1,AP1,JOB,OUT,,Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility  Version 13.0.5233.0 for 64-bit  Copyright (C) 2016 Microsoft. All rights reserved.    Started:  17:25:05  Package execution on IS Server failed. Execution ID: 333209<c/> Execution Status:4.  To view the details for the execution<c/> right-click on the Integration Services Catalog<c/> and open the [All Executions] report  Started:  17:25:05  Finished: 17:25:08  Elapsed:  3.593 seconds.  The package execution failed.  The step failed.,00:00:06,0,0,,,,0

    thanks

    Tuesday, September 3, 2019 4:35 PM

All replies

  • Hi MVilariño,

    In case is SQL Server Agent doesn't provide any details, please check SSIS logs for the details.

    Tuesday, September 3, 2019 4:42 PM
  • Hi MVilariño,

    You could check the job history to view the detailed message for failure, then share the error message with us so that we are able to analyze this issue.

    1. Login sql server instance
    2. Navigate to Integration Service Catalogs
    3. Right Click on your SSISDB catalog and select All Reports -> Standard reports -> All Executions
    4. For your folder, click on All Messages for failed task
    5. Here you will see your error

    But anyway, you could try to check two following options:

    • Switch the run mode to 32/64 bit in the job step properties
    • Try to use proxy account which has sufficient permission to execute the package

    Please refer to SQL Credentials and Proxy for Agent Job.

    Check if this helps.

    Regards,

    Zoe


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Proposed as answer by Zoe Gu Wednesday, September 4, 2019 9:51 AM
    Wednesday, September 4, 2019 2:25 AM
  • Hi,

    This error occurred because I did not have read and write permission on the folder.

    Which user of SQL Server agent?

    Thanks for your help

    Wednesday, September 4, 2019 8:05 AM
  • Hi MVilariño,

    Please remember to click "Mark as Answer" the responses that resolved your issue. This can be beneficial to other community members reading this thread.

    Regards,
    Zoe 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Wednesday, September 4, 2019 9:47 AM