Azure / App-Service-Migration-Assistant

Azure Websites Migration Assistant for Windows is a tool that allows customers to move their existing sites hosted on IIS servers into the cloud on Azure App Service. For more information check out https://appmigration.microsoft.com .
https://appmigration.microsoft.com
MIT License
74 stars 60 forks source link

System can not find path specified error while running App migration assistant- HRESULT: 0x80070003 #65

Closed Sachikp closed 1 year ago

Sachikp commented 2 years ago

We are not able to assess webapps in IIS version 8.5. Tool is giving "system cannot find path specified HRESULT: 0x80070003" error.

Investigative information

Please provide the following:

Repro steps

Provide the steps required to reproduce the problem:

Example:

  1. download and install App service migration assistant tool version 1.0.8 in IIS server.
  2. Run the tool

Expected behavior

Example:

Actual behavior

tool is not able to fetch webapps hosted in IIS server with error "system cannot find path specified HRESULT: 0x80070003".

Example:

due to that error we are not able to assess webapps hosted in IIS.

Known workarounds

Example: we tried to run PowerShell command (IISdiscovery) given in this link https://github.com/Azure/App-Service-Migration-Assistant/wiki/PowerShell-Scripts MicrosoftTeams-image (1) error

MicrosoftTeams-image (2)

krolson commented 2 years ago

Unfortunately this is failing on a basic call by Microsoft.Web.Administration ("MWA") to get the configurations on the server, effectively below call to GetSection. The MWA dll is shipped with IIS and is used by both the Migration Assistant GUI and the PowerShell scripts to interact with IIS.

$iisInstallPath = [System.Environment]::ExpandEnvironmentVariables("%windir%\system32\inetsrv\Microsoft.Web.Administration.dll");
        [System.Reflection.Assembly]::LoadFrom($iisInstallPath) | Out-Null; 
        $sm = New-Object Microsoft.Web.Administration.ServerManager;
        $Config = $sm.GetApplicationHostConfiguration();
        $configPathsSection = $Config.GetSection("configPaths")

My understanding is that this type of error could be caused by access issues and/or things like path-too-long (where file paths start to exceed 260 characters) - would either of these scenarios be a possible explanation on this server?

krolson commented 1 year ago

Closing due to lack of activity for over 90 days