When the installation program is complete, the Installation Complete dialog box displays.
Click Close to complete the installation. NOTE: In case of any installation errors, such as failure in installing prerequisite/extension/language pack, click the View Log button to open the log file and view the details of the errors (see Description of Installer Error Codes in Installer Troubleshooting).
The selected setup type server/server with web server (IIS) installation is successful. The currently logged in user is added as a member of the IIS_IUSRS group. The default website deleted from IIS manager and hence does not display in SMC. The post-installation steps, if available, for the platform or installed extensions are executed.
(Optional and applicable only for post-installation step – License Activation) The licenses are upgraded and activated based on the license files (.lic) available and/or Activation/Entitlement IDs specified. You can verify license activation of these files in LMU. For already active licenses, expired licenses, invalid file format or missing files, and so on a message displays: Installation Successful but with some errors in the Installation Complete dialog box. In this case click View Log that displays in the Installation Complete dialog boxto open the Installer ELog file located at the path [System drive]:\ProgramData\[company name]\GMS\InstallerFramework\GMS_Installer_Log.
(Optional and applicable only for post-installation step – Project Setup) The already existing active project is upgraded, activated and started by default. If the History Database was linked to the previously active project, it is also upgraded along with the Long Term Storage, if any and then all the existing web sites and web applications are also upgraded, even if upgrade of the any of the existing web application fails. The already existing certificate is used for securing the communication between the Windows App client and the web server (IIS). Finally displays the logon dialog box for specifying the credentials. If there is no already existing project, HDB and website/web application available for upgrade, then the JSON file is referred to for the creation of the project, History database and website/web application. Note that even if the HDB creation/upgrade fails, the post-installation continues with the next step. In that case, you can re-run the post-installation step for HDB creation/upgrade. For the configured an existing project’s Pmon user/web application user, if the password is expired, then the web application upgrade fails and you must manually update the web application using SMC. For more information, refer to the SMC log at the path [Installation drive]:\[installation folder]\GMSMainProject\log.
(Optional and applicable only for post-installation steps of other extensions) The post-installations steps of other extensions, when correctly configured, enabled (modified the .txt file to.xml) are executed as well successfully.
(Optional and applicable only for Quality Updates and Hotfixes) The patches for prerequisites, platform, mandatory extensions, and the non-mandatory extensions, as applicable, are upgraded. For any errors during the patch installation, refer (_ELOG) file.
