Installing IBMi Access Driver on Azure Data Factory Integration Runtime

Question

Hello,

I've been trying to install the Windows version of the IBM i Access Driver on a Data Factory Integration Runtime through adding a script (main.cmd) and the desired installer in a Blob Container

This script seems to work perfectly locally but when I try to run it on IR - it says the custom script can't be executed

I've tested and it installs all the redistributables (first four lines of the code) perfectly - and stops only at the "setup.exe"

Script

"%~dp0Image64a\ISSetupPrerequisites{827DEC3D-1589-41F9-9188-C6BE5CADF691}\vcredist_x86_2013.exe" /silent /norestart

"%~dp0Image64a\ISSetupPrerequisites{5219AC36-EB02-4668-B6E4-711E10D95833}\vcredist_x64_2013.exe" /silent /norestart

"%~dp0Image64a\ISSetupPrerequisites{2D5DF45C-F87F-49CA-9104-467740CC3FB8}\vcredist_x86_2015.exe" /silent /norestart

"%~dp0Image64a\ISSetupPrerequisites{25E2F1F0-09A7-4C6A-ADC7-CA620D43574E}\vcredist_x64_2015.exe" /silent /norestart

"%~dp0Image64a\setup.exe" /s /v"/quiet ACCEPTEULA=1 /norestart"

IBMi Access Driver - ACS Windows App Pkg English (64bit)

https://www.ibm.com/resources/mrs/assets/DownloadList?source=swg-ia&lang=en_US#lang=en_US

Answer 1

Hi @Alexandru Moise
Thanks for the question and using MS Q&A platform.
It sounds like you are having issues running a custom script to install the IBM i Access Driver on a Data Factory Integration Runtime.

One possible reason for the error message you are seeing is that the script is not being executed with the correct permissions. Make sure that the user account running the script has the necessary permissions to execute the script and install software on the Integration Runtime.

Another possible reason is that the script is not being executed from the correct working directory. Make sure that the script is being executed from the correct directory where the installer and other necessary files are located.

You can also try modifying the script to include additional logging or error handling to help diagnose the issue. For example, you can add commands to log the output of each command to a file or to the console.

If none of these solutions work, consider contacting Azure support for further assistance. They may be able to provide additional guidance on how to troubleshoot the issue.

I hope this helps! Let me know if you have any further questions.