I have a similar question to this one;
The requested content appears to be script and will not be served by the static file handler. ... Most likely causes:
Q) "Sort of"?
A) Yes, sort of.Now the site only works when the (new) app pool is set to \[code\].Net 4.0\[/code\], \[code\]Integrated\[/code\],
and the site's Authentication has \[code\]ASP.NET Impersonation\[/code\] set to \[code\]Disabled\[/code\].Any change to these settings sets the server yelping "404.17" all over again.Q) What's wrong with that?
A) What's wrong with that is that I NEED ASP.NET Impersonation for the site to function properly.As always, your guidance is most needed.
- IIS 7.5
- Server 2008
- ASP.Net 4.0 web site
The requested content appears to be script and will not be served by the static file handler. ... Most likely causes:
- The request matched a wildcard mime map. The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different hander.
- Reinstalling .Net
- Reinstalling IIS
- Reinstalling anything
- Running aspnet_regiis
- Republishing the site
- Restarting the application pool
- Changing the application pool to .Net 2.0 and back to .Net 4.0
- Switching around between Integrated and Classic pipeline mode
- Enabling 32-bit mode
- Taking a look at Handler Mappings
Q) "Sort of"?
A) Yes, sort of.Now the site only works when the (new) app pool is set to \[code\].Net 4.0\[/code\], \[code\]Integrated\[/code\],
and the site's Authentication has \[code\]ASP.NET Impersonation\[/code\] set to \[code\]Disabled\[/code\].Any change to these settings sets the server yelping "404.17" all over again.Q) What's wrong with that?
A) What's wrong with that is that I NEED ASP.NET Impersonation for the site to function properly.As always, your guidance is most needed.