Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Alert in ISA Server 2006 when a new MSDE database is created: "Log Write Time Excessive"


View products that this article applies to.

Symptoms

In Microsoft Internet Security and Acceleration (ISA) Server 2006, you may receive a "Log Write Time Excessive" alert when a new MSDE database is created.

↑ Back to the top


Cause

When ISA Server 2006 creates a new MSDE database file for logging, it sets its initial database size to 75 megabytes (MB) and its growth size to 75 MB. However, ISA Server does not set the size of the MSDE transaction log file. By default, the initial log size is 1 MB and grows by 10 percent. If many records are to be logged, the MDSE transaction log file must expand large enough to hold the records. At an expansion rate of 10 percent, the transaction log file has to expand many times to be large enough. Therefore, it takes a long time for the records to be committed on the first commit after database creation. Usually this occurs when several thousand records are committed.

↑ Back to the top


Resolution

To resolve this problem, follow these steps:
  1. Download and then install the hotfix package that is mentioned in the following Microsoft Knowledge Base article:
    960927 Description of the ISA Server 2006 hotfix package: December 7, 2008
  2. Start Notepad, and then copy the following script into a Notepad file.
    Const SE_VPS_GUID = "{143F5698-103B-12D4-FF34-1F34767DEabc}"
    Const SE_VPS_NAME = "UseExtendedMSDELogFile"
    Const SE_VPS_VALUE = true
    
    Sub SetValue()
    
        ' Create the root obect.
        Dim root  ' The FPCLib.FPC root object
        Set root = CreateObject("FPC.Root")
    
        'Declare the other objects needed.
        Dim array       ' An FPCArray object
        Dim VendorSets  ' An FPCVendorParametersSets collection
        Dim VendorSet   ' An FPCVendorParametersSet object
    
        ' Get references to the array object
        ' and the network rules collection.
        Set array = root.GetContainingArray
        Set VendorSets = array.VendorParametersSets
    
        On Error Resume Next
        Set VendorSet = VendorSets.Item( SE_VPS_GUID )
    
        If Err.Number <> 0 Then
            Err.Clear
    
            ' Add the item
            Set VendorSet = VendorSets.Add( SE_VPS_GUID )
            CheckError
            WScript.Echo "New VendorSet added... " & VendorSet.Name
    
        Else
            WScript.Echo "Existing VendorSet found... value- " &  VendorSet.Value(SE_VPS_NAME)
        End If
    
        if VendorSet.Value(SE_VPS_NAME) <> SE_VPS_VALUE Then
    
            Err.Clear
            VendorSet.Value(SE_VPS_NAME) = SE_VPS_VALUE
    
            If Err.Number <> 0 Then
                CheckError
            Else
                VendorSets.Save false, true
                CheckError
    
                If Err.Number = 0 Then
                    WScript.Echo "Done with " & SE_VPS_NAME & ", saved!"
                End If
            End If
        Else
            WScript.Echo "Done with " & SE_VPS_NAME & ", no change!"
        End If
    
    End Sub
    
    Sub CheckError()
    
        If Err.Number <> 0 Then
            WScript.Echo "An error occurred: 0x" & Hex(Err.Number) & " " & Err.Description
            Err.Clear
        End If
    
    End Sub
    
    SetValue
  3. Save the file as a Microsoft Visual Basic script file by using the .vbs file name extension. For example, save the file as ConfigLogsizeGrowth.vbs in the C:\ConfigLogsizeGrowth folder.
  4. At a command prompt, move to the location of the .vbs file, and then run the .vbs file. For example, run the following commands:
    cd C:\ConfigLogsizeGrowth cscript ConfigLogsizeGrowth.vbs
Note After you enable this hotfix, the log file size is set to grow by 2 MB.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: KB960925, kbqfe, kbsurveynew, kbfix, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 960925
Revision : 1
Created on : 4/1/2009
Published on : 4/1/2009
Exists online : False
Views : 457