Consistency Check Scenarios

During the Custom, Semi-automatic, or Silent installation, the Installer performs the consistency check. Depending on the situation, the Installer either aborts the installation or proceeds with the installation and generates a installation log. The installation log stores messages (informational, warning, error, and fatal) about events that occur during the installation process.

NOTE:
You may see a few messages in the installation log. However, unless a fatal (irrecoverable) error occurs, the installation program completes the installation successfully.
The installation user interface indicates the success or failure of each installation attempt, and the installation log file includes an entry for each installation process.

To help you determine the cause of a failure, it is recommended to view the log file located at the path:
[system drive]:\ProgramData\[company name]\GMS\InstallerFramework\GMS_Installer_Log.

For a Semi-automatic installation, view the installation log file that has the extension_SEMI.

For a Silent Installation, view the installation log file that has the extension _SILENT.

Consistency Check Scenarios

The following table provides the scenarios and the corresponding behavior by the different Installation Modes

Scenarios	Behavior during Custom Installation	Behavior during Silent Installation	Behavior during Semi-automatic Installation	Do the following...
GMSConfig.xml file missing. Platform EULA missing, Mandatory prerequisite missing in the Distribution Media.	The Desigo CC Installer does not allow you to go beyond the Welcome to the Desigo CC Install Wizard dialog box and the Next button is disabled.	Aborts the Silent installation and notifies you with the taskbar icon tooltip in the notification area.	Same as Custom installation.	Make sure that the valid file is present.
Prerequisites missing or folder structure corrupted in the Distribution Media.	Does not work if a prerequisite is mandatory. For a non-mandatory prerequisite, the installation will finish; however, it will fail to install the failed non-mandatory prerequisite.	Aborts the Silent installation for a mandatory prerequisite and notifies with the taskbar icon tooltip in the notification area. For non-mandatory prerequisite, the installation will finish; however, it will fail to install the failed non-mandatory prerequisite and the warning will display in the _SILENT installation log file.	Same as Custom installation.	Make sure the valid file is present and the folder structure is intact. For details, see the Installer Log file. Install the prerequisite.
Syntax error/orphan components in the GMSConfig.xml file.	Does not work	Does not work.	Inconsistency error displays on the Welcome dialog box and the Next button is disabled.	Make sure necessary content and components specified in the GMSConfig.xml file are available.
There is an existing installed Desigo CC platform that is an older version than the current one on the computer.	Installer will perform an upgrade for Desigo CC Version 4.0 and later.	Same as custom.	Same as custom.
No Brand folder exists in the Distribution Media.	Does not work.	Does not work.	Same as Custom installation.
The configured Language Pack is not present on the Distribution Media.	NA	Does not work	The Language Pack dialog box displays the available language packs in ..\Languages folder. A warning displays in the Instruction File Selection dialog box. A log entry is added in the Installer Log file.	Ensure that the Language Pack is available in the ..\Languages folder in the Distribution Media.
The configured installation language does not exist in the Distribution Media.	NA	Aborts the Silent installation and notifies with the taskbar icon tooltip in the notification area.	The Welcome dialog box displays the available installation languages in the Languages folder. A warning displays in the Installation Selection dialog box. A log entry is added in the Installer Log file.	Ensure that the installation language is available in the ..\Languages folder in the Distribution Media.
The configured EM is not present in the Distribution Media.	NA	Aborts the Silent installation and notifies with the taskbar icon tooltip in the notification area.	The Feature Selection dialog box displays the available EMs in the EM folder in the Distribution Media. A warning is displays in the Installation Selection dialog box. A log entry is added in the Installer Log file.	Ensure that the EM and its parent EM are available in the Distribution Media. A mandatory EM and its parent EM (mandatory/non-mandatory), available in the distribution media, is always installed, even if they are not configured in the GMS Platform file.
There are missing EMs during major upgrade.	Consistency warning appears on the Welcome dialog Box. Add Missing EMs using Add EM button on the Feature Selection dialog box. The Next button on the Setup type dialog box is disabled till all the missing extensions are added.	If you have not added all the missing extensions using the <ExternalEMsPath> attribute of the GMS Platform file, the Silent installation aborts and notifies with the taskbar icon tooltip in the notification area. A log entry is added in the Silent Installer Log file.	If you have not added all the missing extensions using the <ExternalEMsPath> attribute of the GMS Platform file, then the Feature Selection dialog box displays with Next button disabled. You can add the missing extensions using Add EM button in order to proceed with upgrade.	Ensure that the EM and its parent EM are available in the Distribution Media/ external location and for Silent and Semi-automatic, they are configured in the GMS Platform file.
The configured EULA for Desigo CC or an EM does not exist in the Distribution Media.	The Desigo CC Installer does not allow you to go beyond the Welcome to the Desigo CC Install Wizard dialog box. Error about the missing EULA file is reported.	Aborts the Silent installation and notifies with the taskbar icon tooltip in the notification area. Consistency check is not performed for README EULA files.	Same as Custom installation. The Installation Selection dialog box is not displayed. Consistency check is not performed for README EULA files.	Check the individual EULA file along with the setup of the software component in question and Accept the EULA in the GMS Platform.xml instructions file.
Any invalid parameters in the GMS Platform.xml file, including any inconsistency with the configuration parameters mentioned in the GMS Platform.xml file, as well as those present in the Distribution Media. For example, a negative integer (-60) for the RestartDuration.	NA	Aborts the Silent installation and notifies with the taskbar icon tooltip in the notification area.	NA	Ensure that the GMS Platform.xml file is valid. For all warnings related to the Semi-automatic installation, a log entry is added in the Installer Log for SILENT.
Invalid GMS Platform.xml file. For example, missing closing tag or erroneous tags.			The GMS Platform.xml file is not listed in the Installation Selection dialog box. A warning displays.
Mandatory tag <`SetupType`> is missing. Invalid Setup Type; for example, ABC.			The GMS Platform.xml file is not listed in the Installation Selection dialog box. A warning displays.
Multiple entries for tags, where only one entry is permitted.			The GMS Platform.xml file is not listed in the Installation Selection dialog box. A warning displays.
Invalid Installation language name (for example, xx-YY, instead of en-US) or specified installation language is not found in the Distribution Media.			The Warning tab displays the message. However, the xml file is available for selection. When you select the xml file, and click Next, the Welcome dialog box displays the default en-US language. It also lists the additional languages available in the …c\Languages folder. You can add more installation languages using Add Additional Language.
Invalid EM name, or valid EM name, but not available in the Distribution Media			The Warning tab displays the message. However, the xml file is available for selection. When you select the xml file and click Next, the Feature Selection dialog box displays the Ems that are available in the Distribution Media and those that are selected by default.
Invalid Language Pack name (for example, xx-YY, instead of en-US) or the specified Language Pack does not exist in the Distribution Media.			The Warning tab displays the message. However, the XML file is available for selection. When you select the xml file and click Next, the Language Packs dialog box displays with all the available Language Packs in the …\Languages folder, selected by default. Additionally you can add more languages, using the Add Language Pack.
Platform EULAs, config file, not available or are not accepted.			The Next button is disabled.
Installation drive does not exist.	NA	Default installation path [Installation Drive]:\[Installation Folder] is used in case of Fresh Installation. For upgrade, the installation path used during the previous installation is used and a warning displays in the _SILENT installation log file.	Log is added, and Installation Folder dialog box displays with the default installation path for fresh installation. For upgrade, the installation path used during the previous installation is used and a warning displays in the SemiConsistencyLog.txt installation log file, which displays when you click View Log.
Insufficient disk space	Installation will not proceed to the Installation Folder dialog box.	Installation will abort.	The Installation Folder dialog box displays a message about insufficient disk space. The Next button is disabled. You can change the drive.	You must free the required disk space. (See Tips to Free Up Disk Space in Verify the Installation Environment)
If Name or Command tag missing/empty.	A message informing that the post installation step is inconsistent displays in the Welcome to the Desigo CC Install Wizard dialog box.	A message is included in the Silent installer log file.	A message informing that the post installation step is inconsistent displays in the SemiConsistencyLog.txt installation log file, which displays when you click View Log on the Installation Selection dialog box.	Verify that the Name and Command tag in the EM/GMSPostInstallationConfig xml file are present and have valid values.
EM/GMSPostInstallationConfig xml file is invalid.	A message informing that the inconsistencies presnt in the EM/GMSPostInstallationConfig xml file displays in the Welcome to the Desigo CC Install Wizard dialog box.	A message is included in the Silent installer log file.	A message informing that the inconsistencies presnt in the EM/GMSPostInstallationConfig xml file displays in the SemiConsistencyLog.txt installation log file, which displays when you click View Log on the Installation Selection dialog box.	Verify that the EM/GMSPostInstallationConfig xml file is consistent.
Precondition = Fresh_Machine is not true.	A message informing that the preconditions regarding Fresh_Machine is not satisfied displays in the Welcome to the Desigo CC Install Wizard dialog box.	A message informing that the preconditions regarding fresh machine is not satisfied displays is included in the Silent Installer log file.	A message informing that the preconditions regarding fresh machine is not satisfied displays in the SemiConsistencyLog.txt installation log file, which displays when you click View Log on the Installation Selection dialog box.	Verify that this machine is a fresh machine and the SQL Server is also not installed.
If Name or Execute tag is missing or invalid for the PostInstallation section in the GMS Platform.xml file.	NA	A message is included in the Silent Installer log file.	A message informing that invalid/incomplete information is present in the GMS Platform.xml file displays in the SemiConsistencyLog.txt installation log file, which displays when you click View Log on the Installation Selection dialog box.	Verify that the Name or Execute tag are not missing and are valid.
If any post-installation step with Execute = Always is configured in instruction file and in GMS Platform.xml Execute = False.	NA	The entry Execute = False will not be considered valid and warning message will be logged in the Silent installer log file and that step is executed.	The entry Execute = False will not be considered valid and warning message will be displayed in the SemiConsistencyLog.txt installation log file, which displays when you click View Log on the Installation Selection dialog box. However, the step will be executed.	Verify that the steps that are configured as Execute = Always in the GMS Platform .xm file are either configured as Execute = True or the not configured at all.
When installing a Quality Update using Patch Installer, the QualityUpdatesConfig.xml file is not present in the QualityUpdates folder.	The complete QualityUpdates folder is excluded from installation.	The complete QualityUpdates folder is excluded from installation.	The complete QualityUpdates folder is excluded from installation.	Ensure that the QualityUpdatesConfig.xml file is present in the QualityUpdates folder before proceeding with the installation procedure.
When installing a hotfix using Patch Installer, the UpdateLabel attribute for a patch is not present in the [EMName]PatchConfig.xml or GMSPatchConfig.xml file.	The compete patch will be excluded from installation. For example, if the AdvancedReportingPatchConfig.xml file does not contain the UpdateLabel attribute, then the complete patch for the Advanced Reporting extension will not be installed. The relevant warning message will be shown in the consistency window of the Installation Language Selection dialog box.	The compete patch will be excluded from installation. For example, if the AdvancedReportingPatchConfig.xml file does not contain the UpdateLabel attribute, then the complete patch for the Advanced Reporting extension will not be installed. The relevant warning message is included in the _SILENT installation log file.	The compete patch will be excluded from installation. For example, if the AdvancedReportingPatchConfig.xml file does not contain the UpdateLabel attribute, then the complete patch for the Advanced Reporting extension will not be installed. The relevant warning message displays in the SemiConsistencyLog.txt installation log file, which displays when you click View Log on the Installation Selection dialog box.	Ensure that the UpdateLabel attribute is present in the PatchConfig.xml file for the patch that is to be installed.
The version of the patches does not match with the extension or Platform to be installed or upgraded	A warning message appears on the Installation Language Selection dialog box informing you that the patch has been excluded from installation owing to incompatibility issues.	A warning message appears in the _SILENT log file informing you that the patch has been excluded from installation owing to incompatibility issues.	A warning message appears in the _Semi Consistency Log file informing you that the patch has been excluded from installation owing to incompatibility issues.	Ensure that the patch to be installed is consistent with the extension or Platform.
The digital signature validation is performed for the executable files (such as msi, exe, dll, msp etc. from extension, platform, prerequisite, post installation or languages folder).	For Error: The executable files which are not digitally signed are excluded from installation. For Warning : Only warning message appears for the files which are not digitally signed and the installation continues. An error or warning message appears in the _SignatureConsistencyLog file informing you that the executable files are not signed.	Same as Custom installation. An error or warning message appears in the _SILENT log and _SignatureConsistencyLog file informing you that the executable files are not signed.	Same as Custom installation. An error or a warning message appears in the _SemiConsistency log and _SignatureConsistencyLog file informing you that the executable files are not signed.	Make sure that the executable files used in installation media are digitally signed. The executable FileTypes is mentioned in SignatureValditationData.json file at path …InstallerDVD\InstallFiles\ NOTE1: During installation, if SignatureValditationData.json file is not found then an error message is shown and installer is not allowed to proceed for further installation. Perform installation process again.