Summary

This article describes how to run an InstallShield automation script (VBScript or PowerShell) inside a Windows Server Core Docker image.

NOTE: You can 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. The files listed above 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 five 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.

NOTE: This Knowledge Base article also applies to Windows Server 2022.

Reference

• For information on creating a PowerShell automation script, see Use PowerShell to Create a Project and Add a PowerShell Custom Action Using the InstallShield Automation Interface.
• For information on creating a Python automation script, see How to Use Python with the InstallShield Automation Interface.