Azure-SSIS IR has failed to start due to custom setup failure

vari83 1 Reputation point

Hi All,

We are getting below error while starting SSIS IR. Can you please suggest

Error code: CustomSetupScriptFailure. Error message: Your Azure-SSIS IR has failed to start due to custom setup failure. Details: [{"Code":"CustomSetupScriptBlobContainerInaccessible","NodeNumber":8,"Message":"Cannot access your Azure blob container for custom setup."}]

We have provided the blob storage SAS URI with read and write access plus future expiry date.

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,409 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,468 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,449 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ZoeHui-MSFT 32,411 Reputation points

    Hi @vari83 ,


    This error means that SSIS IR can't access your Azure blob container for custom setup. Make sure the SAS URI of the container is reachable and has not expired.

    Stop the IR if it's running, reconfigure the IR with new custom setup container SAS URI, and then restart the IR.

    Custom setup provides an interface to add your own setup steps during the provisioning or reconfiguration of your SSIS IR. For more information, see Customize setup for the Azure-SSIS Integration Runtime.

    Make sure your container contains only the necessary custom setup files; all the files in the container will be downloaded onto the SSIS IR worker node. We recommend that you test the custom setup script on a local machine to fix any script execution issues before you run the script in SSIS IR.

    The custom setup script container will be checked while IR is running, because SSIS IR is regularly updated. This updating requires access to the container to download the custom setup script and install it again. The process also checks whether the container is accessible and whether the main.cmd file exists.

    More details you may refer to ssis-integration-runtime-management-troubleshoot



    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.