Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved There is currently no matching version Error

  1. Issue
0
Votes
Undo
  1. Randy Bitts
    Randy Bitts
  2. PowerBuilder
  3. Thursday, 15 April 2021 17:30 PM UTC
0
Votes

We are currently upgrading from PB17 to PB19R3 ... I am having an issue on some of my application delivery (Citrix) servers (Windows 2016).

"There is currently no matching version, Lowest Supported Version: 19.2.0.2670

I have five servers, all have the runtime library installed in the same directory, that directory is in the path on the machines.  Runtime is 19.2.0.2670.  Same installer used on all of the servers.  32 bit, just like the compiled code.

On one machine, the application starts perfectly.  On the other 4, I get the "There is currently no matching version" error.

These are all new Citrix servers, no other runtime ever installed on them.  All at the same Windows update level.  Same applications installed on all of them.

Any ideas why 1 works and 4 don't?

I have read a couple of other threads on here, listed below:

https://community.appeon.com/index.php/qna/q-a/pb-2019-r3-there-is-currently-no-matching-version-error

https://community.appeon.com/index.php/qna/q-a/there-is-currently-no-matching-version-lowest-supported-version-19-2-0-2670

The listed/mentioned solutions mention an xml file ... no xml file is on any of the servers - including the one that works.

I have copied the "working" code from the working server to the other servers, doesn't make any difference 

I'm a bit stumped on this at this point ... any ideas from anyone on how to resolve?

Transition GIT Report from 2019 R2 to R3
JWT Authentication request
Accepted Answer
Randy Bitts
Randy Bitts Accepted Answer Pending Moderation
  1. Thursday, 15 April 2021 19:07 PM UTC
  2. PowerBuilder
  3. # Permalink

Resolved ... Microsoft Visual C++ 2010 x86 redistributable was required and missing.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 15 April 2021 21:47 PM UTC
Thanks for sharing the solution! Just FYI, if you use PowerClient it takes care of deploying all these kind of things for you.
  1. Helpful
There are no comments made yet.
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 15 April 2021 17:43 PM UTC
  2. PowerBuilder
  3. # 1

Hi Randy;

  FYI: If you omit deploying the XML file with your PB App EXE, then at App start-up it assumes that it will find the PB runtime DLL's in the same folder as the App EXE - OR - you have added the PB runtime folder (where you installed the runtime from the PB Packager's MSI file) to the O/S's System Path.

HTH

Regards ... Chris

Comment
Randy Bitts
  1. Randy Bitts
  2. Thursday, 15 April 2021 17:49 PM UTC
Runtime is in the PATH ... we have always deployed the application this way, 10+ years now that I've been doing it.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 15 April 2021 17:40 PM UTC
  2. PowerBuilder
  3. # 2

Hi Randy,

There could be a number of config/environment factors where even without the .XML file it will work, but the sure way to get it working is to have the .XML file deployed.  

What I recommend you do is regenerate the application doing full build so that it generates the .XML file for you, and make sure the values in the .XML file are correct.

If after doing full build the .XML file is not being generated, please open a support ticket as it may be a product bug: https://www.appeon.com/standardsupport/newbug

Alternatively, you may want to consider using the new PowerClient deployment option in PB 2019 R3 (Professional or CloudPro Edition).  It will manage not only deploying and updating runtimes but also your application itself.  It also supports incremental updates at an object level and encrypts your app.  Here's more info about PowerClient: https://www.appeon.com/products/power-client

Best regards,
Armeen

Comment
Randy Bitts
  1. Randy Bitts
  2. Thursday, 15 April 2021 17:51 PM UTC
They (the developers) did a new build last night, with the same issue today - works on one server, not on the other 4.



That is the puzzling thing - I have one server that it works perfectly on. It's the other 4, that are all basically mirror images of the working one, that it does not work on
  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.