Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConfigErrorCheck received during assessment not giving useful information #81

Open
bguptaNavi opened this issue Jun 12, 2023 · 8 comments

Comments

@bguptaNavi
Copy link

We ran Azure migration assessment tool on-prem and found the following error for two of our websites. The web.cofigs are very small and straightforward. Don't see anything else standing out. Not sure what the error is.

'Details': [
  {
    'CheckPassed': false,
    'CheckName': 'ConfigErrorCheck',
    'DisplayMessage': 'The following configuration errors were found: HRESULT=8007000D, Action=parsing_configuration_file, SectionSchemaName=, AttributeName=, Message=The data is invalid. (Exception from HRESULT: 0x8007000D)\\r\\n',
    'Status': 'Block',
    'DisplayTitle': 'Configuration Errors',
    'CheckDescription': 'Checks for errors in the IIS configuration',
    'MoreInfoLink': 'https://go.microsoft.com/fwlink/?linkid=2084726',
    'logFriendlyMessage': 'The following configuration errors were found: HRESULT=8007000D, Action=parsing_configuration_file, SectionSchemaName=, AttributeName=, Message=?\\u003CException:\\u003CException0000\\u003E\\u003E'
  }
]

UTC Timestamp: Fri, 05 May 2023 18:09:09 GMT

OS Version: Windows Server 2019

web.config

@krolson
Copy link
Contributor

krolson commented Jun 13, 2023

Hi @bguptaNavi ,
If the configs are small and straightforward (and have NO sensitive information like secrets) would you be willing to share a sample for one of the sites in for trying to give additional suggestions/try to reproduce on our end? Please also double check if there are other web.configs within the site content that may be the cause of the error (web.configs could be in any directory in the site) - if you were to change the root web.config file name to something else and rerun the assessment and it still has this error, that would be an indication that the issue is coming from a web.config at another level.

This error code is coming directly from Microsoft.Web.Administration when we try to load and read the configuration, so this is a generic config error. Often this is due to issues like URL Rewrite module config being used while it's not an installed feature on the server.

Generic page about this error: https://learn.microsoft.com/en-us/troubleshoot/developer/webapps/iis/health-diagnostic-performance/http-error-500-19-webpage#hresult-code-0x8007000d

Other page about this error where some other niche reasons it popped up are noted: https://techcommunity.microsoft.com/t5/iis-support-blog/troubleshooting-http-500-19-errors-in-iis-7/ba-p/347247

@bguptaNavi
Copy link
Author

bguptaNavi commented Jun 13, 2023 via email

@krolson
Copy link
Contributor

krolson commented Jun 13, 2023

Hi @bguptaNavi - I'm afraid I am unable to see how to access the email attachments you referenced - could you please try sending the email directly to [email protected] ?

@bguptaNavi
Copy link
Author

bguptaNavi commented Jun 14, 2023 via email

@krolson
Copy link
Contributor

krolson commented Jun 14, 2023

So I am able to cause this error using the configuration files sent and the Internet Information Services (IIS) Manager UI and a machine with a fairly default IIS install - and if you navigate to the site and the folder where the configuration is located and try opening the "Configuration Editor" you should see this same error, as noted below (and I would expect the site itself to be returning a 500.19 at this config file level as well when browsing it).

Configuration Editor
There was an error while performing this operation.

Details:
The data is invalid. (Exception from HRESULT: 0x8007000D)
OK

Given the web.config contents and I suspect the issue is related to the installed modules on the server, such as aspNetCore module on the server (that it's not installed, wrong version compared to what site web.config is referencing, needs repair, etc.) - similar to in this thread: https://stackoverflow.com/questions/54984884/error-500-19-with-0x8007000d-when-running-asp-net-core-app-in-iis-despite-aspnet, and/or the httpPlatformHandler module.

I'm going to close this issue as it's separate from the migration assistant at this point (i.e. related to generic IIS configuration debugging). If you find that the inetmgr UI does not give the same error when using Configuration Editor for the config that the App Service Migration Assistant is giving an error for, please do let us know (here or in the now existing email thread you have with us).

@krolson krolson closed this as completed Jun 14, 2023
@bguptaNavi
Copy link
Author

bguptaNavi commented Jun 15, 2023 via email

@krolson krolson reopened this Jun 15, 2023
@krolson
Copy link
Contributor

krolson commented Jun 15, 2023

Hi @bguptaNavi - thanks for those details. I wonder if this has to do with some quirk of the App Service Migration Assistant being "fully packaged" and not relying on any resources on the machine (such that it's version of Microsoft.Web.Administration (MWA) may be slightly different than the version on the server and it's resulting in a behavior difference for this particular configuration pattern). One thing to try here both as a diagnostic and a potential workaround is using the PowerShell scripts Get-SiteReadiness script to see if it gives the same config error result or not. The PowerShell scripts directly use the version of MWA that's already on the server, so it would eliminate this as a potential source of the behavior mismatch between inetmgr and the Migration Assistant.

Please try this and let us know how it goes. If it works, using the scripts is a workaround option to using the Migration Assistant GUI - and either way it would be useful to us to know the specific Windows version of the server (such as in Settings under "About"/"System Properties" the "Windows specifications" information).

@bguptaNavi
Copy link
Author

bguptaNavi commented Jun 16, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants