Troubleshooting Error 1720 &1722 in Studio for Winforms Installation

At times, users get Error 1720/1722 during installation, or un-installation, of Studio For Winforms. The error is, more or less, the same; however, the causes may vary. This blog provides possible solutions to this.

About Error 1720/1722

Error 1720/1722 is one of the most common errors. Following message is displayed during installation, or un-installation of any installation package: "There is a problem with this Windows Installer Package. A script required for the install to complete could not be run. Contact your support personnel or package vendor." You may also refer this to check for more, and get some meaningful information, regarding the cause(s) of this error.

Troubleshooting Scenarios

Error during Installation Case 1 There might be issues with setup trying to detect Visual Studio. As per the version of Visual Studio installed on the machine, the setup looks for the install path to VS in registry, here, to find InstallDir key : For 32 bit : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1 For 64 bit : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\7.1 To fix this, edit the path in InstallDir, which matches the path to the latest version of Visual Studio. For example: For VS2008, change it to: For 32 bit : C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE For 64 bit : C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE Reboot the machine, and run the installer. Case 2 If the issue persists, try performing a silent install using command prompt. However, it is recommended to deactivate all your licenses installed, regarding C1, from the machine, before you initiate the install. Steps to deactivate licenses and perform Silent Install are as follows: 1. Run the command prompt with administrative rights. 2. Type the following command to change the directory to the path where C1LicenseActivation is installed. The utility is generally installed in Program Files\Common Files\ComponentOne Shared folder : cd C:\Program Files\Common Files\ComponentOne Shared 3. Type the following command and enter your name, Company Name and serial key to be deactivated : C1LicenseActivation.exe /d 4. Type the following command to change the directory to the path where the installer location cd 5. Type the following command to silent install the installer : msiexec /x <installername.msi> Reboot the machine, and run the installer. Error during Upgrade Installation The setup may be unable to install/remove product dlls to/from the GAC(Global Assembly Cache). Here, we need to manually remove C1 dlls from GAC before initiating the install again. Once done, follow the next section to remove the old setup, or any leftovers from the previous install. Alternatively, use the Windows installer cleanup utility to remove the installed setup. If you’re curious about Msizap, click here. Error during Uninstallation If the error is observed while removal of components, try these steps: 1. Clear the TEMP folder. (Type %temp% in run prompt). 2. Disable UAC. 3. Open Control Panel | Programs and Features | Add or Remove Programs | Uninstall ComponentOne Studio for WinForms 4. Open the following folder and remove the *.tbd files to remove toolbox entries : C:\Users\\AppData\Local\Microsoft\VisualStudio\10.0\ 5. Delete My Documents\ComponentOne Samples 6. Delete the following folders manually : For 64 bit : C:\Program Files (x86)\ComponentOne For 32 bit : C:\Program Files\ComponentOne Studio Note : If you are using other C1 products, like Doc-To-Help or any other studio, then ensure that you remove only the Winforms folder. If none of the above helps, create an install log and email it to our support team. Here’re the steps to create an install log: 1. Run the command prompt with administrative rights. 2. Type the following command to run the installer and create install log : For msi: msiexec /i InstallerName /L c:\logfile.txt For exe: "installerpath\name" /V"/L c:\logfile.txt" Email the uninstall log to


GrapeCity Developer Tools
comments powered by Disqus