Hi there,
Thanks for getting back to me. I followed the article I referred to which included the ignore section and enabling the ISAPI extension.
When you say "correct machine.config" file, is there a choice, as the article only mentioned one specific file?
Also, the article didn't mention using windows setup to enable ISAPI extension support. Where is this? Surely ISAPI support is already enabled to allow the ISAPI for framework v2.0?
One further thing: Other applications which are set to use a different (v2.0) app pool are also throwing the same error.
More detail on the error...............................
Detailed Error Information
| Module |
IIS Web Core |
| Notification |
Unknown |
| Handler |
StaticFile |
| Error Code |
0x8007007f |
Most likely causes:
- The ISAPI Filter has dependencies that are not available on the Web server.
- IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
- IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
- IIS was not able to process configuration for the Web site or application.
- The authenticated user does not have permission to use this DLL.
Things you can try:
- Try running Reskit tool "depends" on the ISAPI DLL.
- Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
- Check the event logs to see if any additional information was logged.
- Verify the permissions for the DLL.
- Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests