Connect plugin MSI installation error 1720

Description

During an installation of the Connect browser plugin for Windows, an error message is displayed indicating that the installation has failed. The error is due to the CloseConnect custom action VBS script failing to execute correctly. The most frequent cause of this issue is that the WMI repository has been corrupted or the necessary .DLL and .EXE files needed for WMI are unregistered.

To confirm that the error is due to CloseConnect CA failing to execute correctly, you can re-run the installation with logging enabled. Use the following syntax from the command line to re-run the installation where <msi file> is the name of the Connect Installer you downloaded:

msiexec /i <msi file> /l*v install.log
 
Then search for the string "Error 1720"  The results should look like this:
Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.  Custom action CloseConnect script error -2146828218, Microsoft VBScript runtime error: Permission denied: 'GetObject' Line 2, Column 1,  
MSI (s) (2C:30) [13:23:34:108]: Product: Aspera Connect -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.  Custom action CloseConnect script error -2146828218, Microsoft VBScript runtime error: Permission denied: 'GetObject' Line 2, Column 1,  

Action ended 13:23:34: CloseConnect. Return value 3.

 

This error is due to WMI failing to initialize (80041014). 80041014 occurs when you execute a VBScript connecting to WMI (Windows Management Instrumentation). It means that COM cannot locate a provider referenced in the schema. As a wild guess, crucial DLLs may have been accidentally de-registered from your machine. This means that COM cannot locate a provider referenced in the schema.

In practical terms the files used by WMI have been deleted or become corrupt.

Environment

  • Product: Connect browser plugin
  • Operating System: Windows

 

Solution

In order to fix the problem, first attempt to re-register all the .DLL and .EXE files needed for WMI. The steps to do this are outlined below but you can also download the batch file (1720fix.bat) attached to this KB article and run that on your computer to execute the steps automatically.
 
Steps to re-register .DLL and .EXE components for WMI:

1. From the CMD prompt, navigate to the %windir%\System32\Wbem directory:

 cd %windir%\System32\Wbem

 

2. Type the following at the command prompt and then press ENTER:

for %i in (*.dll) do RegSvr32 -s %i

 

3. After the .DLLs have been re-registered you will then need to re-register any .EXE files found in the Wbem folder, except for Mofcomp.exe and Wmic.exe. For example, to re-register the executable file Scrcons.exe type the following from the command prompt:

regsvr32 -s scrcons.exe

 

4. Attempt to re-run the installation.

 Attached to this article is a batch file which can be download to run these commands for you. Simply run the batch file and then retry the installation normally.

Attachments

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk