Advanced Features - Logs

Overview

On this tab, you can configure BYODAPP Logs settings.

By default BYODAPP doesn't create logs, to avoid performance issues.

Logs exist to find more easily the origin of the errors encountered on BYODAPP and you can enable them by doing so:

  • go to C:\wsession

  • create the folder 'Trace'. Logs will automatically be created there, per user.

You will need to activate the log generation in the AdminTool > Advanced > Logs

Screenshot 1-1

There are 5 types of logs:

  • The Web Portal log,
  • The Session Opening log,
  • The Session control log,
  • The Load-Balancing log and
  • The AdminTool application (interface) log.


Log levels correspond to different components, our support team will tell you what value to put according to the problem encountered.

Here are the different log file names and locations:

  • Web Portal log: "C:\Program Files (x86)\BYODAPP\Clients\www\cgi-bin\hb.log"

  • Session Opening log: "C:\wsession\trace"

  • Session control log: "C:\Program Files (x86)\BYODAPP\UserDesktop\files\APSC.log"

  • Load Balancing log: "C:\Program Files (x86)\BYODAPP\UserDesktop\files\svcenterprise.log"

  • AdminTool application log: "C:\Program Files (x86)\BYODAPP\UserDesktop\files\AdminTool.log"

  • RDS-Knight / BYODAPP Advanced Security: "C:\Program Files (x86)\BYODAPP-Security\logs"


You can enable the logs for Connection Client on the client side by adding the following registry key:

[HKEYLOCALMACHINE\SOFTWARE\Digital River\ConnectionClient] "Debug"="true"

The logs are located in C:\Users\\RDP6\logs directory if installation is per user or in C:\Program Files (x86)\Connection Client\RDP6\logs directory if installation is for all users.