Terminal Services Printing Issue
We have a Delphi 5 application, using RB 7.04 that is having a problem
recognizing a default printer in a Terminal Services environment. The
program is running off TS and the problem occurs with networked printers on
the client side. Local printers (attached directed to the end users
machines) on the client side have no issues.
When a user prints a RB report, they get an error citing No Default Printer
as soon as the Print Preview loads, even though a default printer shows up
in the Desktop. They can then click on the Printer icon in the previewer,
select a printer and successfully output the document.
Oddly enough, we also use the DevEx printer engine in the same application
and DevEx has no issues here - it reads the default printer just fine.
Other applications on the same TS installation have no issues printing.
Contrary some MS documentation, printer names in this client's enterprise
contain spaces, which MS says in a no-no. If we take the spaces out of the
printer names both on the local machines and the TS installed printers, the
problem goes away. The client's position is that having printer names with
spaces works for everything else across the enterprise and should work for
us as well.
If anyone has any ideas on why this combination of things (Terminal
Services, client side networked printers and printer names with spaces) has
an issue with RB but not DevEx or other applications, we would love the
feedback. Any suggests on a work around (like how to save a selected
printer in a users configuration and have it override the Windows Default)
would also be very welcome.
recognizing a default printer in a Terminal Services environment. The
program is running off TS and the problem occurs with networked printers on
the client side. Local printers (attached directed to the end users
machines) on the client side have no issues.
When a user prints a RB report, they get an error citing No Default Printer
as soon as the Print Preview loads, even though a default printer shows up
in the Desktop. They can then click on the Printer icon in the previewer,
select a printer and successfully output the document.
Oddly enough, we also use the DevEx printer engine in the same application
and DevEx has no issues here - it reads the default printer just fine.
Other applications on the same TS installation have no issues printing.
Contrary some MS documentation, printer names in this client's enterprise
contain spaces, which MS says in a no-no. If we take the spaces out of the
printer names both on the local machines and the TS installed printers, the
problem goes away. The client's position is that having printer names with
spaces works for everything else across the enterprise and should work for
us as well.
If anyone has any ideas on why this combination of things (Terminal
Services, client side networked printers and printer names with spaces) has
an issue with RB but not DevEx or other applications, we would love the
feedback. Any suggests on a work around (like how to save a selected
printer in a users configuration and have it override the Windows Default)
would also be very welcome.
This discussion has been closed.
Comments
If anyone has info/experience using RB with Terminal Services, please do not
hesitate to post a reply here.
This question was also sent to support@digital-metaphors.com and was
answered via email.
--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com