Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

After moving an IIS 6 / .Net 2 app to IIS 7.5 - it seems that after I update the website then stop/start IIS it takes forever (almost an hour) for IIS to start serving content again. I've tried various methods of stopping/starting IIS as well as IISreset /noforce but nothing works. Even after a reboot the website just spins. Then after a while it just start working again.

The trick is that this only happens on servers in one environment. All others work fine and respond immediately after a app pool recycle is issued.

Any tips / suggestions as to where I could look to find a difference or cause???

share|improve this question
1  
Have you used procmon from systinternals to monitor what is being accessed by the server during this spinning-of-wheels phase? –  Bart Silverstrim Jun 25 '12 at 15:28
    
Does anything in the application rely on a DNS lookup? –  Bart Silverstrim Jun 25 '12 at 15:29
    
No, nothing in DNS but I will certainly check just in case. –  af-at-work Jun 25 '12 at 15:34
    
Grabbing procmon now. –  af-at-work Jun 25 '12 at 15:35
    
sysinternals tools are a definite recommended addition to the toolkit. Even if they don't help here, they often come in handy for troubleshooting other issues. –  Bart Silverstrim Jun 25 '12 at 15:36

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.