PowerClient deployment has the following known issues:
-
The virus-detection software such as Avira, McAfee WebAdvisor, BullGuard etc. may block the PowerBuilderRuntime.exe file or CloudAppLauncher.exe during the installation process of the program.
-
Avira: An unsigned Cloud App will be blocked. You may add it to exceptions list and restart your machine to run it successfully. To prevent future false-positive file quarantine, we recommend that you sign your Cloud App first.
-
For resolutions with the other virus-detection software, refer to this article.
-
-
PowerBuilder is designed to be case-insensitive, therefore, if app files are deployed to a case-sensitive system like Linux, some app files (such as images) may not be found or loaded when the application is run. To avoid any issue caused by the case of file name, make sure to configure the Linux server to ignore case-sensitive.
WebBrowser has the following known issues:
-
When an MDI child window which contains the WebBrowser control is opened, and then deactivated and activated, the WebBrowser control may display blank.
-
When the WebBrowser control is opened as an instance of visual user object in a window via OpenUserObject, and then closed via CloseUserObject; and when these steps are repeated for several times, PowerBuilder may crash.
ExtractorObject has the following known issues:
-
If you extract an encrypted file and specify incorrect password, the error code is -10, not -7.
-
The TotalSize in the Start event may not equal to the CompletedSize in the SizeCompleted event.
UI theme has the following known issues:
-
If you have applied a theme to the application via the ApplyTheme function and then selected the "Windows classic style" option when building the application, the application UI will be rendered in a mixture of the applied theme and the Windows classic styles (which is not expected). If you have applied a theme to the application via the Themes tab and then selected the "Windows classic style" option when building the application, the application UI will be rendered in the Windows classic style (which is expected).
-
The RightToLeft and LeftText properties are not effective for RadioButton and CheckBox.
-
When an item is selected from the DropDownPictureListBox, the picture that was displayed will disappear.
The RichTextEdit option "Built-in TX Text Control", which is newly added in version 2019 R3, is a special OEM version of TX Text Control ActiveX X15. The following known issues and unsupported features of RichTextEdit control that affect the "Built-in Rich Text Control" option can be avoided by selecting the newly added "Built-in TX Text Control" option:
-
(Bug ID: 246) RichTextEdit does not allow changing the font programmatically.
-
(Bug ID: 288) DataWindow RichText control does not scale correctly.
-
(Bug ID: 451) Merging the data of two RichTextEdit control into a third one does not work correctly.
-
(Bug ID: 346, 392, 451, 493, 589, 637, 655, 672, 656, 675, 747, 925, 932, 918, 923, 989, 894, 1024, 1117, 1146, 1142, 1334, 1363, 1386, 1421, 1510, 1495, 1496, 1529, 1548, 1624, 1636, 1693, 1687, 1711, 1827, 1836, 1894, 1876) Please check with the support team for any issue that concerns you.
Other known issues:
-
You may fail to install KB2533623 on Windows 7 or Windows Server 2018 R2 as required by Appeon Installer. The error message is either “the update is not applicable” or “the library hostfxr.dll was not found…”. It is a common Windows Update issue. We recommend you find a solution on the Microsoft website according to your environment and the actual error message.
-
After updating 2019 R3 to a new build, the application project created in the previous build still has the runtime path in the application XML pointing to the previous build. Please open the application project settings, and update the "Runtime Path in Application XML" setting in the Run tab.
-
In order to run Web service successfully in 2019 R3, you must add the path of PowerBuilder IDE and PowerBuilder Runtime to the system PATH environment variable, so that the dependent DLL files can be found.
-
SQL Anywhere 17.0.2053 (which is available as the free trial version on the SAP website at the time of writing this document) should not be used if SQL Anywhere stored procedure is used, otherwise the error such as "[Anywhere]syntax near'procedure ?'line 1" may occur. Use a different build (such as 17.0.4.2000 or earlier, or 17.0.4.2088 or later) if SQL Anywhere stored procedure is used.
-
When using regasm.exe (the assembly registration tool provided by Microsoft) to register the DLL file, if the registration failed, there will be no message indicating that.
-
RichText DataWindow that uses the TX Text Control can only support using the Ghostscript distiller (the Distill! method) to save data as PDF file; it does not support using the PDFLib generator (the NativePDF! method).
-
The following functionalities do not work if the computer connects with the Internet through a proxy server requiring user authentication: 1) PowerBuilder online license, 2) PowerBuilder Installer (the online installation program), 3) PowerServer Mobile Templates Manager.
-
If you run PowerBuilder as a guest (not an administrator), you may come across the following license issues: the license login screen may not show the status of the settings correctly; the license file may not be accessed after upgrade; or the new login credentials may not be saved properly.
-
The Help -> PowerBuilder Demo Apps menu will open the https://demo.appeon.com web page which is in English only.
-
The Git detail error messages thrown by the Git server are in English only.
-
The readme file for the SalesDemo application is in English only.
-
When the PBEXAMPLES app is deployed as a 32-bit PowerClient project, the RTE control displays an error, because the RTE control selected for the Application object and the PowerClient project are different.
SnapDevelop has the following known issues:
-
The following areas in the IDE have not been fully localized into Japanese: 1) Syntax service features, 2) Output window, 3) Debug window (including Watch, Local etc.); 4) Git and SVN windows and menus; 5) Close button and tooltips in some windows.
-
Windows 10 version 1607 or later is required if installing SnapDeveloper and its components (.NET DataStore and PowerScript Migrator) using the offline installer, as Microsoft .NET Framework 4.8 supports Windows 10 version 1607 or later.
-
When you launch SnapDevelop from the PowerBuilder IDE to debug C# assemblies, you may find that SnapDevelop may stop responding or the debugger may stop working.
-
In DB Server Explorer, when expanding the SQL Anywhere ODBC demo database that is installed with PowerBuilder, the "Index is outside the bounds of the array" error occurs.
-
For the other known issues, please view here.
