09-18-2007 06:33 PM - edited 03-14-2019 11:36 PM
We have a monitoring program called Whats Up Gold. We use it to monitoring various servers and along with them all our CCM's. We have been getting an alert from our PUB saying HTTPS is down and then it comes right back up.
In checking the event logs each time it happens we notice the following:
-----------------------------------
Source: ASP
EventID - 9
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.
-----------------------------------
AFTER that there are the following event logs
-----------------------------------
Source: ASP
EVENTID: 4
Service stopped
-----------------------------------
then we get
-----------------------------------
Source: ASP
EVENTID: 3
Service started
-----------------------------------
Now this happens alot. I think its normal and its only telling us it reached its timeout which it stops and then restarts.
But its alerting like crasy and the "BOSS'S" want to know why.
I am only taking a guess when saying it seems normal.
Has anyone else seen this and looked into it?
Any thoughts?
Thanks
09-18-2007 06:55 PM
Hi Donald,
This is a known bug :( You are most correct that it is not service effecting! You can show the Boss the bug listed in the Bug Toolkit :)
CSCeb80203
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.
Hope this helps!
Rob
09-18-2007 07:02 PM
Thank you SIR.
I should have figured it to be a "CISCO" bug.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: