How to Use DebugLogLevel Registry Value to Debug Report Desk Issues

How to Use DebugLogLevel Registry Value to Debug Report Desk Issues

Release Date: TBA
Version 8.6

Since Report Desk is a brand new feature of Elliott V8.5, you may encounter a problem with it.  If you do, a Netcellent support representative may ask you to turn on the debugging of Report Desk so a log file can be written to your %temp% folder.  You can then email the debug log file(s) to Netcellent for further analysis. 

To turn on the debugging feature of Report Desk, you will use "Regedit" and go to the following path:
    \\HKEY_CURRENT_USER\Software\NETcellent\Elliott\8.0\Report Desk\Debug
See sample screen below:


Create a String "DebugLogLevel" with the value of either "Summary" or "Details."  Then you will be ready to run Report Desk again.  A new dubug log file is created for each running of Report Desk on your computer.  Once you re-produce the error, browse to your %temp% folder.  Bring up Windows Explorer and enter %temp% in the address line:

Then press Enter. You will see a screen like this:

In this example, a file with the name RDDebug-181211183503.log is created.  If you open it, you can see data similar to the following:
----DEBUG: D----
12/11/2018 6:35 PM
Starting Report Desk
Starting Report Desk
Initializing components...
Loading...
Checking Registry settings...
ProcessCommandLine...
  D:\Netcellent\M\Elliott7\Bin85\EL850RD.Exe
  ARTYPLST.B.1.1.0
  /U=SUPERVISOR
  /C=ServerDSN=ELIROOT;Server=TS4
  /D=ServerDSN=ELI85DATA;Server=TS4
  /R=M:\ELLIOTT7
  /E=Y
  /V=8.5
  /L=BSS046
  /CO:01
  /P=YYYYY
  /F=

  Company : 01
  UserType:
Verifying connections...
VerifyConnections 1:
VerifyConnections 2:
Possible Populations...
Getting Rights info...
Loading report data...
BuildParametersPanel
VerifyReportDLL
AdjustFormatForParameters
Activating...
SetDefaultValues
GetGlobalVarDS
Ending _Load...

Email this debug file to Netcellent for further analysis.

You can turn off Report Desk debugging by going to registry and setting up the DebugLogLevel value to blank.


EMK


    • Related Articles

    • How to Investigate or Debug Report Desk Problem by Using Registry Keys

      Release Date: 01/25/2025 Version: 8.6 & Up Report Desk is based on the PSQL relational engine. It sends a SQL statement to PSQL engine to retrieve data. Sometimes, you don't get the result back that you expected, so what next? For example, when you ...

    • How to Investigate or Debug Report Desk Problem by Using SQL Statement

      Released Date: 1/25/2025 Version: 8.6 & Higher Report Desk is based on the PSQL relational engine. It sends a SQL statement to the PSQL engine to retrieve data. Sometimes, you don't get the result back as you expected, so what next? For example, when ...

    • Report Desk: Registry Settings

      6/19/2019 Useful Registry Settings DebugLogLevel: Set to Summary or Details to write a progress log to a file named something like %temp%\RDDebug-<yymmddhhmmss>.Log. See ...

    • A Case Where PSQL 13 Client Is Not Compatible with PSQL 15 Server

      Release Date: 02/04/2025 Version: 8.6 Do Users Need to Upgrade to PSQL 15 Client When Upgrading PSQL Server? We were often asked in the past if our users should upgrade their PSQL 13 client when they upgrade to the PSQL 15 server. In our past ...

    • Debug Libraries for Animating

      Release Date: 12/7/2023 Versions: Elliott V8.5 and Up Rationale On occasion, the Netcellent developer will want to test a new version of a COBOL program without disturbing other users or developers sharing the same environment. With this update, the ...