1. Gary Ault
  2. PowerBuilder
  3. Monday, 13 June 2022 14:24 PM UTC

PowerBuilders,

  I am looking in to PowerClient as a means of deploying our applications. However, I keep getting an error message like the one below when I invoke the "Build&Deploy PowerClient Project" option on my PowerClient project. I am using the SalesDemo application on PB CloudPro edition 2019R3 Build 2703.  I have tried deploying in-house applications as well and I get similar errors related to opening a global function (e.g., f_set_platform). I am deploying to a local server and have tested the file path. Thanks for any insights you may have.

Gary Ault

Connecting to the deployment server…
Publishing the PowerClient app…
Splitting the PBD file "C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example Sales App\Native_PB\Appeon.SalesDemo\salesdemo.pbd"...
Failed to open the file "C:\Users\username\AppData\Local\Temp\pbappscache\temp\SalesDemo\salesdemo.pbd\f_restore_data.fun" in the mode "wb". Error code: 1. Description: Operation not permitted.

Failed to publish the installable cloud app.
 ---------- Finished Deploy of project p_salesdemo_pc   (9:44:39 AM)

Accepted Answer
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 14 June 2022 05:48 AM UTC
  2. PowerBuilder
  3. # Permalink

Did you start PowerBuilder as administrator by checking the "Run as Administrator" option?

Comment
  1. Gary Ault
  2. Wednesday, 15 June 2022 11:48 AM UTC
Thanks, Armeen. I was able to deploy the SalesDemo on another PC by running PB as Administrator. Unfortunately, our corporate environment makes it difficult to run applications as administrator. But that is a procedural issue, not a problem with PowerBuilder.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Wednesday, 15 June 2022 13:20 PM UTC
You should only need Admin privileges on Dev machines using PB IDE. The users of PowerClient app don’t need Admin privileges.
  1. Helpful
There are no comments made yet.
Gary Ault Accepted Answer Pending Moderation
  1. Monday, 13 June 2022 17:15 PM UTC
  2. PowerBuilder
  3. # 1

Ok, I removed the global function and all references to it. Now the application publishes successfully. This limitation suggests that applications that use the PFC must be refactored before they can be published via PowerClient. Anyone else have this experience?

Comment
  1. John Fauss
  2. Monday, 13 June 2022 19:09 PM UTC
Do you ever refresh the PFC/PFE libraries with the latest/new version from GitHub, or do you continually migrate existing, old PFC libraries when you upgrade PB versions? The reason I ask is that the early releases of the PFC f_set_platform function and pfc_n_cst_platform non-visual object contained code to support operating environments that are no longer supported, such as AIX, HPUX, & Solaris. If you are using a version of the PFC libraries that originates from before PB 12.0, I can understand why PowerClient might "choke". Maybe something to consider and/or examine.
  1. Helpful
  1. Gary Ault
  2. Monday, 13 June 2022 19:26 PM UTC
Thanks for the good suggestion, John. We are a little out of date (using PFC 2019), but the f_setplatform version is the same. I can try upgrading the entire PFC and see if that makes a difference.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.