I have two servers (Windows Server 2008 R2), one for testing, and one for staging/production areas. My web application uses NLog library for logging.
When I create a new site on the test server and then publish web-app to it, NLog is able to log into site's '{root}\log' folder. However, when publishing to production/staging server, NLog throws exception that it can't access to '{root}\log'.
In site root folder security settings on both servers I see a 'user' named after sites' application pool name, both only have access to read this folder. But on the test server web-app is able to actually write it's log there, when on the staging/production server I have to give to that application pool's 'user' full access to the site root folder for it to be able to write its log.
Why is that difference could be? My test server has mostly default settings, but I can't know what settings could have been applied to the staging/production one.