Avoiding “Lock violation” message when configuring IIS 7.x

This article describes how to solve an issue with a “Lock violation” error when configuring the site for custom extensions or extension-less URLs on IIS 7 and later.
When configuring your IIS 7 (or later) to allow custom extensions/extension-less URLs according to the Developer’s Guide instructions, especially if you’re running Kentico CMS in a virtual directory, you may receive a “Lock violation” error message which doesn’t allow you to specify the path settings in step 4. of the instructions – “Enter the following values: …”

The reason is most probably a locked defaultPath attribute for the httpErrors section. You can check and unlock it in IIS Manager. Select your site (IIS site) and open Configuration Editor and from the Section dropdown list, select system.webServer/httpErrors.

If there is a lock icon next to the defaultPath attribute name, right-click on the attribute name, select ‘defaultPath’ attribute from the context menu and choose Unlock Attribute action from submenu. Click Apply to save the changes and from now, the “Lock violation” error shouldn’t appear, so you can finish the extension-less URLs configuration procedure.


See also: Configuration Locking Lock violation on IIS7

Applies to: Kentico CMS 4.x, 5.x, 6.x, 7.x
Share this article on   LinkedIn

Juraj Ondrus

Hi, I am the Technical support leader at Kentico. I'm here to help you use Kentico and get as much as possible out of it.