"Access to the path '...ToolboxesConfig.config' is denied", after migrating to sitefinity 4.3
I have updated our site from Sitefinity 4.0 to 4.3 and now I am receiving the following exception when I try to open the site:
Server Error in '/Some' Application.
Access to the path '(...)\App_Data\Sitefinity\Configuration\ToolboxesConfig.config' is denied.
Hello Gerardo,
We have answered you in the support ticket you opened. Can we keep our communication at one place so the information flow is better structured.
Best wishes,
Victor Velev
the Telerik team
Hi Victor,
I think that you don't like to talk about SF 4.3 bugs. I have same problems like Gerardo as you can see at my attachment and need a solution asap.
Regards Robert
Hi,
The error says that ASP.NET worker process does not have read/write permissions over App_Data and configuration files. Please grant the asp.net user account (or network service) with read/write permissions. You can do this from windows explorer if you have direct access to the server.
Greetings,
Ivan Dimitrov
the Telerik team
I got the same problem. In order to fix it, you just need to make sure that all your.config files are NOT readonly and application user has read/write permissions to \Sitefinity\Configuration folder.
Take a look at your source code management. If you're using for example TFS, you have to have the file checked out. Not sure why, as the file contents doesn't change.
and it still happens in v. 9! but they won't post the fixes publically for us to find.
Even if you give Network_Service full control, propagate to all children
and make all files in the project folder writeable.
You'll still get Access to the path 'D:\...\...\..._2016_dev\App_Data\Sitefinity\Configuration\SearchConfig.config' is denied.
I'm stuck on the initial deploy of a new project
The only way to get an SF running on a windows server is to also add to the Project folder security and all children:
EVERYONE and ISUR and grant them FULL control.
With such a non-secure requirement, no wonder they don't publish it publicly. Hope this helps the next person.
Instead of giving full control permission for EVERYONE, it is better and safer to give FULL control permission only for user IIS AppPool\<yourpoolname> only for your website folder