DBClient Logs

[Anonymous user]

📖 Home  Back  
DBClient logs show the low level communications between the data access components on the client and the server. The data access components is the interface used by all client access into the server and so DBClient logging shows communications between all applications connecting to the server from that client. DBClient logs are usually needed when diagnosing communications problems, particularly when trying to identify the cause of slow operations. Comparing times in ViewX logs, DBClient logs and DBServer logs can identify where the delay is occurring. Typically DBClient logs should be provided in conjunction with ViewX Logs and DBServer Logs.

DBClient log settings can only be configured through the registry.

In versions prior to ClearSCADA 2007 R1, DBClient log files settings are stored in the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Serck Controls\SCX6\DBClient"LogEnable"=true

In ClearSCADA 2007 R1 and later the key has changed as part of the changes to support Windows Vista, but the logging settings have remained the same.

HKEY_CURRENT_USER\SOFTWARE\Serck Controls\SCX6\DBClient

When enabling DBClient logging, set the LogEnable key to true (default is false) and restart the client application showing the problem (most typically ViewX). DBClient log files can be found in the location defined by the registry value LogFileBase.

Please note that settings in HKEY_CURRENT_USER are specific to the currently logged on user. To apply settings to each Windows user where logging is required, log on as that user and apply the same changes. If security permissions do not allow registry access for some users, changes can be made through HKEY_USERS which stores information about each user profile under unique Security Identifiers. Refer to the following link for information on how to match each user profile with the appropriate security identifier (click here)

Go: Home Back