Service 'Windows Installer (msiserver)' cannot be started inside of a container

I

ivansha

While working with Docker containers on Windows Server 2016 (WS2016) that is a part of corporate domain I ran into an issue that does not allow me to install any MSI packages inside of the container. In particular I'm trying to install vcredist_x86.exe package. I narrowed it down to MSIServer service that cannot run inside of the container for some reason. I use process mode to run containers on WS2016.

If I run the same container on Win10 in hyperv mode, I have no problem starting MSIServer service and installing MSI packages.

If I run the same container on WS2016 in Azure (not a part of corporate domain), I have no problem running MSIServer service inside of the container and can install vcredist package.

Here's the error I get on when I try to start MSIServer service inside of the container on corporate WS2016 machine:



PS C:\> Start-Service msiserver

Start-Service : Service 'Windows Installer (msiserver)' cannot be started due to the following error: Cannot start

service msiserver on computer '.'.

At line:1 char:1

+ Start-Service msiserver

+ ~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],

ServiceCommandException

+ FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand


I suspect corporate domain Group Policy may have something to do with it but so far couldn't find any info that would prove it. The error is not very informative.

Any suggestions how to further troubleshoot this issue?

Continue reading...
 
Back
Top Bottom