xmlSAX2Characters: huge text node error when loading large .nessus XML files via XmlSimple

Chrisrokc — Tue, 31 Mar 2026 14:56:13 GMT

We're loading Nessus scan files (.nessus, which are XML) using XmlSimple in a Qlik Sense Enterprise on Windows environment. When a file contains a single text node larger than ~10MB (typically a host property with a full filesystem listing), the reload fails with:

xmlSAX2Characters: huge text node On line number: 11661. SystemID: (null)

This appears to be libxml2's hard-coded XML_MAX_TEXT_LENGTH limit (10,000,000 bytes). libxml2 supports an XML_PARSE_HUGE flag that raises this to 1GB, but we can't find any way to enable it in Qlik Sense.

What we've confirmed so far:

The LongestPossibleLine setting in Settings.ini only applies to CSV, not XML (per support article 000080675)
The error fires during the initial DOM parse, before any WHERE clause or table path filtering is evaluated
We're currently planning to wrap loads in ErrorMode=0 / ScriptError checks as a workaround

Is there any engine configuration, Settings.ini parameter, or other mechanism in Qlik Sense to raise or disable the XML text node size limit?

Any guidance is appreciated. Thanks in advance.

Re: xmlSAX2Characters: huge text node error when loading large .nessus XML files via XmlSimple

Greg_Taffer — Tue, 31 Mar 2026 15:03:00 GMT

You can raise or remove limitations on data size in Qlik Sense by modifying the Engine's Settings.ini file. While Qlik does not have a specific named parameter for "XML node size," you can increase memory limits and adjust buffer settings to prevent failures when processing large data packets, often associated with XML/JSON parsing.

Recommended Settings.ini Parameters

Modify C:\ProgramData\Qlik\Sense\Engine\Settings.ini on all Engine nodes, adding the settings under the [Settings 7] header.

Disable/Raise Reload Memory Limit: A negative value or 0 disables the limit, allowing the script to use more memory for large nodes.

ini

[Settings 7] ReloadMemoryLimit=0

Increase File Streaming Buffer: If the issue is with data file size exceeding the buffer:

ini

[Settings 7] <Key to increase streaming buffer>

Note: The specific key to use for streaming buffer is often provided by Qlik Support based on the error log, but ReloadMemoryLimit is the primary mechanism to handle large data allocations.

Steps to Apply Changes

Stop services: Stop the Qlik Sense Engine and Qlik Sense Service Dispatcher services on all nodes.
Edit file: Open C:\ProgramData\Qlik\Sense\Engine\Settings.ini in Notepad as Administrator.
Add/Modify: Ensure [Settings 7] exists and add the parameters.
Save: Save and ensure there is a blank line at the end of the file.
Restart: Start the services.

Alternative Adjustments

If the error is related to HTTP communications (e.g., Qlik Web Connectors), you may need to increase the HTTP Header size via the Registry:

Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Parameters: Increase MaxFieldLength and MaxRequestBytes.

Disclaimer: Modifying settings.ini to unlimited (0) can cause engine instability if memory is exhausted.

topic xmlSAX2Characters: huge text node error when loading large .nessus XML files via XmlSimple in App Development

xmlSAX2Characters: huge text node error when loading large .nessus XML files via XmlSimple

Re: xmlSAX2Characters: huge text node error when loading large .nessus XML files via XmlSimple