Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I acknowledge that you have already said that you have tried changing your app pool settings. However, you didn't say <em>which</em> settings you tried.</p> <p>I generally touch the following whenever I set up an IIS Site:</p> <ul> <li>.NET Framework Version</li> <li>Enable 32-bit applications (I frequently to work with managed dlls that are 32-bit only)</li> <li>Managed Pipeline Mode</li> <li>Identity</li> </ul> <p>Double check/play with the values you have for these settings under IIS.</p> <p>Another thing worth checking is your sessionState element in your web.config. In my experience an incorrectly configured sessionState gives a google-able error, but it is plausible to me that there could be something going on with session persistence that hasn't been fully persisted into your website.</p> <p>Also consider your impersonation. Again: In my experience an incorrect impersonation will error quickly. But if you're using a domain account then it seems plausible that this could be failing to resolve and causing your app pool to hang.</p> <p>How are you deploying to IIS? Are you dumping your source code into IIS, or are you compiling and publishing a Web Application? Whichever of the two you are trying, consider trying the other.</p> <p>Are you putting up a release build or a debug build of your web application? Whichever you're trying that is in error, give the other a try and see if that works.</p> <p>Be mindful of security here: Test giving your app pool an administrator identity. This is a bad solution in the long run, but if your website works when running under an administrator account then this would narrow down your problem area to being permissions related.</p> <p>That's all I can think of to try given the information presented so far. Can you think of anything else that might be relevant?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload