Session timeout

[mikefitzpat]

Hi,

The Migration tool has returned an error, "Session a76a2f76-8569-435b-b749-229586236038. timed out"

Is it possible to see what the cause is please.

It did manage to report a number of issues we would need to address on order to migrate this applications, e.g. TCP Ports, Protocols, Single Application Pool and Site Content Size, however the migration tool is now non-responsive and consuming 20% CPU & 5Gb RAM

Happy to send any further information you require.

Best wishes,

Mike

[krolson]

Hello Mike,

Thank you for reaching out about this behavior.

It seems like the discovery took a long time, which can happen with certain types of configurations, like very broad/deeply nested site content or location paths, and this may thus be running into a callback timeout limit with the GUI and getting stuck. This is likely not something we can work around with the current tool and unfortunately there's no plan for an update at this time even if we identified a product change that would help.

However, it may work to use the migration PowerShell scripts Get-SiteReadiness to try to evaluate the site(s) on this server instead, which will run similar checks and save the results as a .json file, but which is less likely to have a timeout issue as all steps are completed locally on the machine and with less wrappers around them.

More information on the scripts option: https://github.com/Azure/App-Service-Migration-Assistant/wiki/PowerShell-Scripts

Would that work for you?

Thanks,
Kristina