BCAAA - How to collect debugging level verbosity logs in the Microsoft Windows server

Products

• ProxySG Software - SGOS
• ISG Proxy

Issue/Introduction

How to collect debugging level verbosity logs in the Microsoft Windows server for troubleshooting BCAAA IWA Direct and Windows SSO Single Sign-On (SSO) issues

Environment

Microsoft Windows

Resolution

1. Stop the BCAAA service processes in the Windows Task Manager

2. In the directory: C:\Program Files (x86)\Blue Coat Systems\BCAAA
    (where the "bcaaa.exe" file resides) delete (if any) log files named: 

• bcaaa.log
• bcaaa-xxxx.log
• debug_dcq_primary_full.sso         (contains "every login")
• debug_dcq_primary_inc.sso          (contains "every login" since the service started)
• dcq_primary_full.sso
• dcq_primary_inc.sso

3. Enable debug logging for both BCAAA and SSO:

    Run Notepad with admin rights
    a) edit the BCAAA.ini file and add/enable the following line:

    [Debug]
    DebugLevel=0xFFFFFFFF
    
    b) edit the SSO.ini file and add/enable the following line:

    [DCQSetup]
    DCQDebug=1

4. Re-start the BCAAA service from Windows Services

5. Reproduce the issue while debugging verbosity is on

6. Collect the following log files and attach them to the case:

•     bcaaa.log
•     bcca-xxxx.log
•     debug_dcq_primary_full.sso
•     debug_dcq_primary_inc.sso
•     bcca.ini
•     sso.ini

    Don't collect the following binary log files: 

•     dcq_primary_full.sso
•     dcq_primary_inc.sso

7. Stop the BCAAA service processes in the Windows Task Manager, disable debugging verbosity removing lines added in step three, and restart the BCAAA service

Additional Information

Can also refer to article ID: 166076 - "Gather BCAAA debug logs"