The tool hangs while migrating

[viveksundararaj]

Investigative information

• UTC Timestamp: September 5, 2021 11:10:00 AM
• Migration Tool App version : 1.0.6.20061101
• OS Version: Windows Server 2016

Repro steps

Just run the Azure App Service Migration Assistant Tool. During the assessment, the tool found 2 gave 2 warnings only.

Expected behavior

An Azure WebApp must be provisioned and the content of the on premise website must be moved to Azure WebApp.

Actual behavior

A new Azure WebApp is being provisioned but the content of the on premise website is not being moved to Azure WebApp. The tool hangs during the migration of web content and a blank screen appears.

[krolson]

Hi @viveksundararaj, thank you for letting us know about this. This sounds like an issue that was fixed in the currently available Preview version of the tool. Would you be willing to try that version and let us know if that works? It would be the "App Service migration assistant for Java on Apache Tomcat (Windows—preview)" on https://azure.microsoft.com/en-us/services/app-service/migration-assistant/ - this includes the IIS app migration experience in addition to the Preview TOMCAT app option.

If that doesn't resolve the issue, would you be willing to share a detail like the site name you used for the migration so we could try to associate backend logs for the particular site migration and see if we can tell what happened from that? You could even create a "throwaway" site just for the migration attempt.

[padevadi]

@krolson , we almost facing a similar issue after the above migration in progress wizard, it turns to a blank screen, we don't see a message about migration completion, and when we access the target azure web app with a private endpoint or public URL site is not up. Do you suggest us to use the above preview PowerShell way to try migration? does the PowerShell script modify any config on the source IIS server or involve any downtime on the source IIS site

[viveksundararaj]

@krolson , we almost facing a similar issue after the above migration in progress wizard, it turns to a blank screen, we don't see a message about migration completion, and when we access the target azure web app with a private endpoint or public URL site is not up. Do you suggest us to use the above preview PowerShell way to try migration? does the PowerShell script modify any config on the source IIS server or involve any downtime on the source IIS site

@padevadi, I would advise you to try the suggestion of Krolson. The preview version (App Service migration assistant for Java on Apache Tomcat (Windows—preview) did work out on my case.

[padevadi]

Thanks, @viveksundararaj . But when I am running Generate-MigrationSettings.ps1, I am receiving the below error message Site package results file: Exception of type 'System.OutOfMemoryException' was thrown

I did upgrade the mem on the server from which I am running the script as well as upgraded the pagefile

[krolson]

Hi @padevadi - thanks for the comments here!

We haven't seen that particular error for the Generate-MigrationSettings.ps1 before - couple questions/thoughts/options:

• Was the package results file passed in for SitePackageResultsPath created on the same server or another server?
• Based on the above message, I am guessing the error is happening on the below step - can you try running this PS command outside of the script and see what happens? (either set $SitePackageResultsPath = "" first or replace the $SitePackageResultsPath value directly in below command): $PackageResults = Get-Content $SitePackageResultsPath -ErrorAction Stop | ConvertFrom-Json
• Does the package results file happen to be large...? If it is for many sites, you could make a copy and remove all the packages except the one you're interested in and see that makes a difference (and please let us know the file size / number of sites that are in the file when it didn't work)
• Workaround option for this script: this generate settings script is also optional - as a workaround you could also manually modify the TemplateMigrationSettings.json to create the settings file (the settings will get validated when you run Invoke-SiteMigration).

[padevadi]

@krolson, I copied the package zip and json output to another system and executed the invoke migration step from that system. Migration is successfull now.