Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

IIS error 500.19 – Different causes and fixes

by | Feb 2, 2021

IIS error 500.19 occurs to a website that is hosted in Windows using IIS.

This occurs due to the permission of the document root or due to the ASP.NET.

At Bobcares, we often receive requests to fix IIS related errors as part of our Server Management Services.

Today, let’s analyze IIS error 500.19 and see how our Support Engineers fix it for our customers.

What causes IIS error 500.19

The IIS error 500.19 causes due to a number of reasons. Some of the top reasons that our Support Engineers have noticed so far include:

  • Permission of Application pool user
  • ASP.NET version
  • Missing ASP.NET version

Let us now look at the solutions for each case one by one.

How to fix IIS error 500.19

Recently we had a customer who was facing an ‘IIS error 500.19’. On analyzing the error, the permission for the IIS user to document root of the website was changed. Now let us discuss how our Support Engineers give the application pool user permission.


Permission for an application pool user

First, we verify the permission of the IIS user for the document root. Then we give the necessary permissions to the domain’s web folders.

If the Plesk panel is available we can change the permission from the panel.

Login to Plesk >> File manager >> Select home directory >> Click change permission.

IIS error 500.19

Finally, we select the required permission and click Apply.


ASP.NET version

Another reason for this error could be the ASP.NET version. If the latest ASP.NET version is not supported by the website then the error occurs. The reason is that when we install the latest ASP.NET version on the server sometimes the default version changes to the new version. Therefore, to resolve the error our Support Engineers change the ASP.NET version. Here is how we do it.

  • Start >> Administrative Tools >> Internet Information Services (IIS) Manager >> Application pool
  • Then we select the domain’s application pool and right-click on it.
  • After that, we click on the advanced setting, and from the drop-down, we change the ASP.NET version.

If the Plesk panel is available then we can change the version from the panel.

  • Login to Plesk >> Hosting setting.
  • From the drop-down Microsoft ASP.NET Support change the version.


ASP.NET feature missing

If the feature for ASP.NET not added during installation the error will occur. Here are the steps how we enable the feature.

  • First, we open server manager and then expand roles.
  • Now, we click on the webserver. Then under the Role Services section, we click on Add Role service. After that, we check the box for ASP.NET.
  • Then we click next. Finally, we click install.

[Need any further assistance in fixing IIS errors? – We’d be happy to help you]



Today, we discussed how our Support Engineers resolve IIS error 500.19. To fix the error, we verify the user permissions and make sure the ASP.NET version is right.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.