Landscape orientation doesn't work in SAP Crystal Report 13.0.21 and 13.0.22 for Visual Studio

[Former Member]

Hi everyone,

We've just upgraded from SP17 to SP21 and found a new issue with the Landscape orientation.

On Windows 7, all our landscape reports preview in landscape but when printing to the printer, it prints in portrait. By the way, this works perfectly in windows server 2012 now.

Is this is a known crystal report issue? and if so - is there a workaround? this is a BIG problem for us.

Thanks,

Vasya

[former_member11696 · Accepted solution]

Hi All,

Sorry for the delay. I finally have a 1709 Windows 10 image running and tested Dan's report and I too get the same results, prints portrait from the WPF viewer.

I'll escalate it and try to get this in SP 23.

87397 / 2018 WPF viewer will not print landscape on Windows 10 build 1709

KBA - 2607294 - WPF viewer in CR for VS SP 22 will not print landscape on Windows 10 Fall Creator version 1709

Thanks again

Don

[Former Member · Accepted solution]

We look forward to testing a new version. However I'd like to emphasize, we have the described issue on Windows 7 Professional 64-bit(6.1, build 7601). Will you fix it for Win 7 as well?

[former_member11696 · Accepted solution]

I did not test that version, I did not think anyone was still using it.

https://support.microsoft.com/en-ca/help/13853/windows-lifecycle-fact-sheet

Client operating systems End of mainstream support End of extended support

Windows 7, service pack 1* January 13, 2015 January 14, 2020

I'll test it when I get a chance...

Don

[former_member11696 · Accepted solution]

Confirmed it doesn't work on Windows 7

[former_member579340]

Hi Don.

Like the others, I too would love to know an ETA on this, it's now May.

Printing landscape via the WPF viewer is broken and is causing us some very upset customers.

Thanks!

Scott

[Former Member]

Hi Don,

Thanks for acknowledging the issue. How often are the service packs released? Would it be possible to get and ETA for a solution?

Thanks,

TJ

[former_member11696]

4 times a year roughly... next one is end of May.

[Former Member]

Hi Don,

Thanks for acknowledging the issue. How often are the service packs released? Would it be possible to get and ETA for a solution?

As minor as this may seem, my customer base is not too pleased with the work-arounds we've proposed. I know, I know... very demanding..

Thanks,

TJ

[former_member11696]

End of May 2018 is the set date, that can change depending on how it all goes.

[former_member11696]

Also, this is not a support program, it's forums. If you want direct help log a case in SMP or purchase a single case.

Don

[former_member11696]

Did you try SP 22? They did some more updates to the WPF viewer.

Also, not clear what this actual issue is with this post now. Some it seems to be fixed and others not.

Everyone who still has an issue please post a new question and we'll work from there.

But test with SP 22 first and then specify the SP and anything else to help so I don't have to ask.

Thanks

Don

[Former Member]

Hi Don, it looks like you, guys, don't accept our issue as a known one. I tested some reports with the application you mentioned in your previous post(RAS2010_Printing) and it printed correctly - in landscape orientation. However, in our application we're using WPF Viewer(SAPBusinessObjects.WPF.Viewer.CrystalReportsViewer) instead and always getting portrait orientation there. Please let me know what else I could check and if you could advise on a possible solution.

Thanks,

Vasya

[Former Member]

Hello

We just tried SP 22 and the sub reports seem to be fixed at least for Windows 2012 but we are back to Landscape mode getting printed in Portrait. We cannot seem to find a version of Crystal Viewer that has sub reports working, that does not have the broken Landscape to Portrait issue. Please me know if there is a work around or further plans to fix this.

https://archive.sap.com/discussions/thread/3812560

Thanks

Carlo

[former_member11696]

See the download WIKI page, SP 22 was just released, we don't patch SP's, full builds only.

https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

On that page is a test app for printing reports with save data, see i f it works for you.

https://blogs.sap.com/2015/08/19/printing-crystal-reports-in-net/

Don

[Former Member]

Don, please let us know if this issue was fixed in SP22?

[Former Member]

Is there a workaround?

[Former Member]

Same here! I have requested support on this 2 months ago! Can we do a screen sharing session to demonstrate the problem?

Our customers are getting really upset.

[Former Member]

Our software has the same problem. The issue also occurs on 13.0.20.

Reports designed as Landscape can be printed in Landscape. Portrait reports could be printed in Landscape in prior versions of Crystal Report runtime. The detail section used to be resized based on the page size.

[Former Member]

I did try changing the paper size manually and it still did not fix the printing issue.

Furthermore, the sub reports do not work. Instead of displaying the sub report it pulls up data from the group tree.

P.S. Everything was tested on Win 7 64 bit and Win server 2012 64 bit

[Former Member]

Our printer is konica minolta bizhub c554

[former_member11696]

I still need to know what printer are you using?

[former_member11696]

Is Windows 7 32 or 64 bit?

If you configure the printer with the custom paper size and orientation does that work?

Which driver are you using?

Don

[Former Member]

Don, I have Win 7 64. We use standard driver for this printer, but this issue happens with any printer we have. I downgraded to SP 17 and cannot recall if I played with printer settings, but definitely all that looks like it might be a regression of this: https://archive.sap.com/discussions/message/16550384

[former_member11696]

Different issue...

[former_member11696]

What printer are you using?

[Former Member]

It's konica minolta bizhub c554

[Former Member]

Is there any update on that?

[Former Member]

Same here. This is a huge problem for our customers! It's creating a huge hit on our support department. Please, can someone take a look at this asap!?

Thank you in advance!