OGIMIGE0002 | ERROR: Missing file in source installation - {0} |
Explanation |
This message is displayed when no source file is found. |
Action |
Check if the file exists and is readable for the user. |
OGIMIGE0003 | ERROR: Missing file in destination installation - {0} |
Explanation |
This message is displayed when no destination file is found under path: <installdir_new_version>/profiles/<some_profile>/configuration/com.softwareag.platform.config.propsloader/ |
Action |
Check if the file exists and is readable for the user. |
OGIMIGE0004 | ERROR: Backup failed for destination file - {0} |
Explanation |
The file is backed up before merging . Losing this file might be crucial. |
Action |
Make sure that the file can be written in the parent directory. |
OGIMIGE0006 | ERROR: Error while opening file - {0} |
Explanation |
In order to migrate a file its content should be read. This error occurs because the file could not be opened properly. |
Action |
Make sure the file is not locked (for example, the file may be already opened by another program). |
OGIMIGE0007 | ERROR: Result configuration file in destination installation was not found - {0} |
Explanation |
After merging, the result is either a new file, or an updated overwritten destination file. |
Action |
Please make sure the file exists and is readable for the user. |
OGIMIGE0010 | ERROR: More than one in the destination installation - {0} were found under {1} |
Explanation |
This message is displayed when more than one destination file is found. This is not expected if a clean destination installation is done. |
Action |
Check the log file to see where are the files. Remove the unneeded files and leave only one file - the default one. |
OGIMIGE0013 | ERROR: Loading source properties layout configuration failed. The source file is: from file {0} |
Explanation |
When we load our properties we also load the comments and blank lines the file contains. |
Action |
Make sure that you source file is a valid java poprerty file and it is not corrupted. |
OGIMIGE0014 | ERROR: Cannot identify version of product {0}. Cannot find any locally installed products in the specified installation directory: {1} |
Explanation |
The migration application attempted to identify the version of a locally installed product with the given product prop file name (without the .prop suffix), but no locally installed products were found in the specified installation directory. |
Action |
Specify the source version of the product when prompted to. |
OGIMIGE0015 | ERROR: Cannot identify version of product {0}. Cannot find this product in the list of locally installed products in the specified installation directory: {1} |
Explanation |
The migration application attempted to identify the version of a locally installed product with the given product prop file name (without the .prop suffix), but such locally installed product was not found in the specified installation directory. |
Action |
Specify the source version of the product when prompted to. |
OGIMIGE0018 | ERROR: Storing result properties configuration layout failed. |
Explanation |
The property file with all the properties and their comments failed on the saving step. |
Action |
Check the file access permisions of your taget installation. |
OGIMIGE0019 | ERROR: JAAS configuration {0} does not exist. |
Explanation |
The JAAS configuration file is missing and the migration cannot proceed. |
Action |
Migration for JAAS configuration was not successful. Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0020 | ERROR: JAAS configuration {0} is not a file. |
Explanation |
The JAAS configuration file is not a valid file and the migration cannot proceed. |
Action |
Migration for JAAS configuration was not successful. Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0021 | ERROR: Destination JAAS configuration {0} does not exist. |
Explanation |
The JAAS configuration file is missing and the migration cannot proceed. |
Action |
Migration for JAAS configuration was not successful. Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0022 | ERROR: Destination JAAS configuration {0} is not a file. |
Explanation |
The destination JAAS configuration file is not a valid file and the migration cannot proceed. |
Action |
Migration for JAAS configuration was not successful. Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0023 | ERROR: Backup failed for destination JAAS configuration file - {0}. |
Explanation |
Migration of the JAAS configuration was unsuccessful. Creating a backup of the original file was unsuccessful and and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0024 | ERROR: Error parsing source JAAS configuration {0} |
Explanation |
Migration of the JAAS configuration was unsuccessful. An error is found in the source JAAS configuration and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0025 | ERROR: Error parsing destination JAAS configuration {0} |
Explanation |
Migration of the JAAS configuration was unsuccessful. An error was found in the destination JAAS configuration and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0026 | ERROR: Error saving destination JAAS configuration - {0}. |
Explanation |
Migration of the JAAS configuration was unsuccessful. An error occured while storing the migrated JAAS configuration and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0028 | ERROR: Source server.xml configuration {0} does not exist. |
Explanation |
The server.xml file could not be migrated because the file does not exist. |
Action |
Check if the source server.xml file exists and is readable for the user. |
OGIMIGE0029 | ERROR: Source server.xml configuration {0} is not a file. |
Explanation |
The server.xml is not a proper file. |
Action |
Check the server.xml file. |
OGIMIGE0030 | ERROR: Parsing server.xml file {0}. |
Explanation |
The server.xml file is not a valid XML file. |
Action |
Check the server.xml file. |
OGIMIGE0031 | ERROR: Reading server.xml file {0}. |
Explanation |
The server.xml file could not be read properly. |
Action |
Check the server.xml file. |
OGIMIGE0032 | ERROR: Parser Configuration server.xml file {0}. |
Explanation |
Parser error occurs when parsing the server.xml file. |
Action |
Check the server.xml file. |
OGIMIGE0033 | ERROR: Backup file {0}. |
Explanation |
The file could not be backed up successfully. |
Action |
Check the source location and target location paths and files. |
OGIMIGE0034 | ERROR: Reading file {0}. |
Explanation |
The error occurs because the file could not be read properly. |
Action |
Check the source location and target location paths,files, and permissions. |
OGIMIGE0035 | ERROR: Writing file {0}. |
Explanation |
The error occurs because the file could not be written properly. |
Action |
Check the source location and target location paths,files, and permissions. |
OGIMIGE0036 | ERROR: Create/Update file {0}. |
Explanation |
The error occurs because the file could not be created or updated properly. |
Action |
Check the source location and target location paths,files, and permissions. |
OGIMIGE0042 | ERROR: Configuration migration finished with failure(s). |
Explanation |
Migration failed for the server.xml, web.xml, and config.xml, *.jks files. |
Action |
Check the detailed error messages displayed by the migration tool. |
OGIMIGE0048 | ERROR: Cannot identify version of product {0}. The product installation under {1} does not contain any build modules for the current installer platform: {2} |
Explanation |
The migration application attempted to identify the version of a locally installed product, but the local product is targeting a different installer platform (operating system and architecture) and the product information could not be loaded. |
Action |
Specify the source version of the product. |
OGIMIGE0049 | ERROR: Cannot parse version of product {0}. The product version {1} does not have valid syntax. Expecting a version in the format <major>.<minor>.<micro>.<fixnum>.<buildnum>. |
Explanation |
The migration application attempted to identify the source version of a locally installed product, but the product version did not have a correct format. |
Action |
Specify the source version of the product. |
OGIMIGE0052 | ERROR: User repository file does not exist in the expected location: {0} |
Explanation |
Migration for common/conf entries was not successful.The users.txt file was not found in the expected location. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0053 | ERROR: Error reading user repository file: {0} |
Explanation |
Migration for common/conf entries was not successful. The users.txt file could not be read from the expected location. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0054 | ERROR: User repository file version cannot be retrieved: {0} |
Explanation |
Migration for common/conf entries was not successful. The users.txt file was not migrated. An unexpected error occurred during the retrieval of the users.txt file version. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0055 | ERROR: User repository version is not compatible. Required minimal version is: {0}, found version is: {1}. Manual steps are required. |
Explanation |
Migration for common/conf entries was not successful. The users.txt file cannot be migrated if the files in both locations are not with compatible versions. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0056 | ERROR: User repository version could not be retrieved: {0} |
Explanation |
Migration for common/conf entries was not successful. An unexpected error occurred during the compatibility check of the users.txt file. The users.txt file must be migrated manually. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0058 | ERROR: Source user repository file does not exist: {0} |
Explanation |
Migration for common/conf entries was not successful. The source user repository file users.txt cannot be found in the specified location. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0059 | ERROR: Destination user repository file does not exist: {0} |
Explanation |
Migration for common/conf entries was not successful. The destination user repository file users.txt cannot be found in the specified location. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0060 | ERROR: Source user repository file {0} could not be copied to destination. |
Explanation |
Migration of common/conf entries was unsuccessful. The source user repository file users.txt cannot be copied to destination due to an unexpected error. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0066 | ERROR: Missing source SSH configuration file {0} |
Explanation |
Migration of the SSH configuration was not successful. The source file with the SSH configuration is not found and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0067 | ERROR: Error reading source SSH configuration file {0} |
Explanation |
Migration of the SSH configuration was not successful. An error occurred while reading the source SSH configuration file and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0068 | ERROR: Missing destination SSH configuration file {0} |
Explanation |
Migration for SSH configuration was not successful. The destination configuration file for the SSH configuration cannot be found and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0069 | ERROR: Error backing up destination SSH configuration file {0} |
Explanation |
Migration of the SSH configuration was not successful. An error occurred while trying to backup the original destination SSH configuration file and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0071 | ERROR: Destination SSH config file not found {0} |
Explanation |
Migration for the SSH configuration was not successful. The destination SSH config file was not found and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0072 | ERROR: Error storing migrated SSH configuration {0} |
Explanation |
Migration of the SSH configuration was not successful. An error occurred while storing the migrated SSH configuration and the migration cannot proceed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0073 | Invalid source installation directory specified: {0}. No {1} subdirectory is present, this directory is required for the {2} migration to proceed. |
Explanation |
The migration application requires the specified product subdirectory to be available in the source installation in order to proceed, but the directory was not found. This can happen if the product, for which the migration is executed is not available in the source installation directory. |
Action |
Make sure that the specified source installation contains the product that is being migrated. |
OGIMIGE0081 | In file {0} Keystore/Truststore file referenced from HTTPS Connector in attribute {1} that can not be found, creating a valid HTTPS configuration not possible. |
Explanation |
The server.xml file contains a Keystore/Truststore configuration (keystoreFile= truststoreFile=), pointing to a file that cannot be found. Migrating this would lead in an unusable HTTPS configuration. |
Action |
In your profile check the file /tomcat/conf/server.xml and the properties keystoreFile="TheKeystoreFilename" truststoreFile="TheTrustStoreFileName". Also check that the file(s) TheKeystoreFilename/TheTrustStoreFileName are existing and valid keystore/truststore files or reference the delivered default one: keystoreFile="C:\SAG822\profiles\CTP\configuration\tomcat\conf\localhost_dont_use_in_production.jks" and start the migration again. |
OGIMIGE0083 | ERROR: Backup file cannot be created - invalid value for destination file passed - {0}. |
Explanation |
While trying to create a backup of the original file, an invalid original file was passed. |
Action |
Check the log for more details. |
OGIMIGE0084 | Cannot identfy installer platform for specified installation directory: {0}. Reason: Cannot read installation metadata file: {1} |
Explanation |
The migration application needs to verify that the source installation is created for the same operating system and architecture as the destination installation. This is done by inspecting the installation metadata located under install/products directory in the installation. If the installation metadata is missing or corrupt, or the process does not have read permissions for the specified file, the platform identification will fail and the migration cannot proceed. |
Action |
Make sure that the specified installation directory contains proper installation metadata (install/products directory containing installer property files for installed products) and the process has the correct privileges to read it. |
OGIMIGE0086 | Failed to read file ''{0}''. |
Explanation |
The platform migration utility could not read the specified file. |
Action |
Make sure the file exists and the user executing the migration is authorized to read it. |
OGIMIGE0087 | Failed to close file stream ''{0}''. |
Explanation |
An I/O error occurred while closing the file stream. |
Action |
Make sure the file exists and the user executing the migration is authorized to read it. |
OGIMIGE0089 | An invalid path property ''{0}'' was found in file ''{1}''. Path should not be null or empty. |
Explanation |
A path property sent for transformation has a null or empty value. Transformation cannot proceed with an invalid argument. |
Action |
Ensure that the property referenced in the given file has a valid path value. |
OGIMIGE0092 | The path ''{0}'' is referenced in file ''{1}''; it should be available as ''{2}'', but could not be found. Hence the path cannot be migrated. |
Explanation |
The path transformer has discovered that a path referenced in a file in the source installation points to a file inside the source installation. The file does not exist and the configuration is invalid. |
Action |
Ensure that the path referenced in the specified file points to a valid file on the file system. |
OGIMIGE0095 | The absolute path ''{0}'' referenced in file ''{1}'' does not exist on the file system. |
Explanation |
The path transformer has discovered that a path referenced in a file in the source installation points to a file outside the source installation. The file does not exist and the configuration is invalid. |
Action |
Ensure that the path referenced in the specified file points to a valid file on the file system. |
OGIMIGE0097 | Could not determine original installation location for ''{0}''. |
Explanation |
The path transformer failed to determine the original source installation root directory, which is required in order for the transformer to function properly. |
Action |
Make sure the migration source directory contains a "profiles" folder with at least one valid profile inside. |
OGIMIGE0098 | The original source directory ''{0}'' exists on this file system but the current migration is using ''{1}'' as a source. Path transformation is not supported. |
Explanation |
Path transformer determined that the migration source directory is different from the original source installation root directory (which could be the case when you are migrating from a zip file or from a mapped/mounted directory). However, the original source installation root directory exists on this file system but it is not used as a migration source directory. This is not a supported path transformation scenario as the system may not reliably validate the transformed paths. |
Action |
If the original source installation directory is available on the same file system it should be used directly as a migration source directory. |
OGIMIGE0099 | The target directory ''{0}'' must be the same as the installation root directory ''{1}''. |
Explanation |
The target directory in the migrated profile config.ini file is different from the migration target directory. The target installation is corrupted. |
Action |
Make sure that the migration target directory is not moved or tampered with. |
OGIMIGE0102 | Failed to copy transformed file path from ''{0}'' to ''{1}''. |
Explanation |
Path transformer transformed a file path from the migration source directory to the migration target directory. The file copy operation failed. |
Action |
Make sure that the user executing the migration is able to physically copy the source file to the destination. |
OGIMIGE0103 | An invalid URL property ''{0}'' was found in file ''{1}''. URL should not be null or empty. |
Explanation |
A URL property sent for transformation has a null or empty value. Transformation cannot proceed with an invalid argument. |
Action |
Ensure that the property referenced in the given file has a valid URL value. |
OGIMIGE0107 | Source installation directory ({0}) uses ''{1}'' platform, while destination installation directory ({2}) uses ''{3}''. |
Explanation |
The migration cannot proceed if the source and destination installation platforms are different. |
Action |
Make sure the source and destination directories contain installations of one and the same platform. |
OGIMIGE0111 | ERROR: copy file{0}. |
Explanation |
Copy file operation failed. |
Action |
Make sure the file exists and is not used or opened by an application. |
OGIMIGE0113 | Error while merging the properties from "{0}" to "{1}". |
Explanation |
Merging the .properties files failed with an error. |
Action |
Check the logs for more information. |
OGIMIGE0115 | ERROR: Error during finalization of the JAAS configuration. |
Explanation |
An error occured while finilizing the migrated JAAS configuration and the migration could not proceed. |
Action |
Contact Software AG Global Support. |
OGIMIGE0116 | Abort migration due to errors while evaluating source installation {0} |
Explanation |
Migration of roles.txt entries was not successful due to problems with the source SAG product installation. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0117 | Abort migration due to errors while evaluating destination installation {0} |
Explanation |
Migration of roles.txt entries was not successful due to problems with the source SAG product installation. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0118 | Error while reading source 'roles.txt': {0} |
Explanation |
Unexpected error occured while reading the 'roles.txt' file from the source SAG product installation. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0119 | Error while reading destination 'roles.txt': {0} |
Explanation |
Unexpected error occured while reading the 'roles.txt' file from the destination SAG product installation. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0121 | Cannot backup {0}. Migration is not safe. Proceeding with next migration. |
Explanation |
Cannot create backup copy of the 'roles.txt' file. Migration might be successful but if it fails the previous content of the 'roles.txt file can't be restored. Therefore, we skip the migration for this particular 'roles.txt' file. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0122 | Error while merging {0} and {1} |
Explanation |
Unexpected error occured while merging the content of source and destination installation 'roles.txt' files. The current migration will be skipped and the original 'roles.txt' content will be restored. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0123 | 'config.ini' doesn't exist or is not file: {0} |
Explanation |
Cannot proceed with the migration since the required configuration file 'config.ini' doesn't exist. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0126 | Configuration location {0} doesn't exist or is not file. |
Explanation |
The specified configuration location doesn't exist and therefore the migration process will be skipped. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0127 | Configuration location {0} does not exist. |
Explanation |
The specified configuration location doesn't exist and therefore the migration process will be skipped. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0128 | Configuration location {0} is not a file. |
Explanation |
The specified configuration location doesn't exist and therefore the migration process will be skipped. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0129 | Cannot create backup file: {0} |
Explanation |
The migration is not able to create a backup file for the JAAS configuration. |
Action |
Check the source location and target location paths, files, and permissions. |
OGIMIGE0130 | This is not a valid destination backup file location: null |
Explanation |
Missing destination backup file location. |
Action |
Check the source location and target location paths, files, and permissions. |
OGIMIGE0131 | The destination backup file location "{0}" does not exist. |
Explanation |
The destination backup file location does not exist. |
Action |
Check the source location and target location paths, files, and permissions. |
OGIMIGE0134 | JKS "{0}" with file {1} is missing a mandatory property for password from the configuration file. |
Explanation |
If a truststoreFile property exists in the configuration, there must be a truststorePass property. The same rule applies for the keystoreFile and keystorePass properties. |
Action |
Check the properties of the HTTPS connectors. |
OGIMIGE0135 | The backup of "{0}" failed. |
Explanation |
The specified file cannot be copied or deleted after backup. |
Action |
Check for permisions on the file. |
OGIMIGE0136 | The migration of key/certificates from "{0}" to "{1}" failed. |
Explanation |
The migration of certificates and keys is failing for the specified Java Key Stores. |
Action |
Ensure that the property files are pointing to the correct locations of the trustore and the keystore in the source installation. Ensure that the password in the configuration is correct and the configuration is operational. |
OGIMIGE0137 | Can not find the needed infrastructure components in the installation. |
Explanation |
A requirment to "Infrastructure/Libraries/Shared Libraries" is needed. |
Action |
Make sure that "Infrastructure/Libraries/Shared Libraries" component from the install tree is installed. |
OGIMIGE0141 | Cannot clean destination directory. |
Explanation |
Read/write access is not possible. |
Action |
Validate there no other process is using the direcotry |
OGIMIGE0143 | The keystores {0} and {1} do not exist. |
Explanation |
Both the default and the backup keystores are missing. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0144 | The certificate with alias {0} could not be copied from source to target. |
Explanation |
The certificate cannot be copied. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0145 | Path transformation for trustStoreLocation of "{0}" was not successful. Migration will fail. |
Explanation |
Trust store transformation failed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0146 | Path transformation for keyStoreLocation of "{0}" was not successful. Migration will fail. |
Explanation |
Key store transformation failed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0147 | Cannot find "{0}" in path "{1}" |
Explanation |
The profiles folder is missing. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0148 | Keystore {0} specified in {1} does not exist on file system. |
Explanation |
The specified key store does not exist |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0149 | Cannot transform tomcat relative path {0} to absolute. |
Explanation |
The configured Tomcat directory is wrong. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0150 | Cannot find location for: {0} |
Explanation |
Key store cannot be found. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0151 | Cannot open keystore file. |
Explanation |
Key store file cannot be opened. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0152 | ERROR migrating configurations from source to destination. |
Explanation |
Configuration migration failed. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0153 | Cannot clean destination directory. |
Explanation |
Migration destination directory cannot be cleaned. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0156 | Cannot create destination file - {0}. |
Explanation |
The destination file cannot be created. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGE0158 | Cannot copy configuration from {0} to {1} |
Explanation |
Failed to copy the configuration of the source file. |
Action |
Ensure that the source file has a valid configuration. |
OGIMIGE0159 | Cannot convert {0} to canonical path. |
Explanation |
The path to the file cannot be converted to a canonical path. |
Action |
None. |
OGIMIGE0165 | Loading properties layout configuration failed for file {0} |
Explanation |
The property file failed to be loaded. |
Action |
Check the file access permisions of your installation. |
OGIMIGI0133 | This login context is skipped by migration, because it contained SSX login module, but In version 10.x SSX is no longer available and migration is not possible |
OGIMIGW0005 | WARNING: File could not be deleted - {0}. |
Explanation |
An error occured while deleting incompatible destination file. This is a warning message because deleting this file should not be crucial for the finctionality of the application. |
Action |
Delete this file manually as it may cause future conflicts. |
OGIMIGW0008 | WARNING: Referenced file was found in the source installation but was not found in the destination installation: "{0}" . Check if the file was migrated and if not migrate it manually. |
Explanation |
Configurations could have properties with values that contain paths to files. During migration these paths could become invalid. To prevent the migration of such paths that make the configurations unusable, a check is done if the file exists in the new installation. This warning shows that the file was successfully located in the source installation, but was missing from the destination. |
Action |
Check if the path from the configuration is valid after the migration. If the path is not valid, migrate the file manually and edit the path if needed. |
OGIMIGW0009 | WARNING: Referenced file was not found in the destination system: "{0}" |
Explanation |
Configurations could have properties with values that contain paths to files. During migration these paths could become unvalid. To prevent the migration of such paths that make the configurations unusable, a check is done if the file exists in the new installation. |
Action |
Check if the path from the configuration is valid after the migration.If the path is not valid, migrate the file manually and edit the path if needed. |
OGIMIGW0011 | WARNING: Property value for key {0} could not be transformed properly. |
Explanation |
During migration some properties require special transformation of their values and transformer classes are used. This message is shown when the class cannot be found or instantiated, or it is not a valid transformer class. This could lead to invalid property values. |
Action |
Check the value of the migrated property. |
OGIMIGW0012 | WARNING: Installer client jar not available, falling back on custom installer metadata parser. |
Explanation |
Migration framework did not find a required jar for reading the installation metadata, it will attempt to read the metadata by parsing the prop file instead. |
Action |
No action is required. |
OGIMIGW0016 | WARNING: Properties for transformation were not loaded.This might make your configuration unusable. |
Explanation |
We are using special files that map properties which need some kind of transformation for their value or key. In order to use them we have to load them from a file. This step has failed. |
Action |
Contact Software AG global support. |
OGIMIGW0017 | WARNING: Transformer class was not found for the following property: |
Explanation |
We allow custom property transformation which is done via a class. The loading of this class has failed. One or more properties were not transformed correctly. |
Action |
Contact Software AG global support. |
OGIMIGW0027 | WARNING: Some runtime components were not enabled in the source configuration - {0}. Migration exits successfully. |
Explanation |
Some runtime componets like JMX, SSH are not enabled in the source configuration. No data will be migrated from these source configurations. |
Action |
To explicitly disable a component, change the port property in the destination installation. |
OGIMIGW0037 | WARNING: Error on read file {0}. |
Explanation |
The error occurs because the file could not be read properly. |
Action |
Check the source location and target location paths,files, and permissions. |
OGIMIGW0038 | WARNING: Error on write file {0}. |
Explanation |
The error occurs because the file could not be written properly. |
Action |
Check the source location and target location paths,files, and permissions. |
OGIMIGW0051 | WARNING: Using the default 'localhost_dont_use_in_production.jks' file in file {0} property name {1}, because the file referenced in the older version could not be found. Change the file specified in the property. |
Explanation |
The specified property in the specified properties file points to the default .jks keystore file, because the keystore file referenced in the older version could not be found. |
Action |
Change the property to point to a valid existing production .jks keystore file. |
OGIMIGW0065 | WARNING: SSH port is not set in source configuration {0}. Migration exits successfully. |
Explanation |
SSH port is not set in source configuration so there is nothing to migrate. |
Action |
SSH port is not set in configuration and nothing is done. If this is not the case, refer to the upgrade documentation and execute the required manual steps. |
OGIMIGW0104 | Value for JAAS configuration in config.ini could not be processed. |
Explanation |
The JAAS configuration modifications will be made to the original JAAS configuration located in the profile folder. |
Action |
Define an absolute path to the current location of the JAAS configuration to be migrated or move it in the profile configuration folder. |
OGIMIGW0108 | WARNING: source internal user repository file users.txt not present : "{0}" Skip the migration of users.txt; groups.txt, roles.txt. |
Explanation |
The users.txt internal user repository file is not present in common/conf directory. The file(s) could not be migrated. |
Action |
Check the profiles/TheProfile/configuration/jaas.config for the following entry: internalRepository="ADirectory/users.txt"and check if this is migrated by the jaas config migration. Do the same for the groups.txt and roles.txt files. If there is no such entry, a migration of that file is not nesecessary, because no internal user repository for authentication is enabled or configured. |
OGIMIGW0112 | WARNING: security configuration source file scPassMan.config.xml missing. File is mandatory! Skipping migration of all passman files. |
Explanation |
Passman security configuration files are normally 3 files : scPassMan.config.xml ; defaultPassStore.dat and mpw.dat . The .dat files are optional, but the .xml is important and without it migration cannot be done. |
Action |
Check whether the scPassMan.config.xml file is present in the following location: installdir/profiles/TheProfile/configuration/security. With the xml file present, retry migration or migrate manually. |
OGIMIGW0132 | Found SSX login module {2} in source {0}. SSX is removed in 10.0, so login context {1} will not be migrated. |
Explanation |
SSX login module is found in source installation, but SSX is removed in version 10.0, so we can't migrate it properly |
Action |
Migrate login context by hand as it is not possible not migrate it automatically. |
OGIMIGW0138 | Attribute {0} for appender {1} does not have mapping in log4j2 and cannot be migrated. |
Explanation |
A predefined mapping list of appender attributes for log4j1 and log4j2 configurations exists. An attribute that is not in the mapping list is not supported and cannot be migrated. |
OGIMIGW0139 | Appender {0} cannot be migrated because its class {1} is not supported. |
Explanation |
Only the appenders of org.apache.log4j.RollingFileAppender and org.apache.log4j.ConsoleAppender log4j1 types are supported for migration to log4j2 configuration. |
OGIMIGW0140 | Logger {0} cannot be migrated because it uses unsupported appenders. |
Explanation |
If a logger uses appenders that are not supported for migration to log4j2 configuration, it cannot be migrated. Only the appenders of org.apache.log4j.RollingFileAppender and org.apache.log4j.ConsoleAppender log4j1 types are supported for migration to log4j2 configuration. |
OGIMIGW0142 | Logger configuration in source must have valid appenders. |
Explanation |
Every log4j logger must have the following syntax: log4j.logger.<loggerName>=<level, appenderName> |
Action |
Ensure that the configuration file of the audit logger in the source installation has a valid syntax. |
OGIMIGW0154 | Creating file {0} with configurations {1} has failed. |
Explanation |
Cannot create file for configuration migration. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGW0155 | Migration for configuration file {0} is skipped because {1} type already exist in destination. |
Explanation |
The target configuration already exists. |
Action |
Refer to the upgrade documentation and execute the required manual steps. |
OGIMIGW0157 | Retrieving the password from Passman has failed: {0}. |
Explanation |
Cannot retrieve the password from Passman. |
Action |
Contact Software AG Global Support. |
OGIMIGW0160 | External JKS file found. The migration framework does not support migration of keystores outside the Software AG installation. Skipping migration for file {0} |
Explanation |
The migration framework does nоt support the migration of keystores outside the Software AG installation directory. The external JKS file will not be migrated. |
Action |
None. |
OGIMIGW0161 | No ConversionPattern attribute is specified in the source configuration. {0} will be used instead. |
Explanation |
ConversionPattern attribute is missing in the source configuration. The default ConversionPattern will be used instead. |
Action |
None. |
OGIMIGW0162 | Migration is successful, but failed to reorder the migrated configuration file {0}. Reason: {1} |
Action |
None. |
OGIMIGW0163 | Found a configured proxy in destination. Skipping migration for proxy configuration type {0} |
Explanation |
There is a configured proxy in the destination installation. Тhe proxy of the same type from the source installation will not be migrated. |
Action |
None. |
OGIMIGW0164 | The configuration file of Metering Agent doesn't exist: {0} |
Explanation |
The metering.agent.properties file is not present in common/metering/conf/ directory. The file could not be migrated. |
Action |
Make sure you have installed product webMethods Metering. |