Classic ASP errors with current identity does not have write access to c:\windows\microsoft.net\framework\v4.0.30319\temporary ASP.NET files

Hi @Ramirez, Rose ,

The error does not necessarily mean the .asp files contain .NET code. If the application pool uses the Integrated pipeline, ASP.NET modules can also participate in Classic ASP requests. Microsoft documents this behavior in Application Pools in IIS.

I would suggest checking the following first:

1. Open the application pool’s Advanced Settings and note its Identity, .NET CLR Version, and Managed Pipeline Mode.
2. Check the complete error message for the identity shown in parentheses.
3. If the site is entirely Classic ASP and does not use managed modules or child ASP.NET applications, test it in a dedicated application pool with .NET CLR Version set to No Managed Code.
4. If managed processing is required, grant the identity shown in the error read and write access to the exact folder named in the message: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

C:\Windows\Temp is a separate directory, so permissions there do not address this particular error. Microsoft lists the required permissions for the ASP.NET compilation folder in ASP.NET Required Access Control Lists.

If the issue remains, please share the complete error and stack trace with sensitive details removed, along with the three application pool settings above. That should show whether unnecessary managed processing is being loaded or the actual worker identity still lacks access.

If your classic asp does not use .net, you probably configured .net pipeline which does. Edit the pool account and set the clr version to no managed code and pipeline mode to classic. Also under advanced settings enable 32 bit applications