Print jobs hangs and fonts change using Report View Distribution and Dot Net 4.0

Question

ERP application written in C3 .net using Report View Distribution 10/Dot Net 4.0 in Terminal Server/Citrix environment.  SQL 2008 R2 is back end.  Two Problems:  The font changes is the viewer and report - when running on Terminal Server or Citrix environment where client is using Window 7. 

The second problem is the reports occassionally hang in the viewer or when sent directly to the printer.

Have 160 customer using the application - but this only occurs if the Terminal Server/Citirx server is 2008, database is  MSSQL 2008 r2 and using Report Viewer Distribution 10 with Dot Net 4.0.  We have about 10 Clients with this environment and they all experience the same problem.

We have done substantial research with out a lot of results.  Would appreciate any help.

Answer 1

Here is a little more information related to the above issue:

I have installed the version of the application on a Windows 2003 server.  Because of the application I was forced to install dot net 4.0.   Prior to installing the latest version I was running a version of application which did not required Dot Net 4.0 (used Dot Not 3.5) – and I had no problems with the font changing or the application hanging.

If I access the application on the Console (not using Terminal Services) – the font is fine (the console is again a Windows 2003).

If I access the application from my PC (Windows 7) using the Terminal Services the font changes.

I then set up the application client directly on my PC (Windows 7) and accessed the server in Client/Server mode  the font does NOT change.

I tried it with both Report Viewer Distributable 2008 and Report View Distributable 2010 sp1 – both had issues with the font via Terminal Services.  Not in Client/Server mode.

So it appears to me it is an bug associated with Dot Net 4.0 working with Terminal Services/Citrix Server.   Any suggestions?  Any help?  

Answer 2

Hi David,

we have exact the same problem in a citrix environment.
Viewing and printing via reporting forms produces very bad output (I don't know, whether the fond changes - may be it's simply bad rendered).
Saving the report as a PDF works fine and thus the printout from PDF is fine too.

---

TIA, Matze

Answer 3

Hi TIA

What development environment are you using?   Are you using Dot Net 4.0?  Are you using report writer distributable - if so, which version?

Could you describe your environment?  So we isolate the common elements.   Obviously Citrix and TS is one.  Are you using SQL 2008? 

Thanks good to know we are not alone. 

Answer 4

Hi David,

here is the configuration we use.

.NET 4.0
ReportViewer 2010 Redistributable SP1

The Terminal Server is a Windows 2003 Server Machine as far as I know. The clients are XP machines.
We had no problems with .NET 2.0/Report Viewer 2008. .NET 3.5 was never used.

I thought this was a problem with softwarerendering and tried to reproduce this in a virtual machine. The output was not as good as on my desktop but not as bad as in the citrix environment. hmmm....

I hope, some Microsoft contributors read this and give some help...

Regards, Matze

---

TIA, Matze