500.19 error with IIS7.5

Question

I am getting the following error, even after I unlock my website. Any reasons?

HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid.

Module         CustomErrorModule
Notification   SendResponse
Handler        StaticFile
Error Code     0x80070021
Config Error   Lock violation
Config File    \\?\C:\Web\En\web.config

<validation validateIntegratedModeConfiguration="false"/>
<httpErrors errorMode="DetailedLocalOnly" defaultPath="/Oops.aspx" defaultResponseMode="ExecuteURL">
<clear></clear>

I have done the following in applicationHost.config

<location path="mysite.net" overrideMode="Allow">
    <system.webServer>
        <handlers />
        <httpErrors />
    </system.webServer>
</location>

score 12 · Answer 1 · answered May 04 '12 at 15:49

12

I had a similar Lock violation error due to defaultPath. The following fixed it for me:

The only thing that it works is to go and remove manually "defaultPath" from "lockAttributes" attribute of xml node in the file %windir%\System32\inetsrv\config\applicationHost.config

You'll have to decide for yourself whether editing applicationHost.config is too dirty.

answered May 04 '12 at 15:49

Ben Challenor

3,365
1
35
35

1

This solved the problem for me. Mysteriously, while troubleshooting this on our dev/staging servers, and editing web.config on my local copy, this actually got *added* to my local copy of applicationhost.config (used by IIS Express) and the problem started appearing when debugging in Visual Studio. You can get to the local applicationhost.config from the IIS Express tray icon. – Mike Strother Jun 24 '14 at 15:44
Also; on the web server you must use notepad to make the edits. – Mike Strother Jun 24 '14 at 15:51

score 4 · Answer 2 · answered May 05 '13 at 06:17

4

I edited the applicationHost.config but was still getting the error.

Completely forgot that after you edit applicationHost.config, you have to restart IIS.

answered May 05 '13 at 06:17

frattaro

3,241
1
16
10

score 3 · Answer 3 · edited May 23 '17 at 12:17

3

As per my answer to this similar issue;

Try unlocking the relevant IIS configuration settings at server level, as follows:

Open IIS Manager
Select the server in the Connections pane
Open Configuration Editor in the main pane
In the Sections drop down, select the section to unlock, e.g. system.webServer > defaultPath
Click Unlock Attribute in the right pane
Repeat for any other settings which you need to unlock
Restart IIS (optional) - Select the server in the Conncetions pane, click Restart in the Actions pane

edited May 23 '17 at 12:17

Community

1
1

answered Sep 06 '14 at 08:18

Chris

3,210
1
33
35

@AtLeastTheresToast are you able to elaborate on why it doesn't work on IIS 10 (I've not tested) and are you able to suggest an alternative solution for those on IIS 10? – Chris May 11 '18 at 20:10

score 1 · Answer 4 · edited Apr 11 '19 at 21:49

1

I solved problem by doing this:

Click "Start button"
In the search box, enter "Turn windows features on or off"
In the features window, Click: "Internet Information Services"
Click: "World Wide Web Services"
Click: "Application Development Features"
Check (enable) the features. I checked all but CGI.

edited Apr 11 '19 at 21:49

JJJ

1,009
6
19
31

answered Apr 11 '19 at 21:19

Ege

138
1
14

score 1 · Answer 5 · answered Jun 17 '11 at 19:40

I encountered this before and it had something to do with a security setup. Check the web application folder permissions and make sure the following users and groups are included "ASPNET", "IIS_IUSRS", "IUSR".

Don't know if this will work for you or not, but worth a try I suppose.

score 0 · Answer 6 · answered Jul 17 '18 at 05:54

I got this message after sharing my folder with a coworker. The folder had a lock on it (in Windows explorer). I had to release the lock (by granting a permission to all authenticated users, for further instructions view https://www.howtogeek.com/howto/17117/remove-the-lock-icon-from-a-folder-in-windows-7/). Once the lock has been removed, the error disappeared.

500.19 error with IIS7.5

6 Answers6

Linked