CMS 10.5–10.6 Post Upgrade Logs
After the Ingeniux CMS 10.5–10.6 upgrade wizard finishes, 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 |
|---|---|---|
| SiteUpgrade_cms-[x].log | [Drive]:\Ingeniux\[CMS-version]\Installers\ | In this log, verify that the message Installation completed successfully displays near the end of the file. 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 uses the error code to help troubleshoot the error. |
| AssetFileMigrationReport.xml | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | 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\ | 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\ | 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\ | In this report, verify that no failures are listed within the
<Failures> tag. If failures exist, use the attribute
information to resolve the issues. |
| ContentUpgrader.log | [Drive]:\[path-to-CMS-install]\site\App_Data\xml\ | This log file tracks the Raven Database (RavenDB) upgrade process. 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 uses the error code to help troubleshoot the error. |
| 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\ | 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\ | 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. |