Bug 6729

Using Perforce source control,- full deploy stop after first target 16 June, 2021

Peoter Veiberman
07 June, 2021
Product: PowerBuilder Category: Third Party Software
Version: 2019 R2 Build: 2353
Classification: Publishing: Public
Priority: P2
Status: Reproducing Reason:
Communication Status: Waiting for Appeon
Ken Guo @Appeon 16 June, 2021
Hi Peoter,

We currently do not have such tools to catch the root cause of this error.

Given the situation of your company (cannot provide the environment to us), we will try to reproduce the issue locally first. If we can reproduce the issue locally, then it will be easy to debug.

Peoter Veiberman 16 June, 2021
Hello Ken,

as I already wrote you in comments for ticket 6728,- we can't expose company machine "out". The only possibility to catch the error (from my POV),- please prepare some toll/dll/LOG's trigger file and send it to me. I'll send you back the LOG after reproducing.
I may need to change some registry definition in order to track this error? Tell me which?
Ken Guo @Appeon 11 June, 2021
Hi Peoter,

From the information you provided, we can’t locate the issue yet.

Since we haven’t been able to reproduce this issue locally, can you help provide us a virtual machine that can reproduce this issue so that we can further analyze the issue? Hope you can understand.

Peoter Veiberman 10 June, 2021

The targets re-arrangement/or adding one-by-one doesn't affect. The build stops always after finishing deploy of first target.
I drew attention to the fact that when deploy is running using batch file + connect to source control,- the activities of "Regenerating ..."  ARE NOT REFLECTED IN OUTPUT PANEL! just in LOG file. I just see below over all the time of deploy:

Connection to source control established
Refreshing source control status........
 ---------- Deploy: Deploy of workspace /my workspace name/   (/time/)
 ---------- Deploy of target /my target name/
 --------- Deploying project /my project name/
Creating executable file . . .
Inspecting Application Dependencies...
Building type ....
Building type ....
the tracking of "Building type" is stopping somewhere in the middle and we see this(although the deploy is not really done):

 ---------- Done Deploy of target /my target name/
 ---------- Finished Deploy of workspace /my workspace name/   (/time/)

and then:

Building type ....
Building type ....

and then it is jumping to Warnings panel without displaying log of "Writing....." lines

It may help for your investigation?
Ken Guo @Appeon 10 June, 2021
Hi Peoter,

Thanks for the feedback.

To further locate the issue, I want to find out if this issue is related to a specific application, so please help try the following:
1. Adjust the order of PBT in PBW. Move the current first PBT to the last. Then try again and see if it works normally.
2. Try and see if it works normally when a PBW contains only one PBT. If yes, then increase it to 2 or 3 PBTs and see if it’s still normal.

Peoter Veiberman 10 June, 2021

It is absolutely works for the same workspace when it isn't connected to source control. All 17 targets is deploying as needed. When connected to source control,- the full deploy is stopped after deploying of first target
Ken Guo @Appeon 10 June, 2021
Hi Peoter,

To locate the cause of this issue, I suggest you try the following:
1. Turn off Source Control in PBW then verify if it works well without Source Control.
2. Create a new PBW containing only one PBT then try again and see if it works.

Chris Pollach @Appeon 09 June, 2021
Hi Peoter;

  Thank you for trying that PB.ini setting and for the SCM log!

  I will now transfer this ticket over to the main Support / Engineering team for their review & feedback on your Perforce issue.

Regards ... Chris
Peoter Veiberman 08 June, 2021
SCM.log (0KB)


update of PB.INI didn't help. SCM log file is attached

Chris Pollach @Appeon 07 June, 2021
Hi Peoter;

Please try adding these to the IDE's PB.ini as follows:

1) Start the PB IDE
2) Proceed to the System Options dialogue (menu: Tools => System options)
3) In the "General" tab page, take note of the "Initialization Path"
4) Close the PB IDE.
5) Locate the folder in File Manager as per step#3
6) Locate & Open the PB.ini file in Notepad
7) Add the following entries as follows:


8) Close an save the PB.ini file changes
9) Restart the IDE.
10) Retry the Perforce SCM process.

Note: If the above does not work, please send us the SCM log file as located in the WorkSpace => RMB => Properties => Source Control tab page => Log File name.

Regards ... Chris
Peoter Veiberman 07 June, 2021
No, I don't have such section in PB.INI. PB.INI was generated automatically when PB was installation. This file wasn't changed manually.
Chris Pollach @Appeon 07 June, 2021
Hi Peoter;

   Do you have the following entries in your PB.ini file used by the PB IDE?


Regards ... Chris
Peoter Veiberman 07 June, 2021
When connecting to Perforce SCM, the full deploy of workspace (having 17 targets) has been stopping  after deploy of first target.
*Reproduce Steps:
 build is executed by batch file below (example!):

pb190 /w D:\CDShop\CDShop.pbw /d /out D:\tmp\cdshop.out

the last lines of cdshop.out is:

Writing /here the path to the last object / . . .
 ---------- Source Control
Serializing SCC Status Cache...
14258 status entries saved in 
\here the path to .pbc file\.
6/7/2021   11:12 Source control terminated
 ---------- Done Source Control

Please let me know if I can send you some LOG file
Windows Server 2019
Database Type:
Database Version: