• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • How to fix "There is currently no matching version"

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

Resolved How to fix "There is currently no matching version"

  1. How-to
0
Votes
Undo
  1. Olan Knight
    Olan Knight
  2. PowerBuilder
  3. Friday, 19 February 2021 18:57 PM UTC

PB2019R3
Windows 64 bit platform
_______________________________________________

UPDATE:
I copied ALL of the runtime DLLs into the folder, and it worked.
I'm now deleting DLLs one at a time until the error recurs.
The issue was the pbvm.dll. The correct version has a size of 6779 KB, and the version I had was 7457 KB.

_______________________________________________

This is the code we have migrated from 2019R2 into 2019R3. I think I have all of the required DLLs for the application, including all of the required Microsoft and Appeon DLLs.

I used Inno Setup to create the installer, and the ISS file was copied from the 2019R2 versions, with the DLLs modified for R3.

All files, the EX, all DLLs...everything goes into a single folder.






What is causing this and how do I fix it?

 

Searching Google, I found an answer of sorts: Copy the <app_name>.xml file into the same same folder as the other DLLs and modify the path to pointt o where the runtime DLLs reside.

We got the same error (above), THEN we got a NEW error:

PS2021 vs PB2021, what are the differences?
Application Ribbon Menu - Adding Recent Items
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 19 February 2021 19:26 PM UTC
  2. PowerBuilder
  3. # 1

In the application object in Edit Source mode there is a property appruntimeversion. Make sure that is correct.

Comment
Olan Knight
  1. Olan Knight
  2. Friday, 19 February 2021 20:31 PM UTC
Yes, that was the first thing I checked as it would have been somewhat embarrasing to have generated a 64 bit EXE for my 32 bit app!
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 19 February 2021 19:38 PM UTC
  2. PowerBuilder
  3. # 2

Your issue might be caused because you were missing libglog.dll?

 

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 19 February 2021 20:39 PM UTC
Glad to hear you poinpointed the cause, and thanks for sharing the solution!
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Monday, 22 February 2021 13:41 PM UTC
I don't see libglog.dll in my installation either.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 22 February 2021 14:50 PM UTC
Somebody else in a separate post mentioned that caused their issue.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 19 February 2021 21:28 PM UTC
  2. PowerBuilder
  3. # 3

>>copy the <app_name>.xml file ... and modify the path to point to ... runtime DLLs.

if you have the dlls in the same folder as the EXE, then the xml file is NOT needed. 

 

It is now easy to get the correct dlls starting with 2019R3. 

for 32 bit just copy all files from your build version:

   C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.x 

If you are 64 bit, then copy the files from the x64 bit subdirectory instead

 

in both cases you should also copy the thirdpartylegal for, well, legal reasons.

 

then you also have to find and copy the pblab.ini file if you do any datawindow labels.  For some annoying reason appeon insists on NOT putting this one file in the runtime directoryundecided 

 

So, all possible required files except for 1 is located together with only those required files.

 

 

 

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.