Fred Mastropasqua

Yeah this one got me.. http://learn.iis.net/page.aspx/624/application-pool-identities/

The change microsoft made to have AppPool now run as “ApplicationPoolIdentity” instead of Network service.

So if you normally give Network Service rights needed to your webapp, you now have to stop doing that and change it to

IIS AppPool\DefaultAppPool

Or

IIS AppPool\<NAME OF YOUR APPPOOL>

End of that.

1. Open Windows Explorer
2. Select a file or directory.
3. Right click the file and select "Properties"
4. Select the "Security" tab
5. Click the "Edit" and then "Add" button
6. Click the "Locations" button and make sure you select your machine.
7. Enter "IIS AppPool\DefaultAppPool" in the "Enter the object names to select:" text box.
8. Click the "Check Names" button and click "OK".

By doing this the file or directory you selected will now also allow the "DefaultAppPool" identity access.

IIS And Hosting, Troubleshooting, ASP.NET, .Net Framework, Operating Systems IIS7, application pool, asp.net

So you’re getting IIS error’s when trying to run a .svc file that’s coded to use WCF or Windows Communication Foundation.

HTTP Error 404.17 - Not Found

The requested content appears to be script and will not be served by the static file handler.

or maybe..

HTTP Error 404.3 - Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

Took me awhile to realize I need to setup/configure IIS and WCF properly.  Here are the steps from MS, I went through and realized I had missed one component (IIS6 Scripting tools, who would have thought), which I probably didn’t need, but the big ones that I didn’t have WCF Http Activation installed.  After that, I registered WCF..

"%WINDIR%\Microsoft.Net\Framework\v3.5\WFServicesReg.exe" /c

and then I was golden, but there might be other things you are lacking or missing. So go through all the steps.

One-Time Set Up Procedure for the Windows Communication Foundation Samples

ASP.NET, IIS And Hosting, WCF wcf, iis7, asp.net

Well I've had this problem awhile.. where if you move over to Vista and IIS 7 you'll notice that your Debug sessions timeout very quickly, 90 seconds to be exact.

It's very annoying.  I had once went through my app pool changing every time value I found to something higher just to fix it for the moment, which is a bad idea. I usually like to know why something happens and figure how to fix it properly.

So I came across a forum article on asp.net written by jshallard.

Here is the solution for fixing your Debugging Timeout Issue:
I went with the first option, I like to debug forever

In IIS 7 go to the Application Pools and select the Advanced Settings for the pool which you process runs in. In the Process Model section you can do one of two things;
    * Set the Ping Enabled property to False. This will stop IIS checking to see if the worker process is still running and keep your process alive permanently (or until you stop your debugged process)
    * If you prefer to allow IIS to continue the monitoring process then change the Ping Maximum Response Timeout value to something larger than 90 seconds (default value).

Operating Systems, Troubleshooting, Visual Studio vista, iis7, visual studio, timeout, debug, debugging timeout