[Troubleshooting-BHOLD] There is a problem with this Windows Installer package.

[Troubleshooting-BHOLD] There is a problem with this Windows Installer package.

Rate This
  • Comments 1

Problem Statement

Attempting to install the BHOLD FIM Integration Module on a FIM Server with BHOLD Core being installed on a separate machine may fail with the following error dialog.

Error

There is a problem with this Windows Installer package.  A program run as part of the setup did not finish as expected.  Contact your support personnel or package vendor.

 

 

Troubleshooting

  • Reviewed the Application Event Log and found the following

 

 Cause

The message implies that the extended protection setting for IIS doesn't match that of what install expects. This setting is exposed in Authentication->Windows Authentication-Advanced Settings of the that node is selected on navigation bar on left:

 

 

Resolution

In this particular issue, we found the default IIS node was set to 'Accept', which translates to 'WhenSupported' value. We enabled windows authentication, which had been disabled, then set this value to 'Off' in advanced settings, then disabled windows authentication and ran IISRESET and the next attempt at the install succeeded.

 

A very important hint came from the customer's applicationHost.config file: 

 

 *NOTE: The highlighted section shows a value other than 'Off' configured. It seems odd that it didn't just look at the FIM site, which is typically 'SharePoint – 80'. This site didn't have the above entry. This entry came from the root node. So apparently the install looks throughout the entire file.

 

            <applicationDependencies>

                <application name="Active Server Pages" groupId="ASP" />

            </applicationDependencies>

            <authentication>

                <anonymousAuthentication enabled="true" userName="IUSR" />

                <basicAuthentication enabled="false" />

                <clientCertificateMappingAuthentication enabled="false" />

                <digestAuthentication enabled="false" />

                <iisClientCertificateMappingAuthentication enabled="false">

                </iisClientCertificateMappingAuthentication>

                <windowsAuthentication enabled="false" useKernelMode="true">

                    <providers>

                        <add value="Negotiate" />

                        <add value="NTLM" />

                    </providers>

<extendedProtection tokenChecking="Allow" />

                </windowsAuthentication>

            </authentication>

            <authorization>

                <add accessType="Allow" users="*" />

            </authorization>

 

Leave a Comment
  • Please add 1 and 8 and type the answer here:
  • Post
  • This error can also occur if the installer is not run as a local administrator.  In this case, you will find an 11720 (msiInstaller) event in the Application Event Log with a reference to a vbscript error - "Permission denied Line 70, Column 1,".

    You might want to simply confirm that you are running the MSI as an administrator before you implement the resolution suggested on this page.

Page 1 of 1 (1 items)