1. Albert van Bochove
  2. PowerBuilder
  3. Monday, 18 September 2023 18:47 PM UTC

Hello, I have two executables that are part of the same project, here I share the images of the structure of my project, I have the main project which is gefis__application, and I have a second dependent project, whose executable name is: "Claims". It turns out that this is a project that I need to migrate to PB22, and it comes from PB10, but what I can't do is do a correct deploy to the claims subproject, because it gives me the following error " ---------- Deploy: Deploy of aabs (2:58:57 PM)
Invalid executable file name.
---------- Finished Deploy of aabs (2:58:57 PM)
"

Visibly I see the module called gefis_aabs that contains a taget project whose executable file name is claims, how should I fix this?

I already migrated the  gefis__aplication project , converted ok, but when I waht to deploy the subproject tells me the error  "Invalid executable file name". What can be the problem and how to fix it please?

Attachments (1)
Accepted Answer
John Fauss Accepted Answer Pending Moderation
  1. Monday, 18 September 2023 23:11 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi, Albert -

If I may offer a suggestion: The very tall image you included in your post is not readable on my double (side-by-side) monitors... the type size displays very small - Would you please post instead a couple of partial screen shots that show only the pertinent information? Thank you.

Comment
  1. Albert van Bochove
  2. Wednesday, 20 September 2023 12:22 PM UTC
I will send the images separated then, thanks.
  1. Helpful
There are no comments made yet.
Albert van Bochove Accepted Answer Pending Moderation
  1. Thursday, 21 September 2023 17:56 PM UTC
  2. PowerBuilder
  3. # 1

Chris , 

I have removed the path, it was wrongly set but still does not move the project on to a good deployment. 

check the attached image and see how I have  configured my project now and I dont know how to fix the error I get after  rebuild the whole project and pressing Deploy, the error is about not  matching the libraries list. 

 

Also I noticed that I dont have in my project a .pbr file for the AABS project, Should I have it ?

Attachments (1)
Comment
  1. Albert van Bochove
  2. Friday, 22 September 2023 14:39 PM UTC
Is there a way I can create a .pbr file taking as source the project I already have? Because sadly I dont have the .pbr file in the list of files of my project.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 22 September 2023 15:54 PM UTC
If you can remember what external files the old PBR had, you can just use Notepad to create the PBR's item list.

Of course, the best would be to seek the file restoration from a back-up or a source code repository.
  1. Helpful
  1. Albert van Bochove
  2. Friday, 22 September 2023 19:31 PM UTC
well , this is not my case, because I am migrating this project buiilt by other team years ago, and the bck we have does not contains that .pbr file I dont know what can be inside that .pbr file. I will try to rebuild the app from scratch.

  1. Helpful
There are no comments made yet.
Albert van Bochove Accepted Answer Pending Moderation
  1. Wednesday, 20 September 2023 12:26 PM UTC
  2. PowerBuilder
  3. # 2

Hello,

here I am sending the  2 app I have in the same proyect. please look at the attached images.

Attachments (2)
Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 20 September 2023 15:06 PM UTC
Hi Albert;

I see TWO projects - not just one. One for each App EXE.

Regards ... Chris
  1. Helpful 1
  1. Albert van Bochove
  2. Wednesday, 20 September 2023 17:25 PM UTC
ok, sorry, I can be mistaken cosaying the tecnical words according the PowerBuilder development but yes, that is my question there are two proyects , and I need to deploy the aabs one, when I click on Deploy that proyect then I get the "Invalid executable file name", how to fix that? what is the fix that is pointing me that error message?
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 20 September 2023 20:29 PM UTC
Hi Albert;

The AABS project's EXE name looks valid. Though there could be a hidden character in the path / Name somewhere (maybe from from a past PB version migration or from a source code repository update). Try removing the entire Path + EXE name from the project. Then enter an App Name EXE only (no path). Save the Project. Then try a "Deploy" again. HTH

Regards ... Chris
  1. Helpful 1
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.