Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jan 27, 2021 12:20:39 PM
Jan 14, 2021 4:33:14 AM
The Windows event logs are filled up with the entry and restarting the Qlik Sense services stops this problem for a short time.
ERROR: null value in column "payload" violates not-null constraint
DETAIL: Failing row contains (255769031, 2020-12-09 11:27:18.845765-06, DEBUG, 76, QlikSensePrintingWebSocketProxy, servername, printing, 10696, null).
CONTEXT: COPY log_entries, line 8
STATEMENT: COPY public.log_entries (entry_timestamp, entry_level, thread, logger, process_host, process_name, process_id, payload) FROM STDIN WITH BINARY
R&D identified a 3rd party library (SuperSocket) which by default uses log4net as its logger, being the same Qlik default logger this is used and a null value is written. R&D is working on a fix.
Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support at support.qlik.com with the ID QB- 3361 for reference.
A possible workaround is to change the table log_entries in the QLogs database to accept NULL values.
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
Qlik Sense Enterprise on Windows April 2021
Product Defect ID: QB-3361