Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning content is displayed in garbled text on the Assessment Report screen in AppServiceMigrationAssistant #95

Open
ApprenticeTech opened this issue Aug 16, 2024 · 2 comments

Comments

@ApprenticeTech
Copy link

Investigative information

  • UTC Timestamp: 2020/06/12 3:07(GMT +09:00)(AppServiceMigrationAssistant.msi)
  • Migration Tool App version : 1.0.6(AppServiceMigrationAssistant)
  • OS Version: Windows Server 2016 Standard, Version 10.0.14393

Repro steps

  1. Run the installer (AppServiceMigrationAssistant.msi).
  2. Start the migration tool from the ‘AppServiceMigrationAssistant’ desktop screen.
  3. Select the site to be migrated on the Start screen and press NEXT.
  4. In the Assessment Report screen, the warning content is displayed in garbled text in the Warning Details column.
    Note : the language of the execution environment here is Japanese.

Expected behavior

The warning content can be read without garbling.

Actual behavior

As described in 4 of Repro steps.

Known workarounds

Nothing.

AzureASMigration_AssessmentReport_GarbledText

@ApprenticeTech ApprenticeTech changed the title Warning content is displayed in garbled text on the Assessment Report screen in AppServiceMigrationAssistant. Warning content is displayed in garbled text on the Assessment Report screen in AppServiceMigrationAssistant Aug 16, 2024
@krolson
Copy link
Contributor

krolson commented Aug 22, 2024

Thank you for reporting this issue. This will be tracked for future updates.

The PowerShell script Get-SiteReadiness may return the information without the garbling (information: https://github.com/Azure/App-Service-Migration-Assistant/wiki/PowerShell-Scripts) if you end up trying this please let us know if it behaves differently for you.

@ApprenticeTech
Copy link
Author

Thank you for your response.

I executed Get-SiteReadiness.ps1 and investigated the range including the migration target site name in the output JSON file.

I have confirmed that the FailedChecks and WarningChecks in the JSON file generally correspond to the Error and Warning contents of the Assessment Report.
However, there did not appear to be any text that could be considered to correspond to the garbled messages I wanted this time.

In addition, there seems to be a slight difference in the warning content.

Assessment Report

JSON

The following text is on the Learn More link page, but the location of the log file could not be determined.
It appears that they are not in the System and Application of the Windows Log, and not in IIS logs "%SystemDrive%\inetpub\logs\LogFiles\W3SVC~".

"Review logs on the host machine to determine the errors being encountered by the web app."

However, because the following description was found in the JSON file, it seems that it is good to follow this, so it is recognised that a solution has been found.

Recommendation: Avoid storing application secrets such as database credentials in configuration files and consider updating to use Azure app setting environment variables or integration with Key Vault.

It would be best if we could check the log file on the host machine, but if this is not possible, we would like to implement the measures described in the JSON file.

Thank you for reading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants