in my case PBC returned

• Create of executable file failed
• Creation of executable failed with a link error

there were no compilation errors, all pbds were created but not the exe file

it turns out the version parameter (/v, /fv, /vn, /fvn) values were incorrectly formatted, instead of "1.2.3.4", "1.2.3" is the cause

I didn't notice this in any of the replies, but...

I've seen this error if there are bad resources in the build, the application icon or resources on PBRs.  Try removing these and if the problem clears.  If so, you'll just need to isolate the offending resource(s).

Phil

I. Since you say you have a colleague who hasn't got the problem, copy all of his code and try again

2. Check which pre-requisites pb2021 needs and make sure they're all there (since it works for 64 bit, I'm thinking maybe some 32 bit framework, c++ runtime or windows sdk if that's still a thing nowadays).

3. As weird as it may sound. In the past there were moments in which I couldn't compile from the project (it would blow up, no error message), but ... doing rightmouse click and choosing 'deploy' worked fine). Might be worth trying again, now that you have a project object in the library.

4. From an administrator command promp (some users have fixed problems doing this):

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

5. If nothing works: I think it would be better to create a support ticket for a question like this: https://www.appeon.com/standardsupport/newbug 

regards.

I had the same issue: "Build of EE failed".

It turned out to be a bad object in the code.
To find such an object that seems to be OK but it not, open each PBL, select each object one at a time, and REGEN it. The bad object will fail.

Yes, this is a slow and annoying thing to do, but it was the only way I found the bad object.


Later -

Olan

The "yyyyyyyy"s in the project are coming from telling it to create pbd files (it adds one "y" for each pbl in the target). I pasted in your modified parameters and as soon as I attempt to save or just build, it automatically updates and adds all of the "yyyyyy"s back in.

Then another thing:

Sometimes I get an executable build failed when my pbt file or the main pbl (where the application object) is. Now to be on the sure site do this:

- make a full copy of everything (also just in case source control might need these write protected attributes).

- right click on the main folder in the file explorer of windows (make sure pb is closed first) and go to "properties", uncheck the "readonly box" and apply to all sub folders.

- try again to build the executable.

Here's an example of my own little project:
/d "D:\_GitHub\PB\OBJETOS pb2021\Objetos_v10.pbt" /o "D:\_GitHub\PB\OBJETOS pb2021\objetos_pb2021.exe" /r "D:\_GitHub\PB\OBJETOS pb2021\objetos.pbr" /w n /m n /x 32 /bg n /p "Objetos Powerbuilder pb2021" /cp "Miguel Leeuwe" /de "Find objects, search by one or two strings, list repeated objects, automatic deletion of repeated datawindows and comparison of 2 versions of an application" /cr "(MIT) You can use it freely" /v "2021.1.0.0" /vn "2021.1.0.0" /fv "2021.1.0.0" /fvn "2021.1.0.0" /ge 0 /pd y /rt 21.0.0.1506

Where the HECK are all of these "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy"s coming from in your project?

Try taking them out and use this instead :

/d "C:\PB21NewTest\SAFE\dcfssafe.pbt" /o "C:\PB21NewTest\SAFE\DCFS\dcfs_applic\dcfssafe.exe" /w n /f /m n /x 32 /bg y /p "SAFE" /cp "Appeon" /de "Appeon Product File" /cr "State of Utah" /v "1.1.1.1" /vn "1.1.1.1" /fv "1.1.1.1" /fvn "1.1.1.1" /ge 0 /pd /rt 21.0.0.1311

Hi, and thanks for responding, Miguel.

I renamed the 64-bit executable and did a 32-bit build with the executable going to the same folder and still got the error.  Note: The 64-bit executable was not showing that it was read-only prior to being renamed.

I also thought it might be that I don't have write access to the output folder for the exe, but I have tried other builds pointing to folders where I know I have write access and still get the same error, and it works to just switch to a 64-bit build and write to the same folder.

We are using a project and I have uploaded a picture of the project settings that includes the error from the build I just tried.  The parameters were not all showing, so I have pasted them below:

/d "C:\PB21NewTest\SAFE\dcfssafe.pbt" /o "C:\PB21NewTest\SAFE\DCFS\dcfs_applic\dcfssafe.exe" /w n /f /m n /x 32 /bg y /p "SAFE" /cp "Appeon" /de "Appeon Product File" /cr "State of Utah" /v "1.1.1.1" /vn "1.1.1.1" /fv "1.1.1.1" /fvn "1.1.1.1" /ge 0 /pd yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy /rt 21.0.0.1311

One thing to note is that when I first tried with my migrated code . . . if I right-clicked on the target and chose Deploy, I would get a message that said no deployable projects were found and asked if I would like to create one, even though I had a project object in the target.  I ended up creating a basic new one and using that to build with.  It has no .pbr file and no icon selected.  

Thanks

I had this same issue when the project I was using was attempting to write the exe to a network shared folder.  When I changed to a local folder it went fine.  From that I assumed it was a permissions issue.

Hi,

Things I can think of: You don't have access rights for the output folder of the EXE. Or, there's already an EXe and it's 'read only'.

How are you generating the exe? Using a project or Powergen?

Show us a picture of your project settings?

regards.