• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Lock violation web.config telerik

fung kok ting

New Pleskian
Hi guys,

trying to deploy asp.net with telerik handler to plesk windows but face this error, working fine in azure hosting, local pc, local windows 2012 R2.

this is the exact error in the portal:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:

Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070021
Config Error Lock violation
Config File \\?\C:\Inetpub\vhosts\xxx.xxx.xxx\httpdocs\aspnet\booking\web.config
Requested URL http://xxx.xxx.xxx:80/booking/
Physical Path C:\Inetpub\vhosts\xxx.xxx.xxx\httpdocs\aspnet\booking\
Logon Method Not yet determined
Logon User Not yet determined

Config Source:
152: <!-- This is the primary handler used to fetch most of the needed resources -->
153: <add name="Telerik_Web_UI_WebResource_axd" path="Telerik.Web.UI.WebResource.axd" type="Telerik.Web.UI.WebResource, Telerik.Web.UI, Culture=neutral, Version=2017.2.503.45, PublicKeyToken=121fae78165ba3d4" verb="*" preCondition="integratedMode" lockItem="false" />
154: <!-- Only needed for RadSpell and RadEditor's spell checking -->

More Information:
This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
View more information »
 
Back
Top