Hi - thanks for the comments.
I have seen nothing at all related to HTTP in the event logs. No
errors at all; a few warnings, all of which were corrected over time,
but again, nothing at all to do with IIS.
The default connection timeout is 120 seconds; in past incarnations of
these web sites, that has been sufficient.
The default database port (1433) is open and active, but blocked from
the Internet via Windows Firewall.
I loaded perfmon and tracked access for the past 24 hours; peak load
is less than 2600 connections per hour (if I am reading that
correctly...)
Still no logs created. Very frustrating. I've checked and rechecked
permissions on the file systems, but all is well there. Indeed, 3
sites are happily creating usable logs. Naturally, they are not the
sites I am having trouble with. I see no difference in their
properties over the other sites that are not creating logs. Of the 3
that are logging, 1 is a pure .Net application, the other two are
older ASP style. Every site on the server relies on the same database
instance for authentication and data.
Very confused. Thank you all for any input.
Rick
On Feb 1, 5:53 am, ASHOK <AS....TakeThisOut@discussions.microsoft.com> wrote:
> hi,
> will you write something more about your problem. For upgraded of all your
> system" congratulation ".
> So you have new IIS6 now .what I think there is not any issue with IIS
> internally ( IIS engine).
> Please check your IIS connection time out setting (default which 120 sec)
> .2nd see the extended log configuration . see also that default 1433 port is
> open or not towards your database server.
> 3rd be sure using "perfmon" that how many connection are coming to your web
> server. check current connection and anonymous connection also.
>
> Thanks
> Ashok -Kumar
>
>
>
> "rirel...@gmail.com" wrote:
> > Hi!
> > Upgraded our web server to IIS 6 (from IIS 5) and MS/SQL 2005 (from
> > 2000). Having timeout issues under nominal load. Leaning towards
> > SQL, but I need the IIS logs to pinpoint the activity.
>
> > I turned on logging, per documentation and the various dialog boxes -
> > but only 3 out of the 11 sites I host are creating logs. The other 8
> > - the ones with the application issues - do not create logs of any
> > format in any directory regardless of how often I change the settings,
> > bounce the site, or scream and cry.
>
> > Customers angry, CEO panicky, developers grumpy...
>
> > Any input would be greatly appreciated. tia
>
> > Rick- Hide quoted text -
>
> - Show quoted text - >> Stay informed about: IIS 6.0 Logging Fails