AR20 Parser Compatibility, Performance, and Multi-Instance Deployment Questions

Posted by: julien.iseli on 19 November 2026, 3:33 am EST

  • Posted 19 November 2026, 3:33 am EST

    Hi,

    We successfully migrated to ActiveReports 20, but a significant number of RDLX reports had to be modified before they would render correctly. It appears that AR20 is much less forgiving when parsing report definitions than previous versions. Is there a configuration setting or compatibility mode that could make the parser behave more leniently?

    We also noticed a noticeable performance degradation when rendering reports through the Web Viewer compared to our previous setup. Are there any recommended configurations, best practices, or performance optimizations we should apply to improve rendering times (especially when loading images)?

    Finally, we observed that both the Web Viewer and Web Designer stop functioning correctly when the Reporting API backend is scaled out to multiple instances. Do you have any documentation or guidance on configuring ActiveReports for a multi-instance or load-balanced environment? In particular, are there any requirements regarding shared storage, caching, session state, or other infrastructure components that need to be considered?

    Best,

    Julien

  • Posted 20 November 2026, 4:09 am EST

    Hi Julie,

    1. RDLX compatibility: There is no documented general “lenient parser” mode. SkipReportValidation bypasses pre-execution validation but does not fix malformed XML; validation should normally remain enabled. EnableLegacyDeserialization addresses specific older serialization formats. The GDI/CrossPlatform setting is not an RDLX parser compatibility option. See configuration guidance.

    2. Web Viewer performance: Please compare first-load and subsequent-load timings, separating database access, image retrieval, server rendering, and browser display. For images, reduce unnecessarily large dimensions/file sizes, check repeated downloads, and consider caching reusable resources. Benchmark HTML versus SVG rendering while checking layout fidelity. Memory/disk caching settings should be evaluated against actual memory and I/O usage; disk caching does not necessarily improve speed. Also retest with the latest applicable AR20 maintenance build. See viewer rendering options.

    3. Multiple backend instances: The viewer maintains its session on a single server, so an active session cannot be distributed across backend instances. We recommend implementing a custom store to manage reports and resources yourself using storage accessible to all instances. Please refer to the WebDesigner Custom Store sample. The sample uses local LiteDB storage by default, which should be adapted for your deployment. A custom store does not distribute viewer-session state. Requests belonging to a viewer session must still reach the server that created it, using session affinity.

    Regards,

    Anand

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels