krolson
commented
2 years ago Hi @radhikar20 - thank you for reporting this issue. Looking at that sessionId it appears that there was a large amount of time spent in getting the application configuration information on the local machine, which then resulted in the timeout. 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:
1) choose a site 2) assessment report
Expected behavior
Provide a description of the expected behavior. successful assessment
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 09e285e0-a61f-4af8-bff1-c769c3864415. timed out
Known workarounds
Provide a description of any known workarounds.