krolson
commented
2 years ago Hi @neville-mooney - thank you for letting us know this is happening! Looking at that sessionId I can see that it took about 13 minutes to get the local machine configuration details (this can happen due to a large amount of site content, which increases the amount of time to load all IIS configuration - which might be at any level of the site - or determine content size), and then additional time for a check on connection strings in web.configs, likely for the same reason. These are eventually timing out the GUI waiting for the result. You would likely be able to duplicate this behavior using the commandline iisConfigAssistant.exe (i.e. if you did step 4 as noted here: https://github.com/Azure/App-Service-Migration-Assistant/wiki/How-the-Assistant-Works#what-information-is-sent-for-assessments it would also take a very long time).
The PowerShell migration scripts would be an option to evaluate and migrate this site instead, as it has some optimizations that should make the assessment step much quicker. The scripts are available on http://aka.ms/appmigrate ("App Service migration assistant for PowerShell scripts (preview)") - notes on how to use them are here: https://github.com/Azure/App-Service-Migration-Assistant/wiki/PowerShell-Scripts
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
Provide a description of the expected behavior.
Assessment should complete without error.
Actual behavior
Provide a description of the actual behavior observed.
"We're sorry, there has been an error. To get help, please use the Help > Report Issues menu option and include the following information: Session bc60a3ba-c6fe-4b19-bfc7-a34f5ce19d57. timed out" Appears after 20 minutes or so.
Known workarounds