Forefront TMG 2010 SP1 cannot write a log to a local SQL Server database

Symptoms

Consider one of the following scenarios:

  • You install an English version of Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1 (SP1) on a computer that is running a non-English version of a Windows operating system.
  • You install a non-English version of TMG 2010 SP1 on a computer that is running an English version of a Windows operating system.

In these scenarios, many pending files for the TMG Large Logging Queue (LLQ) logging feature are created on the hard disk drive of the computer. Additionally, all the disk space on the hard disk drive may be exhausted when these files are created.



Additionally, the "Log formatting failure" alert is raised, and the following event entry is logged in the Application log:


Note The %1, %2, %3, and %4 are placeholders for the dynamic information that is related to this event.

Cause

This issue occurs because some invalid data is created for some fields in the SQL database that is used for logging traffic. Therefore, SQL Server stops logging, and the LLQ files build up.

Note The LLQ files store the log-related data until the data can be committed to the SQL database.

Resolution

Update information

To resolve this issue, install the software update that is described in the following Microsoft Knowledge Base (KB) article:
2288910   Software Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1

Status

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

More Information

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

Properties

Article ID: 2256054 - Last Review: Nov 9, 2010 - Revision: 1

Feedback