locked
TMG Logging Status - Disconnected RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi folks,

    Our TMG 2010 (SP2) installation is configured using default settings for Firewall & Web Proxy Logging. However, we are seeing the Log Status as being 'disconnected'. We are logging to the default folder which just appears to contain .llq files. Could someone please point me in the right direction to begin troubleshooting this issue as we are hoping to move this installation on to our live network as soon as possible?

     

    Many thanks,

     

    JP

    Thursday, December 29, 2011 11:55 AM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Thank you for the post.

     

    Please stopping ISACTRL Service, delete the LLQ Files, restart the ISACTRL Service and then see if it works. Here is similar thread: http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/thread/59f3c827-e0e1-4278-9144-6691fcbdc135.

     

    Regards,

    Nick Gu - MSFT
    Friday, December 30, 2011 7:28 AM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    1.  Check security rights to log volume and directory:

    For any alternative logging folder, the Network Service account must have read permissions from the root partition and any parent folder for the folder. On the logging folder itself, the following permissions are required:

    • Network Service: Full Control
    • System: Full Control
    • Administrators: Full Control

    2. Stop all TMG services

    3. Check is there any OLD log DBs:

    run privileged console

    cd C:\Program Files\Microsoft SQL Server\100\Tools\Binn

    sqlcmd -S localhost\msfw -q “select @@version”

    select @@version;

    go

    select name from sys.databases;

    go

    you'll see a list of DBs

    drop every DBs with name like  ISALOG_ХХХХХХХ_ХХХ_ХХХ

    drop database ISALOG_20140619_WEB_000

    GO

    again check is there left any DBs like ISALOG_ХХХХХХХ_ХХХ_ХХХ

    4. Run all TMG services

    It works for all my TMGs with this log trouble.


    Check log status it must change to QUEUE IN USE, and then to READY



    • Edited by Dezinto Friday, June 20, 2014 9:05 AM
    Friday, June 20, 2014 9:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It worked for me, tnx man u just saved my day...
    Tuesday, August 11, 2015 10:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1.  Check security rights to log volume and directory:

    For any alternative logging folder, the Network Service account must have read permissions from the root partition and any parent folder for the folder. On the logging folder itself, the following permissions are required:

    • Network Service: Full Control
    • System: Full Control
    • Administrators: Full Control

    2. Stop all TMG services

    3. Check is there any OLD log DBs:

    run privileged console

    cd C:\Program Files\Microsoft SQL Server\100\Tools\Binn

    sqlcmd -S localhost\msfw -q “select @@version”

    select @@version;

    go

    select name from sys.databases;

    go

    you'll see a list of DBs

    drop every DBs with name like  ISALOG_ХХХХХХХ_ХХХ_ХХХ

    drop database ISALOG_20140619_WEB_000

    GO

    again check is there left any DBs like ISALOG_ХХХХХХХ_ХХХ_ХХХ

    4. Run all TMG services

    It works for all my TMGs with this log trouble.


    Check log status it must change to QUEUE IN USE, and then to READY
    Genial - Many thanks





    Saturday, April 27, 2019 5:13 PM