Mailing List Archive: ASP timeouts with CM 3.3(2)

and another oddity

Event Type: Warning
Event Source: Active Server Pages
Event Category: None
Event ID: 9
Date: 8/20/2003
Time: 9:50:42 AM
User: N/A
Computer: CM-1CORP
Description:
Warning: IIS log failed to write entry, Script timed out. The maximum
amount of time for a script to execute was exceeded. You can change this
limit by specifying a new value for the property Server.ScriptTimeout or
by changing the value in the IIS administration tools..
For additional information specific to this message please visit the
Microsoft Online Support site located at:
http://www.microsoft.com/contentredirect.asp.

i'm getting this fairly frequently. for fun i increased the asp timeout
value on iis (2X to 180s), but i'm still getting it. any ideas on
what/why this is occuring? i'm not much of a windowz admin and cant'
seem to figure out how to track down the offending asp page. thx for
any help

CSCeb80203
Externally found cosmetic defect: Assigned (A)
Virtual Directory shutdown generates IIS log app event warning

Symptom:

The following warning is observed repeated in the Application Log in the
Event Viewer:

Event Type: Warning
Event Source: Active Server Pages
Event Category: None
Event ID: 9
Date: 6/25/2003
Time: 12:49:42 PM
User: N/A
Computer: CM-PUBLISHER
Description:
Warning: IIS log failed to write entry, Script timed out. The maximum
amount
of time for a script to execute was exceeded. You can change this limit by
specifying a new value for the property Server.ScriptTimeout or by changing
the
value in the IIS administration tools..
For additional information specific to this message please visit the
Microsoft
Online Support site located at:
http://www.microsoft.com/contentredirect.asp.

This warning is followed by the following information message:

Event Type: Information
Event Source: Active Server Pages
Event Category: None
Event ID: 4
Date: 6/25/2003
Time: 12:49:44 PM
User: N/A
Computer: CM-PUBLISHER
Description:
Service stopped.

Conditions:

This appears 20-21 minutes after the last access to a web page.

Workaround:

There is no known workaround. However, is no noticible impact other than the
presence of this warning in the App Log.

/Wes

> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Jeff Behl
> Sent: Wednesday, August 20, 2003 1:04 PM
> To: cisco-voip@puck.nether.net
> Subject: [cisco-voip] ASP timeouts with CM 3.3(2)
>
>
> and another oddity
>
>
> Event Type: Warning
> Event Source: Active Server Pages
> Event Category: None
> Event ID: 9
> Date: 8/20/2003
> Time: 9:50:42 AM
> User: N/A
> Computer: CM-1CORP
> Description:
> Warning: IIS log failed to write entry, Script timed out. The maximum
> amount of time for a script to execute was exceeded. You can change this
> limit by specifying a new value for the property Server.ScriptTimeout or
> by changing the value in the IIS administration tools..
> For additional information specific to this message please visit the
> Microsoft Online Support site located at:
> http://www.microsoft.com/contentredirect.asp.
>
>
> i'm getting this fairly frequently. for fun i increased the asp timeout
> value on iis (2X to 180s), but i'm still getting it. any ideas on
> what/why this is occuring? i'm not much of a windowz admin and cant'
> seem to figure out how to track down the offending asp page. thx for
> any help
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip