Web.Config Lock Violation error on existing IMan installation. (5 replies)
Randy, are there any errors in the Windows event log?
Try checking the IIS IMan application pool. Is it started?
The schedules still run as they are executed/triggered from Realisable Scheduler Service.
Thanks
Support
No, there was nothing in the Windows event log.
We attempted restarting the IIS IMan App Pool a few times.
Is there any more info we can get you to help you resolve this? We are completely locked out of IMan.
Thanks
Hi Randy, could you drop me a message when you;re free, I'll need to investigate.
Nick
Nick
Somehow some of the IMan pre-reqs had become uninstalled.
After re-installing some features, IMan started working again.
Thanks
OK
All of the services are running, but we cannot log into IMan due to "Internal Server Error" - Lock Violation. IMan is set to run under a domain user who is a local administrator. We have not accessed this system in 6 months, and we know that Windows Updates were recently applied. IMan had been running scheduled jobs without issue in those 6 months.
The errors that we are seeing is:
Detailed Error Information:
Module CustomErrorModule
Notification SendResponse
Handler StaticFile
Error Code 0x80070021
Config Error Lock violation
Config File \\?\C:\inetpub\wwwroot\IMan\web.config
Requested URL http://192.168.0.30:80/IMan/Design/DesignPage.aspx
Physical Path C:\inetpub\wwwroot\IMan\Design\DesignPage.aspx
Logon Method Anonymous
Logon User Anonymous
Config Source:
213:
214:
215: