Questions? Feedback?powered byOlark live chat software

Standard Support

Bug 1732

Default printer redirect on Windows Server 2016 doesn't work for RDS connection 17 October, 2018

Eric Cole
11 October, 2018
Product: PowerBuilder Category: Other
Version: 2017 R3 Publishing: Public
Status: Reproducing Priority: P3
Classification: Sybase (legacy) bug Resolution:
Eric Cole 17 October, 2018
For that setting, it was already off on the server.  It was on on my machine.  I turned it off and tried again and it still didn't work.

I'm not changing the default printer on the server at all.  But yes, I've completely logged off the server and remoted back in and it still doesn't work.

The default printer of my user on the server is "Microsoft Print to PDF".

The default printer of my user on my current machine is "Sybase Datawindow PS".

When I remote into the server on the Remote Desktop Connection app that pops up with options before connecting, on the Local Resources tab, I have Printers checked.

When I remote in, if I go to the Printers & Scanners screen on the server, it shows all the local printers on the server, and all my redirected printers.  And the default printer is the one from the my machine "Sybase Datawindow PS (redirected 13)".  If I remote in and I do NOT have that Printers option checked then none of my local printers show up and the default printer is "Microsoft Print to PDF".

If I try to print anything that pops up a dialog box, when it pops up, the default printer selected is "Microsoft Print to PDF", the default printer of my user on that server, not the redirected default local printer .
Mark Lee 17 October, 2018
let Windows manage my default printer

Hi Eric,

Thanks for feedback this info!
1.      Please confirm if you have removed let Windows manage my default printer.
2.      In my test, when you remote to Windows server 2016, the first time to get the default printer is correct. But it fails the second time.
3.      Can you provide me your detail test steps?
 
BTW, did you restart your app every time you changed your default printer?

Regards,
Mark Lee
Eric Cole 12 October, 2018
(In reply to Mark Lee from comment #2)
Hi Eric,

Thanks for reporting this problem!
Yes, R3 has fixed the issue of ticket 1064.
 
Can you let me know if you are using Win7 32bit machine or Win10 64bit
machine to remote to Windows Server 2016?
We will set up such an environment to verify your scenario.

Regards,
Mark Lee
I'm using Windows 10 64 bit to remote in.
Mark Lee 12 October, 2018
Hi Eric,

Thanks for reporting this problem!
Yes, R3 has fixed the issue of ticket 1064.
 
Can you let me know if you are using Win7 32bit machine or Win10 64bit machine to remote to Windows Server 2016?
We will set up such an environment to verify your scenario.

Regards,
Mark Lee
Govinda Lopez 11 October, 2018
Hi Eric,

I will transfer this ticket to our engineering team for further analysis. We will keep you posted on the results here.


Regards,
Eric Cole 11 October, 2018
*Phenomenon: Running a powerbuilder app on windows server 2016 through a RDP connection and using a redirected local printer as default.  When printing it doesn't print to the default printer if no printer dialog box is used.  If you pop up the printer dialog box the default printer is not selected.


*Reproduce Steps:


Remark:

This is the same as Bug 1064 https://www.appeon.com/standardsupport/search/view?id=1064

But I can't post to that bug and the person who started that one hasn't responded to you yet.

I was hopeful that R3 would fix this issue, but we have upgraded and it still doesn't work.  The redirected local printer is still not the default when the printer dialog pops up.

We're still running our powerbuilder app on windows server 2008 and would really like to upgrade to 2016 but this issue is big for us because we do a lot of printing to the default printer.
OS:
Windows Server 2016 
Platform:
64-bit 
Database Type:
Microsoft SQL Server 
Database Version:
2016 13.0.5026.0