locked
IIS hang, but opening FTP restarts it... RRS feed

  • Question

  • User-2043707628 posted

    Kind of a weird one...

    I'll try to connect to my web site remotely, but it will just hang. So I'll open up FTP using WSFTP and close it. Suddenly, the webserver will start serving again.

    I've seen some of the hang posts that recommend installing the Debug Diagnostics 1.0. I tried that, but get errors about COM+ not being able to talk to MS Distributed Transaction Coordinator. How can I reinstall that anyway?

    Any help with both issues (server hang and MDTC install) would be appreciated.

    --G. George 

    Monday, October 16, 2006 2:47 PM

All replies

  • User989702501 posted

    Mmm.. you on XP Pro? If yes, see this blog post.
    first, fix the msdtc.. then com+....
    http://msmvps.com/blogs/bernard/archive/2005/03/22/39216.aspx

     

    Tuesday, October 17, 2006 12:26 AM
  • User-2043707628 posted

    Thanks.

    I'm on Windows 2003, IIS 6. I fixed the MSDTC by resetting the logs for it. I'm running the Debug Diagnostics now, but it's not telling me anything. And it's done this several times since. It always works locally, just not thorugh the internet.

    Tuesday, October 17, 2006 7:38 AM
  • User-2043707628 posted
    I'm using FrontPage to FTP my pages to the site. Seems like whenever I do that (or use FTP in any form), the site freezes up until I FTP to it again. Almost like it's not closing properly or something...
    Tuesday, October 17, 2006 11:29 AM
  • User989702501 posted

    Tough.... without error msgs. is there anything in event log?
    Forget ftp - when IIS hang, I'm sure DebugDiag will capture some log information, it is now doing so? what rules do you configured?

    what you said hang. no page is served by IIS ? not even html?

     

    Tuesday, October 17, 2006 10:40 PM
  • User-2043707628 posted

    Tough.... without error msgs. is there anything in event log?

    Well, I connected to the web sites just fine at 8AM this morning. Tried again about 8:50 and it was hung up. So I did my FTP trick to jolt it back to working and checked the Event Viewer. There's no errors or warnings that appeared in that range of time.

    The only thing that IS in there is this warning in the System Events:

    Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.xxxxx.local.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). 

    Possible causes of failure include: 
    - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers
    - Specified preferred and alternate DNS servers are not running
    - DNS server(s) primary for the records to be registered is not running
    - Preferred or alternate DNS servers are configured with wrong root hints
    - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration 

    USER ACTION 
    Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt or by restarting Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Then theres this error:

    FTP Server could not create a client worker thread for user at host xx.xx.xx.xx.  The connection to this user is terminated.  The data is the error.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    But I think that just blocking this IP address from connecting to my FTP, since I've limited usage to my home IP address only.

    Anyway, both of these messages happened before 8AM, when the server was still working. So, I don't think they have anything to do with it.

    Forget ftp - when IIS hang, I'm sure DebugDiag will capture some log information, it is now doing so? what rules do you configured?

    It wasn't running for this latest freeze up, but I didn't see anything from it yesterday when it was running and I had a couple of freeze ups.

    I just have the hang rule running, checking my websites (localhost and a few domains.) 

    what you said hang. no page is served by IIS ? not even html?

    Right. Nothing. But a quick login to FTP will jolt it back to working again... 

    Wednesday, October 18, 2006 9:10 AM
  • User989702501 posted

    Wow! interesting. ok - ftp error. try
    Event ID 8 When Clients Try to Access IIS FTP Site
    http://support.microsoft.com/?id=293637

     Next, for web. are you saying when the problem happen, you can't browse http://localhost/hello.html test page at the machine itself? IE just keep spining and eventually timeout?

    can you post the iis log file during this period and after you have relogin to ftp and it works again.?

     

     

    Thursday, October 19, 2006 1:22 AM
  • User-2043707628 posted
    Wow! interesting. ok - ftp error. try

    Event ID 8 When Clients Try to Access IIS FTP Site
    http://support.microsoft.com/?id=293637

    I'll look into that, thanks.

    Next, for web. are you saying when the problem happen, you can't browse http://localhost/hello.html test page at the machine itself? IE just keep spining and eventually timeout?

    I'm pretty sure everything still works locally, no matter what. I was browsing my site at the office and it was fine, but someone outside the network said it was locked up at the same time.

    can you post the iis log file during this period and after you have relogin to ftp and it works again.?

    Sure. What log file are you talking about? The usage log is very dense though. Even for that short period of time yesterday between 8AM and 8:50 when I knew it had locked up.

    Thursday, October 19, 2006 8:44 AM
  • User-2043707628 posted

    Well, shoot. I thought it was fixed when I changed the connections from 5000 to unlimited... It seemed to work for about 24 hours, then last night it started locking up again. Bad. This morning it's locked up at least 3 times. I'm not seeing anything in the logs. Could it be my ISP? But wouldn't FTP stop working too?

    I'm ready to stick my head in the frickin' oven... 

    Friday, October 20, 2006 2:04 PM
  • User989702501 posted

    that would be IIS log files - default path %windir%/system32/logfiles/w3svcX, where X is the site id. Only post some entries before and after the hang event.

    No clue what's going on... you see nothing in event log? I mean related to w3svc ?  As for your ISP, not so sure but ftp and http uses different port.

    Thursday, October 26, 2006 2:01 AM
  • User-2043707628 posted

    Ok, I'm pretty sure I've figured this out. And I feel like a dunce to even mention it... There were two gateways set up. One that went to the internet, and another that went to a router somewhere else on the network (that wasn't directly connected to the internet.) I think it would bounce packets between them and essentially lock up. And logging into FTP would spike it back.

    Anyway, I hope this helps someone else who might have done a dunce-like move. ;-)
     

    Monday, October 30, 2006 9:57 AM
  • User989702501 posted

    Ohhhh eeeeeeeeee aarghhhhhhh zzzzzzzzzzzz...

    Mmmm...... why does loggin to ftp spike it back?  blur :)

    Tuesday, October 31, 2006 1:49 AM
  • User-2043707628 posted

    Mmmm...... why does loggin to ftp spike it back?  blur :)

    I have no idea. But it's been 100% perfect ever since I fixed that.

    Sunday, November 5, 2006 11:34 PM
  • User989702501 posted

    :)  Glad you fixed it.

    Tuesday, November 7, 2006 4:33 AM