I have tried to print Narrative reports, using the various print selections (all pages, current page, and page range) and the message pops up with everything but the current page print selection.
It also appears if I try to print to .pdf. I tried that thinking it would be a way around the error but it still happened.
I don’t get the message when I try to print other things in the program.
Try Settings > Bluetooth & devices > Printers & scanners, where you can select your target printer, then check its current default Paper Size in preferences. Ensure both RM and the Windows settings are matching.
My printer is a wireless connection and works with various other reports in RM. I do not know where to check the settings for my printer in RM. It works with other stuff but just doesn’t with these.
First of all, I wish I could tell you what to do so you can just print from RM without jumping through hoops. But I don’t know what the solution is.
That being said, it has been years — probably really decades – since I have printed anything directly from RM. Instead, I save to a file and print from the file. That always works for me.
So I have to ask, what do you mean exactly by "print to .pdf.? Do you mean that you printed from RM and selected PDF as your printer? Or did you save from RM to a PDF file, and then print the resultant PDF file? I suspect that if you do the former it still will not print until you solve the underlying printing problem. And I suspect that if you do the latter, that the file will print just fine. I could be wrong, but I did want to clarify what you had tried already.
My reply was about checking Windows 11 printer paper size setting. The Settings can be accessed thru Windows>Start button on the task bar. For RM, each report/chart type has a Layout>Page size setting. They should match (ie. have the same dimension).
“TCanvasD2D” errors relate directly to an Embarcadero Tool, ‘Embarcadero’ being the main software development software, I believe RootsMagic Inc. now uses. I would suggest such errors should be escalated to the RootsMagic developers for investigation of the cause.
Only someone the requisite programming knowledge of the Tool is likely to be able to provide an informed answer.