Lỗi http error 500.19 internal server error năm 2024
Khi cài đặt Site trong IIS bạn có thể gặp trường hợp HTTP Error 500.19 – Internal Server Error với Error code 0x80070021. Lỗi này xảy ra khi bạn chưa cài đặt đầy đủ các thành phần biên dịch ASP.NET cho IIS Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. HTTP Error 500.19 - internal server error when you open an IIS Webpage
In this articleThis article resolves a problem in which you receive an "HTTP 500.19" error message on a web application in Internet Information Services (IIS) 7.0 and later versions. Original product version: Internet Information Services 7.0 and later versions Original KB number: 942055 To resolve this error, check the following sections for the appropriate error code information. HRESULT code 0x8007000dError message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x8007000d Description of HRESULT The requested page cannot be accessed because the related configuration data for the page is invalid. Cause This problem occurs because the ApplicationHost.config or Web.config file contains a malformed or unidentified XML element. IIS can't identify the XML elements of the modules that are not installed. For example, IIS URL Rewrite module. Resolution Use one of the following methods:
HRESULT code 0x80070021Error message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x80070021 Description of HRESULT The requested page cannot be accessed because the related configuration data for the page is invalid. Cause This problem can occur if the specified portion of the IIS configuration file is locked at a higher configuration level. Resolution Unlock the specified section, or don't use it at the higher level. For more information about configuration locking, see How to Use Locking in IIS 7.0 Configuration. HRESULT code 0x80070005Error message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x80070005 Description of HRESULT The requested page cannot be accessed because the related configuration data for the page is invalid. Cause This problem occurs for one of the following reasons:
Resolution Use one of the following methods:
HRESULT code 0x800700b7Error message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x800700b7 Description of HResult The requested page cannot be accessed because the related configuration data for the page is invalid. Cause This problem may occur if there's a duplicate entry for the specified configuration section setting at a higher level in the configuration hierarchy (for example, ApplicationHost.config or Web.config file in a parent site or folder). The error message itself points out the location of the duplicate entries. Resolution Examine the specified configuration file, and compare it with its parent ApplicationHost.config or Web.config file to check for duplicate entries, as suggested by the error message. Either remove the duplicate entry, or make the entry unique. For example, this problem may occur because the ApplicationHost.config file has a duplicate entry for the following code:
To resolve this problem, delete the duplicate entry in the ApplicationHost.config file for the authorization rule. To do it, follow these steps:
HRESULT code 0x8007007eError message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x8007007e Description of HResult The requested page cannot be accessed because the related configuration data for the page is invalid. Cause This problem occurs because the ApplicationHost.config or Web.config file references a module or a DLL that is invalid or doesn't exist. Resolution In the ApplicationHost.config or Web.config file, locate the module reference or the DLL reference that is invalid, and then fix the reference. To determine which module reference is incorrect, enable Failed Request Tracing, and then reproduce the problem. HRESULT code 0x800700c1Error message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x800700c1 Description of HRESULT The requested page cannot be accessed because the related configuration data for the page is invalid. Cause This problem can occur if the bitness of the specified module is different than that of the application pool hosting the application. For example, you're trying to load a 32-bit component into a 64-bit application pool. This problem may also occur if the specified module is corrupted. Resolution Make sure that the specified module's bitness is the same as that of the hosting application pool. Also, make sure that the module is not corrupted. HRESULT code 0x8007010bError message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x8007010b Description of HRESULT The requested page cannot be accessed because the related configuration data for the page is invalid. Cause This problem can occur if the specified content directory cannot be accessed. Resolution
If you aren't sure what the file path is, use the Process Monitor or Failed Request Tracing tool to identify it. HRESULT code 0x8007052eError message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x8007052e Description of HRESULT The requested page cannot be accessed because the related configuration data for the page is invalid. Cause The default process identity in IIS doesn't have sufficient permissions to open the Web.config file on a remote share. Resolution Verify that the application pool identity account of this web application has sufficient permissions to open the Web.config file. HRESULT code 0x80070003Error message: Server Error in Application "application name" HTTP Error 500.19 – Internal Server Error HRESULT: 0x80070003 Description of HRESULT Cannot read configuration file. Cause This error is caused by a lack of permission or by a physical path that doesn't match the path for the virtual directory. For example, no Web.config exists under the web app physical root path. Resolution
Fix break IIS configuration file issue when you update windowsAs a general safety rule, all configuration files (not limited to IIS) should be backup before installing any update. If you use Virtual Machines, take a snapshot of the Virtual Machine before you update it. This advice isn’t limited to Windows updates. |