Skip to main content

Has anyone had any success in following the posted guides for getting the PowerBI Infrastructure setup for Customer Azure Cloud? I’m trying to follow the guide https://docs.ifs.com/techdocs/23r1/050_reporting/450_self_hosted_bi_int/010_infra_setup_azure/ , but no matter how step-by-step and picture-for-picture I go, I am greeted with the inability to start up my Azure Data Factory’s Integration Runtime with an error code CustomSetupScriptBlobContainerInaccessible.

 

Full error shown after the 1 hour timeout of the IR Startup; 

Error 1:
  Last operation 'Start' get the status 'Failed'.
  Error code: CustomSetupScriptFailure
  Error message: Your Azure-SSIS IR has failed to start due to custom setup failure. Details: D{"Code":"CustomSetupScriptBlobContainerInaccessible","NodeNumber":1,"Message":"Cannot access your Azure blob container for custom setup."}].
  Activity ID: <GUID>

For more details, please refer to https://go.microsoft.com/fwlink/?linkid=2099434.

 

I’ve gone through this setup multiple times following the guide, and have used multiple SAS tokens and URLs in the blob access string (Which succeeds it’s connectivity attempts every time) with multi-year long lifespans, but the issue persists.

 

Looking for any help or guidance on any ‘undocumented required steps’! 

I have successfully resolved the issue by modifying the SAS URL. Kindly follow the steps outlined below for your reference:

1. Navigate to the Storage account and access the shared access signature under the "Security + Network" section.

2. Generate the SAS URI from the aforementioned location (Allowed resource types - Service,Container,Object).

3. Subsequently, obtain the Blob Service SAS URL and append your container name before "?sv," as illustrated below:

https://testbistorageacc.blob.core.windows.net/containername?sv=2022-11-02&ss=bfqt&srt=sco&sp=rwdlacupiytfx&se=2025-04-01T03:25:18Z&st=2024-01-03T20:25:18Z&spr=https&sig=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%3D

4. Additionally, please ensure the accuracy of the modified SAS URL by verifying it through the Microsoft Azure Storage Explorer.

I have successfully resolved the issue by modifying the SAS URL. Kindly follow the steps outlined below for your reference:

1. Navigate to the Storage account and access the shared access signature under the "Security + Network" section.

2. Generate the SAS URI from the aforementioned location (Allowed resource types - Service,Container,Object).

3. Subsequently, obtain the Blob Service SAS URL and append your container name before "?sv," as illustrated below:

https://testbistorageacc.blob.core.windows.net/containername?sv=2022-11-02&ss=bfqt&srt=sco&sp=rwdlacupiytfx&se=2025-04-01T03:25:18Z&st=2024-01-03T20:25:18Z&spr=https&sig=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%3D

4. Additionally, please ensure the accuracy of the modified SAS URL by verifying it through the Microsoft Azure Storage Explorer.

This solved my problem, the SAS URL generated from container didnt work like the documention suggested. Thanks! 

Great find! This solved my problem perfectly.

Reply


Terms & ConditionsCookie settings