The Template Persistent Cache initialization failed for Application Pool” AppPoolName: because of the following error: Could not create a Disk Cache Sub-directory for the Application Pool. The data may have additional error codes
Solution
Running DCpromo.exe (Making the server a domain controller) misses out some permissions on folders and you have to add them manually.
1. Navigate to c:windowsHelpiisHelpcommon > Right CLickClick Sharing and Security >
Add >type IIS_WPG > OK. Give IIS_WPG the following rights, Read and Execute + List Folder Contents + Read > apply > OK Then Add > NETWORK SERVICE > give the following rights Read and Execute + List Folder Contents + Read > apply > OK
2. Navigate to C:WINDOWSsystem32inetsrvASP Compiled Templates.
Give IIS_WPG full control Then Add > NETWORK SERVICE > give Full control > apply > OK
Later on in the year I’ve got a big RSA and SharePoint deployment, as I know ‘Zippity Squat’ about SharePoint, I thought the best way to get some hands on experience, was to work out how to integrate SecureID with Exchange 2013, (which I know a few things about!)
Solution
I’m assuming you already have RSA Authentication Manager setup and users/tokens deployed. This run though is simply to get your RSA solution working with Exchange/OWA
1. Create a user in Active Directory, (here I’m using SVC_RSA_Access), and ensure that user has a mailbox, you can do this in the Exchange Admin Center, but I prefer to use the shell.
6. We need to have the .Net 3.5 Feature added. (Server Manager > Add Roles and Features).
7. Log onto the Security Console of your RSA Authentication Manager appliance > Access > Authentication Agents > Generate Configuration File > Follow the wizard > Download the file.
8. Place the file you downloaded (sdconf.inf) on the Exchange server in the C:Windowssystem32 folder.
9. Download and install the RSA Authentication Agent for Web for IIS, Install and accept all the defaults, it should locate the config file you have just downloaded.
10. On the Exchange server launch ‘RSA Web Agent’, and don’t be surprised when IIS Manager opens.
Seen on Server 2003 running IIS 6, about once a week the website would fail, and the client had to reboot the server to bring things back up again. I took a look at the server and noticed that when the failure happened, we had five Event ID 1014 errors;
Source W3SVC
The World Wide Web Publishing Service encountered an internal error in its process management of worker process ‘<value>’ serving application pool ‘DefaultAppPool’. The data field contains the error number.
And finally we had an Event ID 1002;
Source W3SVC
Application pool ‘DefaultAppPool’ is being automatically disabled due to a series of failures in the process(es) serving that application pool
Solution
1. Before you proceed make sure this is not the problem.
2. Open the Internet Information Services (IIS) Manager > {Servername} > Application Pools > DefaultAppPool (unless your error is for another app pool) > Properties > Health.
3. Rapid-Fail Protection: You may wish to troubleshoot by simply increasing the thresholds, (the frequency of your 1002 events should give you a pointer). Though from what I’ve read this system tends to cause more problems than it cures, in the end I disabled it completely.
Warning: Disabling a system that is designed to protect you inherently has dangers.
If you suddenly get an unstable server, or memory leak problems you might want to reinstate this, and start checking the code in your website!
Related Articles, References, Credits, or External Links
