64-bit Windows Server 2003 Terminal Services
We currently have a VB6 application that uses Crystal Reports 184.108.40.2065 for it's reports. The application has ran just fine on a 32-bit Windows Server 2003 Terminal Server for years now.
However, we have more users and RAM is becoming a problem as 32-bit is limited to 4GB. We want to move the app to a 64-bit Windows Server 2003 Terminal Server.
The application seems to run just fine and reports come up as they should with one exception. Bar charts, pie charts, and other graphics do not display. Nor do they print. The rest of the report displays and prints just fine - but no graphics show up.
Ludek Uher replied
First thing I'd recommend is upgrading to CR XI r2 (11.5.x). CR 11.0 is no longer supported and if you find this is a bug of some sort, there will not be an escalation to QA for a fix available.
You can upgrade to CR XI r2 for free here:
If you do go this route, ensure you keep your CR 11.0 ; keycode as you will need it for the XI r2 install. Uninstall CR XI before installing CR XI r2.
If going to CR XI r2 is not an option. I am not sure what SP for CR XI you are on (don't have that info available anymore). Applying SP4 will not hurt:
If that does not help, use the utility called [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx] to determine what is happening when the app is run.
Also, compare the DLLs loading on the 32 bit and 64 bit OS. For the 32 bit OS use the Modules utility from here:
For the 64 bit OS, I will ftp a 64 bit version of Modules for you. Now, there is a bit of a "gotcha" here. The 64 bit Modules does not save the resulting log file, so you will have to do a manual comparison of the 32 bit log and the 64 bit log (e.g.; print them out, compare them on computers sitting side by side, etc.).
The ftp for th 64 bit modules:
Wait about 1/2 hour for the ftp server to finish putting hte file there.
Follow us on Twitter http://twitter.com/SAPCRNetSup