Skip to content

How to debug HTTP error 500.19 internal server error?

  • by
  • 5 min read

Web apps running on Internet Information Services, otherwise known as IIS 7.0 or later versions, can at times run into an HTTP 500.19 error. In this article, we’re looking at 10 different HRESULT codes this error produces and what you can do to fix them.

HRESULT Code 0x8007000d

The error code is caused by either the ApplicationHost.config or Web config file having malformed or unidentified XML elements. IIS won’t be able to identify these elements as they might be installed.


You can try out either of the two methods to fix this problem.

  • Delete the malformed XML elements from the ApplicationHost.config or Web config files.
  • Identify the malformed XML elements and install the relevant IIS modules.

Also read: What is the Redo shortcut for Windows and Mac?

HRESULT Code 0x80070021

This error code is triggered if a specific portion of the IIS configuration file is locked for a higher configuration level.


You’re going to either have to unlock the section in question or don’t use the section at a higher level than its clearance.

HRESULT Code 0x80070005

The error is triggered by either of the two reasons.

  • If you’re using IIS on a computer that’s running Windows or you’ve configured the web app or website to use UNC (Universal Naming Convention) pass-through authentication to access remote UNC share.
  • The IIS_IUSRS group doesn’t have the permissions required to access or modify the ApplicationHost.config or the Web config files on either the virtual or application directories of IIS.


You can go through either of the following solutions.

  • Instead of configuring the website to use UNC pass-through authentication, specify an account that has the permissions required to access the remote UNC share.
  • Grant read permissions to the IIS_IUSRS group for the ApplicationHost.config file, the Web config file, or the virtual or application directories of IIS. Follow these steps to do so.

Step 1: Locate the folder that contains the ApplicationHost.config file for your site or locate the virtual directories or the application directories that contain the Web config file. Right-click either of them and click Properties.

Step 2; Head over to the Security tab and click Edit. 

Step 3: Click Add and under Enter the object names to select type <computer’s name>\IIS_users. 

Step 4: Once you’re done, click on Check Names followed by OK.

Step 5: Check the Read checkbox and click OK.

HRESULT Code 0x800700b7

The error code is triggered if there’s a duplicate entry for your configuration settings at a higher level in the configuration hierarchy. The error itself points out the location of said duplicate entries.


Check the configuration file pointed out by the error, compare it with the corresponding parent ApplicatiionHost.config or Web config files and either remove the duplicate entry or make it unique.

Also read: Best Nvidia Control Panel settings

HRESULT Code 0x8007007e

The problem is caused by the ApplicationHost.config or the Web config file referring to a module or DLL that either doesn’t exist or is corrupt or invalid. 


Locate the module or DLL reference in the specified files and either fix the reference or install the module. You can use the Failed Request Tracing feature to reproduce the problem and determine which module reference is incorrect. 

HRESULT Code 0x800700c1

If a specified module’s bitness is different from that of the application pool hosting the web app or website, this error gets triggered. 


Ensure that the application pool hosting the app or site has the same bitness as all the modules you’re using. Checking that the module isn’t corrupted is also a good idea.

This should fix the HTTP error 500.19 internal server error.

HRESULT Code 0x8007010b

The error is caused when the specified content directory can’t be accessed. 


Try the following fixes.

  • Verify that the file path exists and is referenced correctly. 
  • Verify file path naming.
  • Verify file path file-level permission set. 
  • Verify that the file path is pointing to a valid file system. 

You can use the Process Monitor or the Failed Request Timing tool to trace the file path. 

Also read: How to change the priority of a process in Windows 10?

HRESULT Code 0x8007052e

The error is caused by the default process identity in IIS not having the required permissions to access the Web config file over a remote share. 


Verify the application pool identity account for the web app or website in question and give it the permissions required to access the Web config file. 

HRESULT Code 0x80070003

The error is triggered by a mismatch in the permission or physical path and the part for the virtual directory. 


Verify that the Web config path exists and has the appropriate permissions. You can use the Process Monitor’s logs to get more information on the error and help narrow the actual problem down. 

This should resolve the HTTP error 500.19 internal server error.

HTTP Error 500.19 Internal Server Error when launching the App-V Management console

This error is caused by incorrect NTFS permissions on the drive hosting your App-V 5.0 Management Service INSTALLDIR directory. 


You need to give the local computer Users group the permissions to read and execute, list folder contents and read for the root of the drive that hosts the INSTALLDIR directory. You can find the INSTALLDIR parameter by referencing the following registry key.


Once the permissions are updated, either restart the App-V Management Service website in IIS or issue an IISRESET.

Also read: How to fix File System Error in Windows 10?

Yadullah Abidi

Yadullah Abidi

Yadullah is a Computer Science graduate who writes/edits/shoots/codes all things cybersecurity, gaming, and tech hardware. When he's not, he streams himself racing virtual cars. He's been writing and reporting on tech and cybersecurity with websites like Candid.Technology and MakeUseOf since 2018. You can contact him here: