none
(TMG) Log Disconnected After Install SP2!!!

    Question

  • I have another database server (SQL Server) act as TMG's log server. But after installing sp2, the log status display as Disconnected! and all log save as many files with an extension .llq in the disk.

    Anyboby have ideas for this issue?

    It's urgent! Boss need the log.  :(

    Friday, March 23, 2012 8:07 AM

All replies

  • Hi,

    connectivity to the central SQL Server seems to be lost. This is the reason for .LLQ (Lare Logging Queue) files in the local filesystem on the TMG Server. As a first step try to temporary change the TMG logging for Webproxy and Firewall service to local file system or local SQL instance. After the changes has been applied try to change the logging again to central SQL Server. If this doesn't solve the problem ask again here in the forum and we try to troubleshoot the SQL logging problem


    regards Marc Grote aka Jens Baier - www.it-training-grote.de - www.forefront-tmg.de - www.nt-faq.de

    Friday, March 23, 2012 8:29 AM
  • Thanks a lot, I'll try it.

    But I'm afraid the LLQ log files in the local filesystem will be lost. Is it possible to restore after log to sql server is working again? 

    Friday, March 23, 2012 9:53 AM
  • "Temporary change the TMG logging to local file system. After the changes has been applied try to change the logging again to central SQL Server. "

    Following the step, I did it, but it doesn't work and I lost all my .llq files(one week history log) in the directory! My God!

    I have to unistall sp2, After unistall the sp2, it works like before.

    What's happened with TMG sp2?

    Friday, March 23, 2012 11:28 AM
  • Hi,

    Thank you for the post.

    Please refer to this kb: http://support.microsoft.com/kb/2662548/en-us

    Regards,


    Nick Gu - MSFT

    Thursday, March 29, 2012 9:22 AM
    Moderator
  • Hi,

    Thank you for the post.

    Please refer to this kb: http://support.microsoft.com/kb/2662548/en-us

    Regards,


    Nick Gu - MSFT

    I did it follow the step, But it still doesn't work.

    What's wrong with TMG sp2?

    I have tested three times, uninstall sp2, it's ok. install sp2, it doesn't work.

    OS:Windows Server 2008 R2 standard Chinese version

    Database Server:  Sql server 2005.

    ???? help!

    • Edited by Jack,Wang Wednesday, April 04, 2012 2:10 PM
    Wednesday, April 04, 2012 2:07 PM
  • Same issue here too with SP2, any fix?

    Ben

    Friday, April 27, 2012 7:53 AM
  • Friday, April 27, 2012 8:13 AM
    Moderator
  • I had the same issue.

    Before SP2 installation I changed logging into local SQL .

    After SP2 installation  I changed logging into external SQL.

    Cheers

    Fred

    Sunday, July 01, 2012 10:21 PM
  • Hi,

    The problem with our TMG setup was that we used a FQDN domain instead of the NetBIOS name when configuring the Firewall service account. So don’t use “Domain.local\TMG-FW-svc” but “Domain\TMG-FW-svc”. This is a limitation of SQL express as the account can’t be added as a login account.

     

    C:\ >sqlcmd -S localhost\MSFW

    1> CREATE LOGIN [Domain.local\TMG-FW-svc] FROM WINDOWS

    2> go

    Msg 15401, Level 16, State 1, Server <Your TMG Server>\MSFW, Line 1

    Windows NT user or group ' Domain.local\TMG-FW-svc ' not found. Check the name again.

     

    To check if the firewall service account is added as a login:

    Run a CMD as administrator

    sqlcmd -S localhost\MSFW

    1> select loginname from master.dbo.syslogins

    2> go

     

    See if the account is there.


    Regards, Bas



    • Edited by BSterkenburg Tuesday, August 14, 2012 7:25 AM
    • Proposed as answer by demon_man Wednesday, April 29, 2015 1:46 PM
    Tuesday, August 14, 2012 7:24 AM
  • TMG 2010: Cannot connect to the SQL database - Event IDs 17204 and 17207

    Symptoms

     

    You might see the following behavior on your TMG server that is configured to write logs into an SQL database:

     

    + The logging status is disconnected (no connection to the database)

    + The size of log queue is increasing (LLQ files are being written to the disk)

    + After the start of the service SQL Server (MSFW) you see in the application log error messages like these (you might see many of these errors):

     

    Log Name:      Application

    Source:        MSSQL$MSFW

    Date:          XXXX

    Event ID:      17204

    Task Category: Server

    Level:         Error

    Keywords:      Classic

    User:          SYSTEM

    Computer:      XXXX

    Description:

    FCB::Open failed: Could not open file path\filename.mdf for file number 1.  OS error: 2(failed to retrieve text for this error. Reason: 15100).

     

    Log Name:      Application

    Source:        MSSQL$MSFW

    Date:          XXXX

    Event ID:      17207

    Task Category: Server

    Level:         Error

    Keywords:      Classic

    User:          SYSTEM

    Computer:      XXXX

    Description:

    FileMgr::StartLogFiles: Operating system error 2(failed to retrieve text for this error. Reason: 15105) occurred while creating or opening file 'path\filename.ldf'. Diagnose and correct the operating system error, and retry the operation.

    Cause

    The actual root cause of the problem is unknown. Basically, the files MSSQL$MSFW is looking for are not available anymore.

    Resolution

     Open an elevated command prompt on the affected TMG server and connect to the SQL instance:

     OSQL -S %computername%\msfw -E

    Execute the following commands until you have deleted all the orphaned databases: (databasename = the name of the file without the file extension from the event)

    DROP DATABASE databasename             

    GO

    After finishing with dropping the inaccessible databases you should restart the SQL Server (MSFW) service. If there are no new errors in the application log, you have to restart the TMG control service and check the logging status again.

    THe command should look like OSQL -S %TMGcomputername%\msfw -E

    DROP DATABASE ISALOG_20100708_WEB_000

    DROP DATABASE ISALOG_20100708_FWS_000

    database name you can find in the Application log after restaring local SQL server on TMG

    • Proposed as answer by Mityab Wednesday, August 22, 2012 9:58 AM
    Wednesday, August 22, 2012 9:57 AM