a customer of our is running our PowerBuilder application on a Windows Server 2016 Terminal Server and reported that after a while users randomly cannot print anymore.
When they restart our application, they can print again.
Important: All of the customer's printers are installed locally on the server. The users have not installed client-side printers that are added to the remote session (we are aware that there are other issues on Windows Server 2016 specific to that)
We discovered that every call within the PowerBuilder application that gets or sets the default printer seems to fail: e.g. PrintGetPrinter() seems to return ?
From this moment on, no PowerBuilder printing of DataWindows etc. is possible anymore!
Unfortunately we have no specific observations what is happening on the server that makes the native PowerBuilder functions fail from then on.
As a workaround we tried to choose a different printer within the application and use it. Not working!
While the PowerBuilder printing is not workin anymore, other applications can still print on all installed printers and even a document viewer embedded into our PowerBuilder application can print just fine using its own printing dialog. Only the native PowerBuilder printing functions and dialogs all fail!
Restarting the applications immediately restores printing functionality, but users have to interrupt their work and start over again which is a big issue for them.
Originally, we discovered this using PowerBuilder 2017 Build 1666.
We are aware that a number of issues involving printing in a remote environment on Windows Server 2016 have been addressed and fixed in PowerBuilder 2017 R3 Build 1880, e.g. this spcific to client-side printers attached to the remote session:
We have migrated and tested with PowerBuilder 2017 R3 Build 1880.
Our problem still exists in PowerBuilder 2017 R3 Build 1880!
Has this been addressed?
Is there a bugfix or a workaround that would quickly solve our customer's issue?