We have a Windows 2012 server running IIS 8.5. We created an application pool and assigned its identity to a specific Windows account (a "Custom" account in the Application Pool Identity dialog box). That account was then granted permissions to see particular network shares/paths in Active Directory. Normally, we would recycle the application pool after granting new permissions to it (similar to a user logging off/on to pick up the new path permissions) and then the application pool could find files on the share to which it had been granted access.
Sometimes a recycle does not work and we have to "stop", wait a few seconds, and then "start" the app pool again. Sometimes even that will not work. Even after restarting the entire web server the app pool cannot see the new path. We end up having to remove and recreate the app pool with that same user account and then it can finally see the path it has been assigned.
I have seen this behavior on several different Windows 2012 servers running IIS 8.5 but have never seen this behavior on Windows 2008R2 running IIS 7.x.
Is there some kind of bug with IIS 8.x that it requires removing the app pool and recreating it in order for network path permissions assigned to it to "kick in"? This is very painful to handle in a production environment.
Looking forward to any thoughts/tips anyone can offer.
Thanks!