PBAutobuild PB 2022 R3 build failing with no Error info.

View Replies (2)

Resolved PBAutobuild PB 2022 R3 build failing with no Error info.

Issue

0

Votes

Undo

Aleš Vojáček
PowerBuilder
Tuesday, 8 October 2024 16:03 PM UTC

We have same problem as described here: Issue except I do not know nothing about MCVCR100.dll ERROR ( I have no error dialog)

We just Upgrade our application from PB 22 to PB 22 R3 runtime 22.2.0.3391.

Until now (with PB 22 R1 and older runtime) autobuild worked great.

Now when we build application in IDE it is ok, but AutoBuild fails

.......

17:49:20 [Normal] Compiling n_dwr_sub.sru...
17:49:20 [Normal] Compiling n_xls_workbook_v5.sru...
17:49:20 [Normal] Compiling uf_bitxor.srf...
17:49:20 [Normal] Compiling n_dwr_const.sru...
17:49:20 [Normal] Compiling uf_bitor.srf...
17:49:20 [Normal] Calling cm_rebuild_application(CM_REBUILD_FULL).
17:50:05 [Normal] End merging the source code.
17:50:05 [Normal] End processing download source code segment.
17:50:05 [Normal] Start processing compile segment.
17:50:05 [Normal] Start compiling the source code.
17:50:05 [Error]
17:50:05 [Error] Failed to compile the target file. File name: G:\Pracovni\Prodata\PowerBuilder\GIT\Laborka\laborka.pbt

So I do not konw why it fails.

The only change in source code is change to newest runtime.

The only chage in json is only runtime version.

Until now it worked.

Ales

Accepted Answer

Aleš Vojáček Accepted Answer Pending Moderation

Thursday, 10 October 2024 08:42 AM UTC
PowerBuilder
# Permalink

Hi all,

After a while we found a solution (ticket helped a lot even if I did not expect what was the problem).

The problem is that in PB2022R3 there is little change in the json build file.

First thing that I did check after migrating from PB2022R1 to PB2022R3 and problems with PBAutoBuild was the json file. I did generate a new one and I compared those two. I did not find any interesting changes and so I tried almost everything that I can think of. Strange was that there is no error info and we changed only the version of PB and runtime.

Here is what caused that strange behaviour, every line which is ment to be comment in json has to be changed like this

"//Rebuild": "0: Incremental; 1: Full"

instead of

"//": "0: Incremental",
"//": "1: Full"

or removed.

Anyway I think that if something is wrong with the json file (especially when it was OK in previous versions PB 2022 R1 worked with that ok) the Error should not be empty, but describe that there is a problem with the json file ideally what is wrong with that file.

That is it :-(

Ales.

Comment

Armeen Mazda @Appeon
Thursday, 10 October 2024 11:42 AM UTC

Thanks for posting the solution!

Helpful 0

There are no comments made yet.

Responses (2)

Chris Pollach @Appeon Accepted Answer Pending Moderation

Tuesday, 8 October 2024 20:05 PM UTC
PowerBuilder
# 1

Hi Aleš;

For this type of problem, please open a Support Ticket so that the Appeon Support Team can delve a lot deeper into this problem. Just stopping at the message "error" is certainly not useful!

Regards .. Chris

Comment

Aleš Vojáček
Tuesday, 8 October 2024 23:04 PM UTC

So I created a bug report.

https://www.appeon.com/standardsupport/track/view?id=12697

That is strange that it was reported in issue I linked, and there is not how it was solved. But without any error description I have no Idea how to dig into it.

Helpful 0

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.

Please login to post a reply

You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »

Forgot Password?

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.