Post Migration Logs
After the migration wizard has finished, check to see if any errors were thrown during the process. The following table contains the names of relevant log files and reports and what you should look for in each.
| Name | Location | Notes |
|---|---|---|
| GenerationUpgrade_[x].log | [Drive]:\Ingeniux\[CMS-version]\Installers\ | Logs the overall generation upgrade process. In this log, search for DEBUG: Error, then read the corresponding error message. If you require more information to resolve the error than provided by the message, note the error code, then contact Ingeniux Support. Support will use the error code to help troubleshoot the error. |
| AssetFileMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | Tracks the assets as they are migrated into CMS 10. In this
report, verify that no failures are listed within the
<Failures> tag. If failures exist, use the attribute
information to resolve the issues. |
| AssetSecurityMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | Tracks the security permissions that were applied to Asset Folders as they
are migrated into CMS 10. In this report, verify that no failures are listed
within the <Failures> tag. If failures exist, use the
attribute information to resolve the issues. |
| ComponentMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | Tracks the migration of component types. In this report, verify that no
failures are listed within the <Failures> tag. If a
failure exists, the associated ID and reason for the failure are found within
the @Id and @Reason attributes,
respectively. |
| ContentUnitMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | Tracks the remapping of content values after they certain values are
upgraded to CMS 10. In this report, verify that no failures are listed within
the <Failures> tag. If failures exist, use the attribute
information to resolve the issues. |
| GenerationUpgrade_ContentMigrationLog_[x].xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | Logs the migration of content during the generaion upgrade process. In this
report, verify that no <Failures> tags are listed as
children within the <SecurityDescriptors>,
<SchemaL10nOverrides>,
<GlobalExports>, or
<PCRDescriptors> tags. If
<Failure> tags exist, see their values for more
information. |
| PageElementMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | In this report, verify that no <Element> tags are
listed as children within the Failures tag. If failed elements exist, review
their attribute values for information about the failed element and reason for
failure. |
| SchemaMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | Logs the migration of schemas to CMS 10. In this report, verify that no
failures are listed within the <Failures> tag. If
failures exist, use the attribute information to resolve the issues. |
| UnusedAssetsMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | This report lists all unused assets. These are assets that exist in the system; however, they are not used in the content. |
| AssetMigration.log | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | Logs the migration of assets during the upgrade process to CMS 10. In this log, verify that the asset migration has completed successfully by scrolling to the last line of the file. The last log message should indicate that the asset migration has completed. |