Ranorex Forum

Hello Team,

We were using the report to pdf functionality of ranorex since 4-5 month and it was working properly.
Last week we upgraded to ranorex8.0, and since that time the report to pdf functionality is not working properly.
We are getting following error


All required fields are present in the project i.e pdf dll and cs file.


But still we are getting the error while generating the pdf report.

Note : we are executing our script on VM. Daily we start our VM for script execution and we stop the VM after execution.
When 1st time we got the error for pdf generation, at that time we tried to delete the pdf dll and add it again to project. After that it worked accordingly.
But on the next day we got the same error again. And if we repeat the step of deleting and adding the pdf dll, it works for that day, and next day we again gets the error.


Please help us find the reason behind this?

Hello,

The customer was in contact with us via email.

The issue was caused by the missing Ranorex.PDF-dll, which is not correctly deployed to the output directory. The issue will be addressed within one of our upcoming releases. As a workaround, create a post-build action which copies the dll to the output folder

Sincerely,
Robert

Plus there seems to be a misidentification by Kaspersky AV against the Ranorex.pdf.exe going on. It gets terminated and quarantined.

This is exactly what happened to me. I couldn't whitelist it either for some reason. Any idea on how to address this?

Hi,

please ensure that you're using the latest version of the Ranorex.PDF DLL.

• • Right-click project
  • Manage packages
  • Search for „Ranorex ReportToPDF“ within the „Available“ tab and install it (Current ver. 1.0.12)

and of course, please ensure to white-list it if it still gets blocked.

Sincerely,
Robert

Rightclicking on my project and "Manage Packages" does not see the installed reportToPdf, but if i rightclick on the referenced Project Automation Helpers, i see the package, and can update it (it's now .12). I added that package to every project using the technique you just described, and it was mayhem. Having it just in Automation Helpers (and referencing that project in all concerned projects did the trick (with disabled Kaspersky...))