shibboleth-sp-3.0.4.2-win64 install issue on Server 2016

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

shibboleth-sp-3.0.4.2-win64 install issue on Server 2016

Tom King

Dear All,

 

I’m trying to install shibboleth-sp-3.0.4.2-win64.msi on a clean and fully patched Windows Server 2016 system. I’ve downloaded the installer and verified the checksum, and am running it using administrator powershell from C:\Temp.

 

Msiexec returns the error “This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.”. The log produced by this process is copied below.

 

I have the same issue with shibboleth-sp-3.0.3.0-win64.msi so I suspect some issue with my environment, but I can’t think what that might be. My antivirus (Sophos Central) isn’t recording any activity. The system already had vc++ versions 2008 (x86,x64) and 2017 (x86) installed, and I installed 2015-2019 x64 myself before downloading shib.

 

If anyone has any ideas what the issue may be, I’d be very grateful.

 

Kind regards,

 

Tom

 

 

 

 

 

 

 

=== Verbose logging started: 10/02/2020  16:14:18  Build type: SHIP UNICODE 5.00.10011.00  Calling process: C:\Windows\system32\msiexec.exe ===

MSI (c) (5C:40) [16:14:18:343]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

 

MSI (c) (5C:40) [16:14:18:343]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

 

MSI (c) (5C:E4) [16:14:18:359]: Resetting cached policy values

MSI (c) (5C:E4) [16:14:18:359]: Machine policy value 'Debug' is 0

MSI (c) (5C:E4) [16:14:18:359]: ******* RunEngine:

           ******* Product: .\shibboleth-sp-3.0.4.2-win64.msi

           ******* Action:

           ******* CommandLine: **********

MSI (c) (5C:E4) [16:14:18:359]: Machine policy value 'DisableUserInstalls' is 0

MSI (c) (5C:E4) [16:14:18:374]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2

MSI (c) (5C:E4) [16:14:18:374]: Note: 1: 1324 2: . 3: 1

MSI (c) (5C:E4) [16:14:18:374]: MainEngineThread is returning 2

=== Verbose logging stopped: 10/02/2020  16:14:18 ===

 

 

 


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: shibboleth-sp-3.0.4.2-win64 install issue on Server 2016

Tom King

So the solution was to create a bat file with the contents “msiexec /i %1” and then drag the MSI onto it.

 

Tom

 

 

 

 

From: users <[hidden email]> on behalf of Tom King <[hidden email]>
Reply to: Shib Users <[hidden email]>
Date: Monday, 10 February 2020 at 16:22
To: "[hidden email]" <[hidden email]>
Subject: shibboleth-sp-3.0.4.2-win64 install issue on Server 2016

 

Dear All,

 

I’m trying to install shibboleth-sp-3.0.4.2-win64.msi on a clean and fully patched Windows Server 2016 system. I’ve downloaded the installer and verified the checksum, and am running it using administrator powershell from C:\Temp.

 

Msiexec returns the error “This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.”. The log produced by this process is copied below.

 

I have the same issue with shibboleth-sp-3.0.3.0-win64.msi so I suspect some issue with my environment, but I can’t think what that might be. My antivirus (Sophos Central) isn’t recording any activity. The system already had vc++ versions 2008 (x86,x64) and 2017 (x86) installed, and I installed 2015-2019 x64 myself before downloading shib.

 

If anyone has any ideas what the issue may be, I’d be very grateful.

 

Kind regards,

 

Tom

 

 

 

 

 

 

 

=== Verbose logging started: 10/02/2020  16:14:18  Build type: SHIP UNICODE 5.00.10011.00  Calling process: C:\Windows\system32\msiexec.exe ===

MSI (c) (5C:40) [16:14:18:343]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

 

MSI (c) (5C:40) [16:14:18:343]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

 

MSI (c) (5C:E4) [16:14:18:359]: Resetting cached policy values

MSI (c) (5C:E4) [16:14:18:359]: Machine policy value 'Debug' is 0

MSI (c) (5C:E4) [16:14:18:359]: ******* RunEngine:

           ******* Product: .\shibboleth-sp-3.0.4.2-win64.msi

           ******* Action:

           ******* CommandLine: **********

MSI (c) (5C:E4) [16:14:18:359]: Machine policy value 'DisableUserInstalls' is 0

MSI (c) (5C:E4) [16:14:18:374]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2

MSI (c) (5C:E4) [16:14:18:374]: Note: 1: 1324 2: . 3: 1

MSI (c) (5C:E4) [16:14:18:374]: MainEngineThread is returning 2

=== Verbose logging stopped: 10/02/2020  16:14:18 ===

 

 

 


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: shibboleth-sp-3.0.4.2-win64 install issue on Server 2016

Rod Widdowson
> Msiexec returns the error “This installation package could not be opened. Verify that the package exists and that you can access it,
> or contact the application vendor to verify that this is a valid Windows Installer package.”.

As you diagnosed this is environmental and nothing to do with the installer.  I'd advise you to check your Global security policy for anomalies, third party security products can also get in the way..  I'd also suggest checking that you are correctly elevated and ensure that the "this has been downloaded ADS" is stripped (its on the properties page).

In any case your go-to tool for situations like this is Procmon, downloaded it from the MS website.

/R


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to [hidden email]