ISICE07

InstallShield 2016

Project • This information applies to the following project types:

Messages

Message 1 (Error)

Component.ComponentId for Component [1] is null. All components must have a valid ComponentId for proper installation and uninstallation. If this is left null, justification must be documented.

[1] is the name of a component in your project that does not have a GUID specified in the Component Code setting in the Components view.

Message 2 (Error)

Component [1] contains COM data, but it has more than 1 file. Each COM component should contain only 1 COM file.

[1] is the name of a component in your project that contains more than one COM server.

Message 3 (Error)

Component [1] has more than one file as the target of a Desktop or Start Menu shortcut.

[1] is the name of a component in your project that has more than one file specified as the target of a shortcut.

Message 4 (Error)

Component [1] is associated with multiple features and is referenced in the following tables: [2]. These references require the component to be associated with exactly 1 feature.

[1] is the name of a component in your project that is associated with more than one feature and that has references in any of the following tables: Class, Extension, MsiAssembly, PublishComponent, TypeLib. [2] is a comma-delimited list of tables that contain references to the component.

Description

ISICE07 verifies that the components in your installation adhere to component rules, which help to ensure that the installation or uninstallation of one product does not harm any other product on a target system. These rules also help to ensure that Windows Installer correctly removes all resources that are connected with a product that is being uninstalled.

Corrective Action

To resolve error 1, open the Components view, select the component that is mentioned in the error message, and click the Component Code setting. In the help pane that is displayed in the lower-right pane, click Generate GUID. If you have a valid reason for leaving the Component Code setting blank, you can document it in the application that you submit for the Windows logo program.

To resolve error 2, move any COM servers to separate components so that each COM server is the key path of its component.

To resolve error 3, use the Shortcuts view to delete all but one of the shortcuts that are associated with the component mentioned in the error message.

To resolve error 4, use the Setup Design view or the Features view to remove the component from all but one feature.

See Also

Component Settings

Setting Key Paths for Components

Creating Shortcuts and Program Folders

Requirements for the Windows Logo Program

ISICEs

Open topic with navigation