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 run the following Report Desk report, I/M -> Processing -> Inventory Transfer Processing -> List -> UDR Transfer Trx History Summary, you use the following parameters:
You expect there should be data in the date range above. But you get the following message "No qualifying records; report canceled" when you run it:
To debug this further, one method is to create registry keys to produce debugging data and send to Netcellent support for further analysis. To do so, choose to run "regedit" to bring up the registry editor. Navigate to Computer\HKEY_CURRENT_USER\Software\NETcellent\Elliott\8.0\Report Desk\Debug and right click and choose "Add" -> "String Value" entries as shown below:
- DebugLogLevel: Details
- LogSQL: Yes
- SerializePassingXML: Yes
- SerializeReportDef: Yes
- SerializeUDRSpec: Yes
- SerializeUDTSpec: Yes
Note these key pair values are "case sensitive" so you must enter the exact case for it to work.
Now you can run the same Report Desk report again to re-create the error. Once you have done that, bring up Windows Explorer, and enter "%temp%" in the navigate box:
That will redirect the system to bring up your local temporary path similar to the following:
Click on the "Date modified" column to let it sort by reverse sequence. Highlight and copy the debug files just created. Email Netcellent support for further analysis.
Please also see the following related KB article:
EMK
Related Articles
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 ...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 ...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 ...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 ...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 ...