Hi Ludek,
Do you suppose it's possible that this issue also causes the Crystal Reports Viewer to export corrupted PDF files, or is that a separate issue?
Our reporting application targets .NET Framework v4.6.1, and I've installed the latest CR runtime (CRforVS_redist_install_64bit_13_0_15). By duplicating the system_web\4_0_30319 folder to match what the ASP.NET report viewer was trying to load (4_6_1055 in our case), the viewer loads and displays reports just fine. However, it exports corrupted PDF files (all pages are blank, though page count and orientation are correct). Exporting to Microsoft Word works fine, as does exporting programmatically to PDF (export without using the viewer).
Adding the businessObjects config section also enabled the viewer to load (though I had to exclude the tilde from the resourceURI to make it work), but the PDF export problem still exists.
Is this applicable at all, or should I create a new post?
Thanks,
Andre