I've hit a problem with a client today and just wondered if anyone knew of a way around this before we log it with PSS.
Basically we have a client who are exclusively still on XP SP3 machines and are connecting to an RDS 2008 SP1 server.
The issue being all of their printers are IPP / internet printers connected in the client and none of these are working.
With a vanilla client they receive the TsWpfWrp crash when printing, and after TsWpfWrp is updated via KB946411 & KB954744 we see no output whatsoever.
I did further deep investigations and found that it appears that TsWpfWrp cannot handle IPP printers.
For example I have an IPP printer mapped which Windows adds to the registry using the following Name value "\\http://10.10.10.10/printer"
When you do a print via EasyPrint to the IPP printer it then results in the following command being run:
tswpfwrp ''\\http://10.10.10.10/printer'' ''test.xps''
Printer :\\http://10.10.10.10\printer
File :test.xps
Error printing:System.Printing.PrintServerException: An exception occurred while creating the PrintServer object. Win32 error: The printer name is invalid.
at System.Printing.PrintServer.Initialize(String path, String[] propertiesFilter, PrinterDefaults printerDefaults)
at System.Printing.PrintServer..ctor(String path)
at TsWpfWrapperNameSpace.TsWpfWrapper.GetPrintQueue(String PrinterFullName)
at TsWpfWrapperNameSpace.TsWpfWrapper.PrintXPSDocument(String printQueueName, String xpsFileName)
at TsWpfWrapperNameSpace.TsWpfWrapper.Main(String[] args)
The printer itself is hosted on a Windows 2003 server with IIS6 and Internet Printing enabled.
If I run the TsWpfWrp command with a standard UNC printer path it works as expected, ie:
tswpfwrp ''\\10.10.10.10\printer'' ''test.xps''
Printer :\\10.10.10.10\printer
File :test.xps
JobQueue was empty, not waiting for printing.
Are there any known workarounds for getting IPP printing working please?
Thanks in advance
Aidan