View Replies (8)
Printing fails after a while on Windows Server 2016 Terminal Server (Default Printer Issue)
  1. Issue
0 Votes
  1. Alexander Manes
  2. PowerBuilder
  3. Tuesday, 28 May 2019 09:07 AM UTC

Hello,

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:
https://community.appeon.com/index.php/qna/q-a/windows-server-2016-and-default-client-printer

 

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?

 

Thanks.

WS and files PowerBuilder 2019 Oracle 18C connectivity support.
Responses (8)
  1. Likes
  2. Latest
  3. Oldest

Find Questions by Tag

.EXE .NET 6.0 .NET Assembly .NET Core 3.1 .NET Core Framework .NET DataStore .NET Std Framework 32-bit 64-bit ADO.NET AEM AI Algorithm Amazon AWS Android Apache API APK App Store App Store (Apple) Appeon Workspace Appeon Xcelerator Plug-in Architecture Array ASE Asynchronous Methods Authentication AutoBuild AutoCompiler Automated Testing Automation AutoScript Azure Barcode Base64 Batch BigData BLOB Branch & Merge Browser Bug Build Button C# C# Class Importer C# Editor C# Model generator Calendar Camera Certificate Chrome Citrix Class Client Client/Server Cloud Cluster Collection COM Command Line Compiler Compression Computed Field Configuration Controls Cookies Cordova Crash Cross-Platform Crosstab CSharpAssembly CSharpObject CSS CSV Cursor Data Database Database Driver Database Painter Database Profile Database Provider DataObject DataSource DataStore DataStore (C#) DataStore (PS) DataType DataWindow DATE DATETIME DB2 Debug Debugger Debugging Deployment Design DLL DO-WHILE Dockable Docker Documentation DOUBLE Download DragDrop Edge Edit Style Editor Elevate Conference Email Embedded SQL Emulator Encoding Encryption Enhancement Request Entity Entity Framework ERP Error Event Event Handler Event Handling Excel Exception Export Expression External Functions F# Field File File Access Filter Firefox Firewall Font FOR-NEXT Foreground Format Function Garbage Collection GeoLocation Git Graph HANA Hash Header HTML/5 HTTP/S HTTPClient Icon IDE Identity IIS IMAPI Import InfoMaker Inheritance Installation Integer IntelliSense Interface Internet Internet Explorer iOS IPA iPad iPhone IWA J# Java JavaScript JBoss JDBC JOIN JSON JSONGenerator JSONParser Kestrel Label Lambda Large File LDAP Library License LINQ Linux OS Load Balancing Localization Localized PBVM Log In Log Out Logging LONG LONGLONG macOS MAPI Maps MDI Memory Memory Leak Menu Merge MessageBox Messagging Method Migration MIME TYPE Mobile Model ModelStore ModelStore (C#) MSOLEDBSQL Multi Threading MVC MySQL n-Tier Namespace NativePDF NVO OAuth ODATA ODBC Office Offline OLE OLEDB Online Open Source OpenAPI OpenSSL Oracle OrcaScript Other Outlook Output Package Parameter Patch PayPal PB Classic PB Native PB.NET PBC PBD PBDOM PBG PBJVM PBL PBNI PBORCA PBVM PBX PDF Performance Permission PFC Picture Pipeline Play Store (Google) Plugin Popup Port POST PostgreSQL PowerBuilder PowerBuilder (Appeon) PowerBuilder (SAP) PowerBuilder Compiler PowerBuilder Runtime PowerClient PowerScript (PS) PowerScript IDE PowerScript Migrator PowerServer PowerServer Mobile PowerServer Toolkit PowerServer Web PowerServerLabel Print Properties Proxy Publish PULL PUSH Query Regression Release Renew Resize Response REST Retrieve RibbonBar RibbonBar Builder Rich Text Roadmap RPC Runtime Packager SaaS Scaffolding Script SDI SDK Security Server Service Session Single Sign-on Size SMTP SMTPClient SnapDevelop SOAP Sort Source Code Speech Recognition SQL SQL Anywhere SQL Server SqlBuilder SqlExecutor SQLite SqlModelMapper Storage Stored Procedure Subscription SVN Swagger Syntax TabbedBar TabbedView Tablet TabPage Target TE Control Testing Text TFS Theme TIME Timer TLS/SSL Tomcat TortoiseGit TortoiseSVN Transaction Transparency Trial Trigger TRY-CATCH TX Control Type UI ULONG UltraLite Uninstall Unit Test Unit Testing UNIX OS Update Upgrade Upload URL User Center User Object UWP Validation VARCHAR Variable Versioning Visual Studio Visual Studio Code VM Voice Warning WCF Web API Web Extensions Web Service WebBrowser WebForms WebLogic WebSphere WildFly WinAPI Window Windows OS WinForms Wizard Workgroup Workspace WPF XCODE XHTML XML Zoom
✖

Helpful?

If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.