Open ApprenticeTech opened 1 month ago
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.
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.
Investigative information
Repro steps
Expected behavior
The warning content can be read without garbling.
Actual behavior
As described in 4 of Repro steps.
Known workarounds
Nothing.