IIS_IUSRS and DefaultAppPool permissions do not work

10,582

There seems to have been some kind of filesystem-level or OS-level permissions caching, because the issue appears to have resolved itself after a complete system reboot (even though restarting IIS (W3SVC) and recycling App Pools really should have resolved this).

Share:
10,582

Related videos on Youtube

Moshe Katz
Author by

Moshe Katz

#SOreadytohelp I am currently a Computer Science graduate student (Ph. D. seeking) at the University of Maryland. I do a lot of programming (primarily web application development) for small businesses and nonprofits. In school, I focus mostly on security and context-aware systems, and I have also worked on counter-terrorism applications. You can find me most days in PHP and/or C#, but increasingly in JavaScript with a focus on Rich Internet Application areas (knockout.js, durandal, breeze.js, etc) and WebRTC.

Updated on September 18, 2022

Comments

  • Moshe Katz
    Moshe Katz over 1 year

    I am setting up a PHP application on IIS 8.5 on Windows Server 2012 R2. I have successfully set up this application before on several Windows Server 2008 R2 and Windows Server 2012 machines, but this is the first 2012 R2 machine I am using.

    The PHP application has log and cache directories that it needs to write into.

    On all previous machines, I have set up the PHP site to run in the Default Application Pool, and then given permission to the IIS_IUSRS group to read the entire site and to write to those directories. So far, this has worked on all of the previous servers I have used.

    However, on this new server, PHP still says it does not have permission to write to the needed locations.

    I checked in Task Manager to be sure that the IIS process (and the PHP CGI process) run as the expected user and find that they run as DefaultAppPool, as expected. However, the permissions don't seem to have worked. I tried stopping and restarting IIS, recycling the App Pool, and adding the IIS AppPool\DefaultAppPool user permissions directly to the folders, none of which have helped.

    What is wrong here? Why does this not work when it worked with no trouble at all on four older servers?