Viewing the Export and Import Logs
The Configuration Portability Logs window lists all export and import log files generated by a configuration portability import or export.
Limited Support/End of Life Capabilities
If you need to request a hotfix or support for these features, please contact Alemba Support
Errors encountered during the import or export process appear in the log, such as differences in settings between the source system data and the target system after the import. The log includes a summary of data-related discrepancies.
The version number of the configuration portability module used for the import or export is also included in the log file. The version number can assist in troubleshooting if errors occurred during the import or export.
Log on to ASM Core in the source or target system, depending on the log you wish to view.
Select Admin > Configuration Portability.
In the Explorer pane, expand Configuration Portability, then select Export and Import Logs.
Select the log you want to view. The Action column in the browse table indicates whether the log is an export or import log. You can adjust the column widths if required.
Select the Action icon.
The log details are displayed, including the version number and errors, which can be useful when troubleshooting.
The version number of the Configuration Portability module used to export or import configuration settings is indicated in the fifth line of the log as such: “Version: X.RP.Y” where X refers to the version number of the Configuration Portability module, RP refers to the rolling patch release and Y refers to the build number
A summary of data-related discrepancies and warnings are displayed in the errors section of the log. This includes configuration setting differences between the imported data file and the target system after an import. It also lists any duplicate items created as a result of the import.
If the export is stopped because of a server failure, perform another export of the data. In the case of an import, restore the target system from a backup and import the data again.
Save the log file to an external file if needed by selecting .
Analysts with the appropriate permissions can also access the Activity Log.