When you try to use an .msi file to install an add-in for Microsoft Office Visio 2007 on a Windows Vista-based computer, the add-in is not installed and the following error message is logged in the installation log file:
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 VisSolPublish_BumpVisioChangeId script error -2147024891, WshShell.RegWrite: Invalid root in registry key "HKLM\Software\Microsoft\Office\Visio\ConfigChangeID". Line 4, Column 1.
Also, when you try to install a custom Microsoft Office InfoPath 2007 template, the following error message is logged in the installation log file:
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.
To work around this issue, use one of the following methods.
Method 1: Disable UAC and run the .msi file
To resolve this issue, disable User Account Control (UAC), and then run the .msi file. To do this, follow these steps:
- Disable User Account Control (UAC). To do this, follow these steps:
- Click Start
Collapse this imageExpand this image
Or, if you are connected to a network domain, click User Accounts, and then click User Accounts. - Click Turn User Account Control on or off.
Collapse this imageExpand this image
- Click to clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.
- Restart the computer.
- Run the .msi file to install the add-in.
- Enable UAC. To do this, repeat step 1, except that in step 1c, click to select the Use User Account Control (UAC) to help protect your computer check box.
Collapse this imageExpand this image
Method 2: Modify the .msi file
To resolve this issue, modify the .msi file. To do that, follow these steps:
- Open the .msi file in an MSI editor. For example, use the Orca MSI Editor that is provided in the Microsoft Windows Software Development Kit (SDK).
For more information about the Windows SDK, go to the Windows SDK Components for Windows Installer Developers
(http://msdn2.microsoft.com/en-us/library/aa370834.aspx)
Microsoft Developers Network (MSDN) website. - Open the .msi file in the MSI editor.
- Locate the Custom Action table.
- Locate the VisSolPublish_BumpVisioChangeId custom action, and then change the type to 3622.
- Save the .msi file, and then exit the editor.
Collapse this imageExpand this image
This change causes the custom action to be a deferred commit custom action of the "noimpersonate" type. This change lets the .msi file run in the administrator permissions level. When you make this change, the script runs later in the "installation" sequence and earlier in the "remove" sequence.
Article ID: 929991 - Last Review: May 24, 2012 - Revision: 5.0
APPLIES TO
- Microsoft Office Visio Professional 2007
- Microsoft Office Visio Standard 2007
- Microsoft Office InfoPath 2007
| kbdeployment kbsetup kberrmsg kbtshoot kbexpertiseinter kbprb KB929991 |
Back to the top
