Article ID: 303878 - Last Review: July 16, 2007 - Revision: 2.2 Unattended Visio 2000 installation does not succeedThis article was previously published under Q303878 On This PageSYMPTOMS
When you use the Microsoft Visio 2000 installer package (Vis2000.msi) from the Select CDs, you may not be able to perform an unattended installation of Microsoft Visio 2000 SR-1a, Professional edition. The installation does not succeed, and you may receive an error message that is similar to the following:
Error 1406: Could not write value Installed to key
CAUSE
This issue occurs because of registry limitations in the Windows Installer in Microsoft Windows 95. The total size of a registry key and all its values is limited to 64 kilobytes (KB) in Windows 95. This may limit the maximum total number of features and components in a product.
RESOLUTION
To work around this issue and finish the installation process, click Ignore each time that you receive the error message. NOTE: If you use the /qb- switch or the /qb+ switch, you receive the error message, and you can click Ignore on the error message. If you click Ignore, the installation may succeed. However, if you use the /qn switch, you do not receive an error message. You cannot click Ignore in that case; therefore, the installation does not succeed. To resolve this issue, you can create a transform that will be applied to the Vis2000.msi installer database. By applying a transform, you can continue to use the Microsoft Visio 2000 installer package (Vis2000.msi) from the Select CD without causing potential support problems for future patches and service releases. In the transform-modified database, you can create a Custom Action of type 51 to set the DPID property to text formatted "No Value", which is acceptable to the Windows 95 registry. The Windows Installer can then call the Custom Action conditionally from the InstallExecuteSequence table. You have to make sure that the Custom Action is the last action to modify the DPID property, and so you have to create the new install sequence with a sequence number that immediately precedes the one for the installation action. You have to do this because the Microsoft Visio 2000 installer package from the Select CD had to sequence the standard action before any changes were made to the computer; therefore, all properties must have been set before then. This procedure sets the condition column so that the Custom Action is called only if the operating system is earlier than Microsoft Windows 98. By doing this, the same transform can be used throughout the organization without an impact on any computer that uses a later version of Windows. For the following resolution, you have to install the Microsoft Windows Installer Software Development Kit (SDK). The Windows Installer SDK comes with a utility named Orca that you can use to create a "destination .msi file". It also comes with a utility named MSITran.exe that you can use to generate the transform. You can download a copy of the Microsoft Windows Installer SDK at no charge. To do this, visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=e96f8abc-62c3-4cc3-93ad-bfc98e3ae4a3
(http://www.microsoft.com/downloads/details.aspx?FamilyID=e96f8abc-62c3-4cc3-93ad-bfc98e3ae4a3)
To create the transform to resolve this issue, follow these steps:
Deployment ExampleThe following is a deployment example that uses the transform that was created in steps 1 through 12. This example applies to the deployment of Visio 2000 to workstations that already have Microsoft Office 2000 SR-1 and Windows Installer 1.1 installed, and to systems where Mssup.exe has already been applied. It also assumes that the Install folder of the Select CD for Visio Professional SR-1a has already been copied onto a network share \\ComputerName\ShareName.
MORE INFORMATION
For more information about the MSI databases, see the Help file named Msi.chm, which is installed by the Windows Installer SDK. See the following topics in the Msi.chm Help file:
In the MSITool.hlp Help file, see the "Transform" Help topic for a syntax and command-line options available to the utility. | Article Translations
|

Back to the top
