1. Larry Gross
  2. PowerBuilder
  3. Thursday, 1 July 2021 23:10 PM UTC

We have been using PowerBuilder 9.0 develop a large application that we normally deploy by coping the new exe into a specific folder on the clients workstation.  Within the application we check to make sure the user has the latest and greatest exe file.  If not we go out and copy the new from a network drive down to the clients workstation.  We do place the required DLLs(never changes) in the same folder.  For our external customers we have the same configuration on a Citrix server and then we publish the application to the external users.

We had everything working and had compiled the application using PowerBuilder 2019 R2 after some trial and errors we were able to figure out which DLLs had to be added to the folder.  Thought we good and were about ready to upgrade everything to PowerBuilder 2019 R3 only to get a new error just before making the major upgrade.  We just upgraded our development environment form R2 to R3 and now we need to figure out how to get past this error.

We are receiving "There is currently no matching version, Lowest Supported Version:19.2.02703" on our Citrix servers. Some posts we read indicate that we might have to place and XML file which has information where the runtime DLLs are stored.  How do we get around this issue.  We really only want to copy the new exe file when updating functionality.  The clients and Citrix servers do not have access to the runtime DLLs.  With our corporate security gurus, we have to have file approved by Black Carbon or the user will get a BIT 9 message and the application crashes.  Is there a simple solution

 

Any and all help would be appreciated.

 

Larry

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 1 July 2021 23:21 PM UTC
  2. PowerBuilder
  3. # 1

Not sure if I understand what you are saying, but if you upgraded PB IDE to 2019 R3 and compiled your EXE with that then you have definitely have to update the runtime DLLs to the 2019 R3 version also.  You cannot keep using the R2 DLLs on the Citrix server.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 2 July 2021 01:54 AM UTC
  2. PowerBuilder
  3. # 2

Hi Larry;

   All the deployment information & how to use the new XML file (which can be omitted BTW depending on your runtime deployment choice) is all precisely documented in the PB Help.

   Just search the help file for the keyword "runtime". That should then present present you a link to the runtime file list & details. This section fully describes each and every DLL that needs to be deployed, DLLs used by PB feature, choices on where to deploy them and details of configuring & using the new XML file from the EXE compilation process.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Larry Gross Accepted Answer Pending Moderation
  1. Tuesday, 6 July 2021 15:13 PM UTC
  2. PowerBuilder
  3. # 3

Thanks,

 

For the clarification, we have not had to change any DLLs up until this R3 release.  We have submitted the listed DLLs for approval for use.  More to follow.

Comment
There are no comments made yet.
Larry Gross Accepted Answer Pending Moderation
  1. Tuesday, 6 July 2021 15:15 PM UTC
  2. PowerBuilder
  3. # 4

Thanks,

 

Have moved past the version error after getting the DLLs approved to be on the network.  Now we are troubleshooting why the new complied application can not connect to the Oracle database.  Assuming we missed a DLL along the line but will keep working at it.

 

Larry

 

Comment
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.