×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Unable to print Crystal reports through remote desktop connections, Macola ES 9.6.300

Unable to print Crystal reports through remote desktop connections, Macola ES 9.6.300

Unable to print Crystal reports through remote desktop connections, Macola ES 9.6.300

(OP)
We're having issues with users who connect to our RDS server (w2k8 sp1) in that they receive 'No data which meets the criteria entered' errors while trying to print. These reports print just fine on local machines with the same criteria for printing and with the same user credentials/permissions.

Does anyone know what might cause such an issue? I am not entirely familiar with the server/system side of Macola just yet so please forgive the vagueness!

RE: Unable to print Crystal reports through remote desktop connections, Macola ES 9.6.300

Can you test report with no criteria, if it works, but not with criteria applied, likely an issue with a formula using a dll that is not in addressable by the RDS users. If so you can open the report, help, more info on RDS client and local user and find the missing DLL and add to directory where it would be addressable by the end users. One other note I recently had a similar issue but was a date formatting issue, removed the record selection formula, but added the date formula to my report header and found my issue.

RE: Unable to print Crystal reports through remote desktop connections, Macola ES 9.6.300

(OP)
Thanks NEmacGuy, it was a missing .dll issue. Fortunately I had received an error while testing some event manager reports which gave the .dll name (believe it was U2LE4SYS.dll.) Copied this dll to the sys32 folder on the server and that seems to have resolved the issue.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close