Running an Automation Script via the InstallShield SAB on a Windows Server Core Docker Image
Running an Automation Script via the InstallShield SAB on a Windows Server Core Docker Image
Running an Automation Script via the InstallShield SAB on Windows Server Core Docker Image
Summary:
How to run an InstallShield automation script (VBScript or PowerShell) inside a Windows Server Core Docker image.
Build a Docker image that has the InstallShield Standalone Build installed by following the steps in the following Knowledge Base article: InstallShield Standalone Build with Docker
Synopsis
This information applies to the following InstallShield project types:
Basic MSI
InstallScript MSI
Cause
When we run an automation script on a Windows Server Core Docker image, it fails with the error "The specified module could not be found." or the project will not build.
Solution
The issue of the build failure on a Windows Server Core Docker image is due to the following missing Microsoft Windows libraries: oledlg.dll, msvbvm60.dll, glu32.dll, opengl32.dll, srpapi.dll. Windows Server Core provides you with a minimal installation of Windows Server with minimal features and supports only certain server roles.
Oledlg.dll, msvbvm60.dll, glu32.dll, opengl32.dll, srpapi.dll are not included with the Windows Server Core installation. Hence, the Automation Interface is failing to build the project for a Basic MSI project or a InstallScript MSI project.
Since all of these DLLs are from Microsoft and we do not have the redistribution rights, we need to copy all of these 5 DLLs from a Windows Server 2019 GUI > SysWow64 folder to the Windows Server 2019 Core Docker image > SysWow64 folder, and then execute the automation script. The automation script will then execute without any errors.
