Installation Log Files | ||||||
|
| |||||
Framework/Application Installation Log File
A log file is created every time setup is run for the framework or an application. The file is called install<framework-or-application-name><version>.log, and is installed in the SERVER_INSTALL\Apps\Framework\ directory by default. For example, the log file for the V6R2012 framework is called installFrameworkV6R2012.log.
This log file lists all administrative objects added or modified during installation, objects renamed due to name collisions, MQL commands skipped due to symbolic name collisions, and error conditions. The log file shows messages generated for each installation script that runs during setup. You can determine which program generated the message by looking above the message until you find the line that lists the program that was running.
The following table describes the messages that can appear in the framework/application installation log file.
| Log Message | Condition | Setup Action Performed |
|---|---|---|
| Currently Installed Application >None Installed |
No application is installed in the database. | Install application for the first time. |
| Currently Installed Applications >Application : A1 V1 >Application : A1 V2 |
Applications A1 of version V1 and A2 of version V2 are already installed. | If the application to be installed is the same as A1 or A2, then update installed application objects for latest version, else add new application. |
| Now Installing >Application : A1 V1 |
— | Start installing application A1 of version V1. |
| Adding : program P1 V1 | Program P1 is not present in the database. | Add program to database. |
| Modifying : program P1 V1 | Program P1 with earlier version already exists. | Modify program in the database to update it to the new version. |
| Exists : program P1 | Program P1 with same or newer version is already present in the database. | Do nothing. |
| Adding : adminType A1 V1 | Administrative object A1 is not present in the database. | Add administrative object to the database. |
| Renaming : adminType A1 | Administrative object with same name as A1 is already present in the database. Object is created by customer and not installed by installation scripts. | Don't change the administrative object present in the database. Instead, install object with the name formed by prefixing previous name with string "eService" + <version>. |
| Same Version : adminType A1 V1 | Administrative object A1 with the same version is present in the database. | Do nothing. |
| Modifying : adminType A1 V1 | Administrative object A1 is installed by an earlier version. | Update existing administrative object to make it compatible with the new version. |
| Adding: itemDesc V1 | Administrative bus object not present in the database. | Add administrative object to the database. |
| Modifying : itemDesc V1 | Administrative bus object is already installed by earlier installation script. | Update administrative object by modifying it for the latest version. |
| Adding : Method T1 M1 | Method M1 is not present on type T1. | Add a new method. |
| Exists : Method T1 M1 | Method M1 already exists on type T1. | Do nothing. |
| Removing : Method T1 M1 | Method M1 is defined on type T1. | Remove method. |
| Adding : user U1 | Sample user U1 is not present in the database. | Add a person. |
| Exists : user U1 | Sample user U1 is already present in the database. | Do nothing. |
| Adding : itemDesc | Sample bus object is not present in the database. | Add sample object to the database. |
| Adding : workspace R1 | — | Sets workspace for role R1. |
| Adding : workspace itemDesc V1 | Toolset is not defined in the current operating workspace. | Add Toolset in the operating workspace for version V1. |
| Modifying : workspace itemDesc V1 | Toolset is defined in the current operating workspace. | Modify Toolset in the operating workspace for version V1. |
| Cannot create type xxx not unique type Note: This message should not appear after version 9550. |
There is an existing, custom administrative object with the same symbolic name as an object being installed. | Condition causes the installation to roll back, and creates many additional errors. You need to unregister the existing administrative object. Note: Only for pre-9550 installations. |
| Cannot rename xxx as object already exists with new name | There is an existing, custom administrative object with the same name as the new name you are trying to use. | Condition causes the installation to roll back, and creates many additional errors. You need to unregister the existing administrative object. |
| Skipping mql command for type T version 9-0-0-0 Following command is skipped mql add type T |
There is an existing framework administrative object with the same symbolic name as the object being installed. | Add command is skipped. |
| type T already exists. Following mql command skipped mql add type T |
There is an existing custom administrative object with the same symbolic name as the object being added. | Add command is skipped. |
| Skipping mql command for type T version 9-0-0-0 Following command is skipped mql modify type T |
There is an existing framework object whose version is equal or greater than that of the object being installed. | Modify command is skipped. |
| Syncing type T at version 9-0-0-0 | There is an administrative object with the same symbolic name, Application property of FrameworkFuture, and the same Version property as that of the object being installed. | Application property is changed to Framework, and Modify or Add command is not executed. |
Schema Installation Log File
A log file is created every time the Schema Installer is run. The file is called installSchemaInstaller<version>.log, and is installed in the SERVER_INSTALL\Apps\<version>\SchemaInstaller\ directory by default.
This file contains a section for each version of each installed schema (Application Exchange Framework, Team Central, all other ENOVIA products, and any custom schema.
You may see Modifying messages for a version earlier than your currently installed version (for example, if your installed version were 9.5.5.1 you might see a modifying message for version 9.5.0.0). This situation may occur if a prior conversion executed, but for some reason did not update the version number for the object. The message here indicates that the version has been modified, not that the conversion was run again.
The following table describes the messages that can appear in the schema installation log file.
| Log Message | Description |
|---|---|
| Currently Installed Applications | Lists the applications that have already been installed. |
| Now installing >Application : SchemaInstaller Running SchemaInstallerPrograms.tcl |
The Schema Installer is running. |
| Adding : program P1 V1 | Schema for the program/version added. |
| Running SchemaInstallerCustomPrograms.tcl |
The schema for custom programs (defined by the custom SDF, SMF, and mapping files) is being installed. |
| >Upgrading <version> <application> | Section for each application/version containing the schema changes. |
| >Adding : adminType P1 V1 | Adding administrative objects for the program/version P1/V1. |
| >Modifying : adminType P1/V1 | Modifying administrative objects for the program/version P1/V1. |
| >Modifying : workspace itemDesc V1 | Toolset is defined in current operating workspace. |
MQL Schema Changes Log File
A schema changes log file is created every time the Schema Installer is run. The file is called SchemaChangesMQL<version>.log, and is installed in the SERVER_INSTALL\Apps\<version>\SchemaInstaller\ directory by default.
The file contains the MQL code corresponding to the entries listed in the Schema Installer log file.