ReportPro 2.34 / VO App

[Neale]

Windows update KB5089573 has caused a problem with ReportPro2, for now I have uninstalled the latest update and all is OK.
I have attached a screen shot from the production app and one from the VO IDE. Any ideas?

[Neale]

BTW the error occurs with a very simple report or complex.
And also from the stand alone RP editor.

[Chris]

Hi Neale,

We will look into it. Can you please send us a report showing the problem so we have a reproducible sample to debug?

[robert]

Neale,

This seems to be happening in the code that reads font descriptors for True Type fonts.
We will look into this, but it would help to see which fonts you are using in the report.
And if they are not standard Windows fonts, then please include the TTF files for these fonts.

Robert

[Neale]

Simple report and table attached, with screen shot of error when the report is exported.
Run report, export report to PDF and error occurs.
Tested on a computer running the latest Win 11 KB5089573.

[Neale]

Also, this error can occur.

[Jan@share.be]

Hi

We have the same problem, report export to PDF generates this error.
thanks for the fix (deinstall the Windows update KB5089573), after that it works again.

But we would like to have a report-fix if it is possible.

thanks

Jan Van Calster

[robert]

Guys,

We will try to come with a fix asap.
But we're also very busy getting X# 3 ready, and that is our main product.
RP2 and RP3 are "abandoned" and we have adopted them, but our own "baby" has a higher priority as you will understand.

Robert

[Jan@share.be]

Today, the same problem again.

Removing Windows update KB5094126 solved the problem.
This is becoming a monthly problem I fear.

Jan

[comitas2]

Hello,
Just a quick note on how this behaves on my Windows 11 system with an X# report:
An error occurs as soon as the report starts (XSharp_1.jpg)

After a short wait, the message closes and another error appears (XSharp_2.jpg)

While a report from a Vulcan application at least displays correctly,
an error occurs when attempting to print to PDF (Vulcan_1.jpg)

Perhaps this helps narrow down the cause? My guess is a printer device
that cannot be assigned due to the 'new' Windows Protected Print feature—essentially a null object.
Regards, Jörg