Re: Problem with freezing on IIS
From: Thomas Scheiderich (tfs_at_deltanet.com)
Date: 06/16/04
- Next message: Jeff Dillon: "Re: IIS 6.0 - logging everything!"
- Previous message: FIDO: "FP + IIS"
- In reply to: Ken Schaefer: "Re: Problem with freezing on IIS"
- Next in thread: Ken Schaefer: "Re: Problem with freezing on IIS"
- Reply: Ken Schaefer: "Re: Problem with freezing on IIS"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Jun 2004 13:46:04 -0700
Found the problem. Just not sure why it is a problem, yet.
It appears that in the Virtual Directory page there is a field called
Application Protection. If we set this to Low (IIS Process), asp pages work
fine. When we had it set to Medium, it would not even process ASP pages.
Not only would it not process the pages, it would return no error pages. As
soon as we changed it to Low, if I put in a page that didn't exist (when it
was an asp page), I got a message back. If it was a higher priority, I
would get no message back for asp pages, but I would for .htm.
On my other machine, I don't have this problem. I can set it to High and it
processes the same pages just fine. It is the extension that causes the
problem. I could take a simple hello page and just change the name from
hello.htm to hello.asp, and it wouldn't process it. It would never come
back.
I don't have the problem on my other server, which is also using the default
settings (as is the problem server). I have the Application Protection to
High without any problems
I have the identical ASP settings (including asp script timeout of 90
seconds) - the problem is it never times out.
Not sure why it is happening as it is, Low will solve our problem (at least
temporarily), so we will go with that now.
Thanks,
Tom.
"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
news:eKYlVV3UEHA.712@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> Something's definately not working properly. ScriptTimeout can be set
either
> in IIS Manager, or manually in a webpage (Server.ScriptTimeout = <...>)
>
> If someone has disabled script timeout, then the scripts will run forever
if
> there's a problem (so, check that setting)
>
> If you are having logon problems, you will see errors in the server's
> Security Event Log (hence the suggestion to check the event logs).
>
> Alternatively, if something's wrong inside IIS, and you are getting 100%
CPU
> in InetInfo.exe or DllHost.exe you may also see this behaviour - ie lack
of
> response in the browser, because the server is locked up (hence the
> suggestion to check on the server to see if any process is pegged at 100%
> CPU)
>
> I don't know what IIS version you are using - but you don't need to do
> anything special per se. On IIS 6.0 you need to enable the ASP Web Server
> Extension in the IIS manager (but that's just a matter of clicking a
button)
>
> I would also go to the server, and check the IIS logfiles themselves
> (c:\windows\system32\logfiles\w3svc<siteNumber>\ and make sure the request
> is actually getting to IIS. If you have some kind of proxy server or
> something, the error might be in the proxy. You could test this by using
IE
> on the server itself, and attempting to browse to http://localhost/
>
> Cheers
> Ken
>
>
> "Thomas Scheiderich" <tfs@deltanet.com> wrote in message
> news:10cvqo9g9nmocc5@corp.supernews.com...
> : "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
> : news:epeHmW2UEHA.384@TK2MSFTNGP10.phx.gbl...
> : > Again, if this is working on one server, but not the other, then
> something
> : > is different about their configurations.
> : >
> : > a) The ScriptTimeout settings may be different
> :
> : Where would that be?
> :
> : > b) You may have impersonation problems (IIS can't logon the anonymous
> user
> : > context)
> :
> : Why would that be?
> :
> : > c) You may be using a custom error page that itself has errors
> :
> : Don't have any custome error pages. Just a normal install.
> :
> : > ...
> :
> : Looked at both servers.
> :
> : The problem seems to be connected with ASP files. Do we need to do
> : something special to run ASP? Not sure why the one will work and not
the
> : other. Can't find any clear differences.
> :
> : Thanks,
> :
> : Tom
> : > etc
> : >
> : > Have a look on the server, and see if you can see any events in the
> Event
> : > Logs. See if there are any different configuration settings for either
> of
> : > the two servers. See, using the process list, if any of the processes
> are
> : > using 100% CPU or similar.
> : >
> : > Cheers
> : > Ken
> : >
> : > "Thomas Scheiderich" <tfs@deltanet.com> wrote in message
> : > news:10cvmvsginq8fbf@corp.supernews.com...
> : > : "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
> : > : news:eXuwcA2UEHA.584@TK2MSFTNGP09.phx.gbl...
> : > : > Something must be different about the setup between the two
> machines.
> : > : >
> : > : > For example, check the connection timeout settings on the two
> : machines.
> : > : > Maybe one is set to a very short time, and one is set to a very
long
> : > time,
> : > : > and so the second server is waiting longer before throwing an
> : > exception...
> : > : >
> : > : I have it tracked down to asp files.
> : > :
> : > : For example, I have a file in contour called tom.asp which is trying
> to
> : > use
> : > : the DSN Bingo1, which of course, isn't there. It should come back
> : > : immediately telling that there is no such DSN entry (I tried it here
> and
> : > : that is what it does here). I also tried using a non-existant
page -
> : > : tom1.asp - and just like the other, just sits there forever. It
also
> : > should
> : > : come back with an error.
> : > :
> : > : When I tried to use the DSN Bingo as "DNS=Bingo;", with no
> : authorization,
> : > it
> : > : also just sits there. On our other server, it apparently works
fine.
> : > :
> : > : I am not sure what the problem is, but it is going to be tough to
get
> it
> : > up
> : > : if the web site doesn't respond.
> : > :
> : > : I have tracked it down to .asp files. If you have a .asp extension,
> it
> : > just
> : > : freezes. For example, if I take tom3.asp, which freezes and just
> change
> : > the
> : > : request to tom3asp, it comes back right way saying it doesn't exist.
> : > :
> : > : If it doesn't have a .asp extension, it works as expected - errors
and
> : > all.
> : > : If, for example, you try openworx/tom9.htm - you get an error that
> says
> : it
> : > : doesn't exist. If you use openworx/tom9.asp (also doesn't exist),
it
> : just
> : > : sits there.
> : > :
> : > : Very frustrating. I'm sure I am missing something.
> : > :
> : > : Thanks,
> : > :
> : > : Tom
> : > :
> : > : > Cheers
> : > : > Ken
> : > : >
> : > : > "Thomas Scheiderich" <tfs@deltanet.com> wrote in message
> : > : > news:10cvk065boort8f@corp.supernews.com...
> : > : > : I have 2 web servers and I have a page that is trying to open a
> DSN
> : > that
> : > : > : doesn't exist. On my one server, it comes back right away and
> tells
> : > me
> : > : > so.
> : > : > :
> : > : > : The other machine just sits there - no message. It will stay
> there
> : > with
> : > : > the
> : > : > : logo in the top right spinning.
> : > : > :
> : > : > : Why does the one server come back with an error message and the
> : other
> : > : just
> : > : > : sit there?
> : > : > :
> : > : > : Thanks,
> : > : > :
> : > : > : Tom.
> : > : > :
> : > : > :
> : > : >
> : > : >
> : > :
> : > :
> : >
> : >
> :
> :
>
>
- Next message: Jeff Dillon: "Re: IIS 6.0 - logging everything!"
- Previous message: FIDO: "FP + IIS"
- In reply to: Ken Schaefer: "Re: Problem with freezing on IIS"
- Next in thread: Ken Schaefer: "Re: Problem with freezing on IIS"
- Reply: Ken Schaefer: "Re: Problem with freezing on IIS"
- Messages sorted by: [ date ] [ thread ]