DB Client Logging

DB Client log files contain low level information about the connections between the client(s) and the ClearSCADA server. This includes information about each request made by the client and the responses received by the client. DB Client log files are useful when investigating problems with client-server connections.

There are two groups of DB Client log files:

• Named—The log file is from a named ClearSCADA program. Named DB Client files use the following file name convention:

DBClient_<program name>_nnn.log

Where:

• <program name> is the name of the ClearSCADA program that created the file, for example, ViewX_Head1. The angle brackets <> are not included.
• nnn is the number of the log file, for example, 001 is the first log file, 002 is the second log file, 003 is the third log file and so on.
  
• Anonymous—The log file is from a Third Party client. Anonymous DB Client files use the following file name convention:

DBClientxxxx_nnn.log

Where:

• xxxx is the process Id as a 4 digit hexadecimal value.
• nnn is the number of the log file, for example, 001 is the first log file, 002 is the second log file, 003 is the third log file and so on.
  

To enable or disable client logging, you need to configure the logging settings via a registry editor Using a Registry Editor to Change Client Log File Settings

To display a client log file:

1. Use Windows Explorer to locate the log file. The log files are stored at the location that is specified in the LogFileBase registry setting.

   The location of the LogFileBase registry setting is:

   HKEY_CURRENT_USER\SOFTWARE\Schneider Electric\ClearSCADA\DBClient\LogFileBase

2. Open the log file in a text editor program, for example, Microsoft Windows Notepad.