Ask a questionAsk a question
 

AnswerLog Write Time excessive on ISA 2006?

Answers

  • Monday, July 13, 2009 6:28 AMNick Gu - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    Thank you for posting.

     

    As far as I know, “long write time excessive” is a new alert, it indicates when ISA Server logging fails. By default, if the logging process takes longer than 15 seconds, this alert is generated. if this pattern continues and the time exceeds 30 seconds ISA Server will go into lockdown mode. To resolve this issue, you may refer to the KB960925(two steps: 1.install the hotfix kb960927; 2.run the customize script). Meanwhile, this issue may occur when ISA Server running under a heavy load. For more information, please see the following link.

     

    http://support.microsoft.com/kb/941296/en-us

     

    Regards,


    Nick Gu - MSFT

All Replies

  • Monday, July 13, 2009 6:28 AMNick Gu - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi,

     

    Thank you for posting.

     

    As far as I know, “long write time excessive” is a new alert, it indicates when ISA Server logging fails. By default, if the logging process takes longer than 15 seconds, this alert is generated. if this pattern continues and the time exceeds 30 seconds ISA Server will go into lockdown mode. To resolve this issue, you may refer to the KB960925(two steps: 1.install the hotfix kb960927; 2.run the customize script). Meanwhile, this issue may occur when ISA Server running under a heavy load. For more information, please see the following link.

     

    http://support.microsoft.com/kb/941296/en-us

     

    Regards,


    Nick Gu - MSFT
  • Saturday, August 15, 2009 1:24 AMJohn Gwinner Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Oh, this is fantastic!  I get that alert fairly often and was worried my hard drives were slow ... I kept defragging offline, etc.

    I just requested the hotfix. 

    Thanks!


    == John ==