PowerClient deployment has the following known issues:
-
When configuring a PowerClient project, if you add an image file from a folder to the Images/videos dynamically created section, the folder is added first, and then the image is added into the folder, this is to make sure the project remembers the image path.
-
When configuring a PowerClient project, if you have already added a folder to the other sections (Files preloaded as compressed packages or Files preloaded in uncompressed format), you will not be able to add the same folder to the Images/videos dynamically created section.
-
When you switch to the PowerClient project painter from another painter, the text fields in the PowerClient project painter cannot get focus, unless you click the title or blank area of PowerClient project painter first.
-
When running the application deployed with PowerClient, if any registration fails, the error message will display below the upgrade window, and it will terminate the upgrade process until the OK button on the error message is clicked. Therefore, if the upgrade process seems never ends, please check if any error message is displayed below the upgrade window.
-
If you create a package in the External Files tab for a PowerClient project, and if the package contains a multiple-level folder structure, the package may be missing after you save and close the project. This issue will be fixed in the next release.
-
We have incorrectly classified PB DOM as obsolete in the Runtime Packager and PowerClient project configuration.
-
If the end user computer has enabled proxy server, the “Bypass proxy server for local addresses” option must be selected. Otherwise, applications deployed with PowerClient would fail to run.
-
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.
-
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.
Other known issues:
-
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.
-
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.
-
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.
Please view here.
