Logs & Settings Action Plan for Skype Meeting issue

Owned by Agat Support
Last updated: Oct 01, 2018
1 min read
Please follow this action plan in order to collect the logs: 
1. Change the LAC Log Level
  1. Backup the Lync_Access_Control.xml file 
  2. Change the log severity level to debug and enable dumps: 
    • Change the <logging> tag in Lync_Access_Control.xml: 
      1. In <main> tag configure <severity>debug</severity> 
      2. In <dumps> tag change <enabled>true</enabled> 
  3. Save changes 

2. Change the Bastion Log Level

  1. Backup the bastion.xml file
  2. Change the log severity level to debug and enable dumps:
    • Change the <logging> tag in bastion.xml:
      1. In <main> tag configure <severity>debug</severity>
      2. In <dumps> tag change <enabled>true</enabled>
  3. Save changes
3. Restart the Bastion Service 
  1. Open PowerShell 
  2. Execute: Restart-Service bastion 

4. Replicate the issue 

5. Collect the log LAC_<poolname>_<date>.log and the Dumps folder from the relevant date

6. Collect the log Bastion.<date>.log and the dumps folder from the relevant date

7. Collect the Lync_Access_Control.xml

8. Revert back to the old Lync_Access_Control.xml

9. Revert back to the old Bastion.xml

10. Restart the Bastion Service

  1. Open PowerShell 
  2. Execute: Restart-Service bastion 

11. Export Access Portal Logs

  1. Open the Access Portal WebUI
  2. Browse to /admin/logfiles
  3. Change the log level to DEBUG
  4. Replicate the issue
  5. Click on Export
  6. Send AGAT Support the AccessPortal.log file.

12. Send AGAT Software Support the collected logs

The following files are expected to be delivered following this plan:
  1. Access Portal logs and settings
  2. LAC_<poolname>_<date>.log from the relevant time frame in Debug mode
  3. LAC Traffic dumps from the relevant time frame
  4. Lync_Access_Control.xml
  5. Bastion.<date>.log from the relevant date
  6. Bastion Traffic dumps folder from the relevant date
  7. Bastion.xml
  8. Skype for Business Client logs

Default file location could be found here.


Please include the following information:
a. Time frames of issue
b. Users involved (SIP Address, AD username, UPN, etc.)