WPF ReportViewer hangs on second print

[Markus Wolff]

I am using the WPF ReportViewer component inside a modal window (Version 7.0.13.228). When the document is sent to the printer the message box "Printing page .. of .." hangs on the second attempt to print. The print queue shows the document but it seems no data is sent (Pages: N/A, Size: empty). The [Cancel] button does not do anything and the only solution is to abort the program from the task manager.

Is there any way to debug this any further? It has been reported to me by one of my customers who is running the program on a terminal server.

[Stef]

Hello Markus,

If you print without showing the print dialog, please assure the used PrinterSettings are suitable. In addition, you can use the Report.Error event to check if there are any issues during the document processing.

Any additional information as applied settings, from where and how is initiated the print operation will be helpful. Steps how to reproduce the issue at our side will be highly appreciated.

All the best,
Stef
the Telerik team

[Markus Wolff]

Hi Stef,

thanks for your reply.
The document is printed using the print dialog. I just opened a support ticket on this with further information.
I will try to attach to the Report.Error event and add any gathered information as soon as possible.

Kind regards
Markus

[Stef]

Hi Markus,

Thank you for your update.

If we find something important for the other community members, we will post here the results of our discussion from your support ticket.

Greetings,
Stef
the Telerik team

[Markus Wolff]

Report.Error event seems not to be raised.
We couldn't reproduce the error using the old program version which utilizes Reporting and ReportViewer.Wpf as of version 6.2.12.1025.
The terminal server is running Windows 2008 R2 Server 64bit.
Only some of the user accounts and reports seem to be affected.
Is there any way to track the data that is sent to the printer?

The current scenario is:
1 Window with ReportViewer is opened
2 Report displays OK
3 User selects print from the viewer's toolbar
4 Print dialog shows up
5 User selects printer and starts printing
6 Message appears "Printing page ... of XyzReport"
7 Printer prints

When the users tries to print another or even the same report after this the system hangs at step 6.
The print queue shows the job but without a number of pages or size.

What approach could I use to debug this?

[Stef]

Hello Markus,

Please check the comments applying to Windows Server 2008 R2 under the msdn article Enable or disable logging of printing events. In addition, check if all needed assemblies are deployed to these users where printing fails. Basically if the printing message appears, means the report is sent to the printer. If possible test exporting to PDF and printing, or printing other document to the same printer from the same client having problems.

As there is no such issue logged for Q3 2012 nor Q1 2013 WPF ReportViewer control printing, I would ask you to send us the problematic project to test it at our side. Any additional details as selected printer, installed drivers and error logs will be helpful in investigating the question.

Regards,
Stef
the Telerik team

[Robb]

Hello everyone,
Has anyone resolved that issue?

it's actually similar to awaiting for some callback messaging from Winodws Server 2008 print driver by ReportViewer.
and the notification is never comes or is not processed/skipped by ReportViewer
Windows driver says that the printer is awaiting for something or heating, though other applications are working fine.
Maybe Telerik Printer manager doesn't send some specific command to printer, which is ommited in other Windows versions, but mandatory for Server 2008.
so it shows dialog notification window Send to Printer Page 1 of 1 and hangs on.

[Stef]

Hello Robb,

We need more information about the server settings and conditions under which the issue appears. Please check my previous post and let us know:

• Are any warnings or errors logged when you try to print;
• Do you have any relevant information/errors in windows event viewer?
• Which viewer and Telerik Reporting version you have tested?
• Is the error reproducible only with a specific printer?
• Which .NET framework are installed on the server?

We will be waiting for your details.

Regards,
Stef
Telerik

[John]

Has this issue been resolved?  I am experiencing the same problem with version 8.1.14.804.

Thanks,
John

[Stef]

Hello John,

Please go through the whole thread and my posts from April 3rd, 2913 and May 23rd, 2013. To investigate the problem, please send us the mentioned details in a support ticket referencing this forum thread.


Thank you for your cooperation.

Regards,
Stef
Telerik

 

 

[Dan]

We have been experiencing the same issue in our VMWare environment. It isn't always the first printed report spooling with these symptoms, but always by the second print attempt of the same report. The same behavior is exhibited using the Telerik Reporting WPF and WinForms demo applications, which concludes that neither our application nor reports are to blame.

What we have figured out is that the VMs that have a single vCPU associated all have this issue. By adding a second vCPU to the VM, the problem seems to be eliminated. It is possible that it just occurs less frequently, but we have yet to encounter the issue again.

I have submitted a support ticket with details of our issue and hope to find a permanent resolution.

[Stef]

Hi guys,

Thanks to Dan's description in his support ticket on the same question, we managed to reproduce the problem and now we are investigating it. It appears to be a thread synchronization issue.

Once we have more information, we will post it in this forum thread.

Regards,
Stef
Telerik

 

 

[Stef]

Hello guys,

We found out what causes the problem and fixed in the latest available internal build - Telerik Reporting Q3 2014 SP1 version 8.2.14.1219.

Please download it and run the Upgrade Wizard. Keep in mind the WPF ReportVIewer has dependencies on Telerik UI for WPF, and older projects may require additional settings to be updated. To test if the fix applies to your machine configuration you can test with the WindowsForms ReportViewer, and then proceed to upgrade the original WPF projects - Setting a theme of the WPF/Silverlight Report Viewer (Q1 2014 and later).

Regards,
Stef
Telerik