Bug 5414

issue with PBD creation 21 November, 2021

Sreerama Harikrishna
09 October, 2020
Product: PowerBuilder Category: Runtime
Version: 2019 Build: 2170
Classification: Publishing: Public
Priority: P1
Status: Verifying Reason:
Communication Status: Waiting for Customer
Mark Lee @Appeon 21 November, 2021
#48
Hi Harikrishana,

We have been trying to keep in touch with you to find out about the resolution of this issue, we would like to continue with our support but without more information, we are in the need to close it in the next 3 working days, according to our internal help support policy but please remember you can always open a new ticket.  

Regards,
Mark Lee
Mark Lee @Appeon 04 November, 2021
#47
Hi Harikrishna,

I'm just touching base with you about this ticket.  
Did we provide you with enough information to resolve this issue?. 

Please let us know if there is something else to support you with.  
Remember that you can always open a new ticket if need it. 

Regards,
Mark Lee
Mark Lee @Appeon 08 July, 2021
#46
Hi Harikrishna,

I would like to check with you if the response provided has been helpful enough to resolve your case. If so, can we proceed to close the ticket?. Otherwise, please let us know if we can provide you with any further assistance, remember that you can always open another ticket any time you need it. 

Regards,
Mark Lee
Mark Lee @Appeon 08 March, 2021
#45
Hi Harikrishna,

Thanks for your feedback!
We have discussed your issue internally, and there is currently no other good solution.
In addition to the previous debugging suggestion, another suggestion is that even if your app uses incremental build instead of full build, we still recommend that you incrementally build and generate all PBD files by creating a project as we did before. And then update all the PBD files on the client end with these new PBD files.

Regards,
Mark Lee
Sreerama Harikrishna 05 March, 2021
#44
appeon_issue_crash.png (86KB)

Hi Mark,

Please find the details below.

For Point  1 : 
 We have generated PBD and EXE with project painter then still we are getting application crash.

For point 2:
Yes, issue is reproducing.
We have generated full build with out fix and incremental build with changes in unicode PB IDE (Provided by Appeon) and replaced single PBD in unicode full build. we got the error message before app crash (error message attached)

Please let me know if you required any other information
Mark Lee @Appeon 05 March, 2021
#43
Hi Harikrishna,

Following are the summary of the meeting yesterday:
1.    We confirmed that you generate the PBD file using the Build Runtime Library method via right-clicking on PBL and then send the updated PBD file to the customer to upgrade the program.
It is suggested you use the PB Project to package and generate the EXE and PBD and see if you can work it around.
 
2.    Due to that the full build case you provided before the meeting is the one with the modified code, so we can't reproduce the issue after replacing the PBD file in the Unicode full build folder with the incremental built one.
We need you to full build your application without the changes in your code, and incremental build the new file using the IDE we provided, and then do the replacement to see if the issue is reproducible.
 
3.    We also verified that you have provided a publicly accessible machine and can use the Remote Debugger tool 'msvsmon.exe' Microsoft provided to do the debug. However, our development team found that we can't use this tool to attach the process list of your machine.
 
This is the first time we use public IP to do the remote debug, it seems that we can only use other tools or VPN to keep both your machine and our development machine into one LAN so that we could do the source code debug. (We also confirmed that it is not possible for you to provide PVN for us.)
 
We are still analyzing why we can't remote debug via the public IP and currently we still can't find out a better solution.
Thus we are wondering whether if you could directly provide an independent VM Cloud machine with a reproducible case for us to debug or directly provide a reproducible case for us to further analyze.
 
Sorry for the inconvenience caused.

Regards,
Mark Lee
Mark Lee @Appeon 03 March, 2021
#42
Hi Harikrishna,

Sorry that we can't attend the meeting today due to some problems on our side.
And thanks for rescheduling the meeting for the same time tomorrow.

Just a reminder, please make sure you have your IT guys configure port 4015 so that we could access your machine and remote debug via this port.

Regards,
Mark Lee
Sreerama Harikrishna 02 March, 2021
#41
Hi Mark,

i am in the process of full build from unicode_2170 folder.
Please find the below meeting link for tomorrow.

https://oracle.zoom.us/my/vkrish?pwd=OWtQU0dpVmtMYTdlTDRCWmlUQXRDZz09


Regards,
Harikrishna.S
Mark Lee @Appeon 02 March, 2021
#40
Hi Harikrishna,

Thanks for joining the meeting.
We will need you to do the following before the meeting tomorrow.
1.    Full build your app and deploy the project in the PB190.exe in the unicode_2170 folder.
2.    Copy the newly generated EXE, PBD files, and other resource files (DLL, OCX or pic, etc.) that your app needs to the unicode_2170 folder.
3.    Copy this whole unicode_2170 folder and the Remote Debugger folder to the publicly accessible machine.
4.    Make sure the publicly accessible machine has the public IP and we can access it via port 4015.
 
After finishing do the above, please send us the meeting link for tomorrow the same time and we can remote debug this issue. Thanks in advance.

Regards,
Mark Lee
Mark Lee @Appeon 02 March, 2021
#39
ftp settings

Hi Harikrishna,

Before the meeting, please download these files (unicode_2170.zip and Remote Debugger.zip ) first:
We have uploaded these files that our developer team could use to debug in PB 2019 Build 2170 in our FTP server (download.appeon.com).
Please use the account Username (hari.krishna.sreerama@oracle.com) to download it.

FTP server: download.appeon.com
Username: hari.krishna.sreerama@oracle.com
Password: It will be sent in a separate email. 

We suggest that you use a FTP Tool (like the free FileZilla client) to connect to the ftp using the settings in the attachment.

Regards,
Mark Lee
Sreerama Harikrishna 26 February, 2021
#38
Hi Mark,

Please find the below zoom link for meeting

https://oracle.zoom.us/my/vkrish?pwd=OWtQU0dpVmtMYTdlTDRCWmlUQXRDZz09


Please let me know if you required more info on this.

Regards,
Harikrishna.S
Mark Lee @Appeon 25 February, 2021
#37
Hi Harikrishna,

Ok, please share the meeting link with us before the meeting. 
If you want us to send you the GoToMeeting link, please let us know. Thanks.

Regards,
Mark Lee
Sreerama Harikrishna 25 February, 2021
#36
Hi Mark,
we are fine with the mentioned timings (March 2nd at 4 PM UTC+8).
and we are using same PB version (2019 Build 2170).

Please let me know if you required any other info.

Regards,
Harikrishna.S
Mark Lee @Appeon 25 February, 2021
#35
Hi Harikrishna,

Our development team can schedule a meeting with you for next week on Tuesday (March 2nd) at 4 PM UTC+8. Is it OK for you?
 
BTW, which PB version we need to debug? Is it still PowerBuilder 2019 Build 2170 or you upgrade to PowerBuilder 2019 Build 2353?
Please make sure your machine is with public access. Thanks in advance.

Regards,
Mark Lee
Mark Lee @Appeon 18 February, 2021
#34
Hi Harikrishna,

Sorry to let you know that our team is not available for a meeting this week. I will update you next Wednesday. Thanks for your understanding!

Regards,
Mark Lee
Sreerama Harikrishna 16 February, 2021
#33
Hi Mark,

Please let me know the your preferable time for remote debug. so that i will send my zoom invite.

Regards,
Harikrishna.S
Sreerama Harikrishna 02 February, 2021
#32
Hi Mark,

As per your initial suggestion to provide a publicly accessible machine if a standalone replicated app was not available, we had spent a lot of time and effort in getting a machine with public access. Can we proceed with the remote debugging of the application and see if anything could be gathered by debugging the application?

As per a comment from on of the user mike S, we understand that there is PB compilation bug in the functions declaration order when doing an incremental build; could the same issue be happening for instance variables also. The least that could be done is, confirm that this is the case for our current predicament.

Incremental builds are critical to us when we face highly critical production issues that has to be fixed with minimal impact to the rest of the systems. The same was working without any issues in PB 7. We are looking for an expedited resolution on this issue from Appeon.
Mark Lee @Appeon 01 February, 2021
#31
Hi Harikrishna,

I agree with Mike S, this bug is similar to ticket 5163.
I also consulted our developer team about this issue, since the issue you reported is not a consistently reproducible issue for all customers and we are not sure how much time it would take for us to find out the root cause of it via remote debugging, so for this issue, I still suggest you provide a reproducible case (with PBT/PBL) to us for further analysis first.
 
If you still want us to remote debug the ticket 5374 issue, please let us know and reply to that ticket. Thanks.

Regards,
Mark Lee
mike S 21 January, 2021
#30
Harikrishna,

When you are doing your incremental build of the PBD, are you using orcascript to do that?  I have NOT had good results using the IDE to do an incremental build since version 11.  If you are not currently using orcascript to do your single pbd builds, then you try that to see if your results are better.

HOWEVER:  
This bug is similar if not the same as the following issue that i had submitted regarding changes to code and doing single PBD builds:
https://www.appeon.com/standardsupport/track/view?id=5163
I reported the problem as the IDE changing the function declaration order, but i would bet it will change the instance variable order as well.
When this occurs, you WILL get crashes.  
This is a new bug in PB added sometime after 12.5.1 (probably 12.6 but maybe in 2017).
Mark Lee @Appeon 18 January, 2021
#29
Hi Prasanth,

Thanks for the update! I am glad to hear that.
We are focusing on releasing PB 2019 R3 GA this week so we don't have any resources to handle this issue for the time being. I will get back to you next Tuesday about whether our developer team can join us to do the remote debug. Thanks for your understanding.

Regards,
Mark Lee
Prasanth Kalivarapu 18 January, 2021
#28
Hi Mark

We have worked with our internal IT team, they provided us a public access which has our application installed as well as the remote debugger.
 Can we schedule a call to walk through the issue and allow you access to that machine via remote debugger?

Let us know your preferable timings.

Thanks 
Prasanth
Mark Lee @Appeon 19 November, 2020
#27
Hi Harikrishna.S,

In this case, the alternatives will be:
1. Provide a reproducible case (with PBT/PBL) to us for analysis.
2. Provide an independent VM Cloud machine with a reproducible case for us to debug. Currently, you can also upload this VM environment to FTP for us to download to our local machine to debug.
 
Otherwise, we have no other solutions at the moment but only to suggest you try upgrading your PB code from PFC framework 7 to PFC framework 2019.

Regards,
Mark Lee
Sreerama Harikrishna 19 November, 2020
#26
Hi Mark Lee,

Thanks for quick response.
As per our internal policy , we are not allowed systems for public access.Please provide any alternatives for remote debug.

Regards,
Harikrishna.S
Mark Lee @Appeon 18 November, 2020
#25
Hi Harikrishna.S,

Thanks for your feedback.
As we have discussed in the previous meeting, we will need the public IP for us to remote to your customer machine for debugging.

We need your customer to provide the public IP and a specified port that can pass through your firewall for us to access the environment to debug the PB app. Sorry, we might not say it clearly before. 

We use the C++ source code developed by PB to implement Remote debugging through the Remote Debugger tool, so if you are not able to provide public or VPN access, we cannot carry out the remote source code debug.

BTW, the Remote Debugger tool comes from Visual Studio and you can find it in the path (default path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Remote Debugger) in the root folder of Visual Studio.

Regards,
Mark Lee
Sreerama Harikrishna 18 November, 2020
#24
Hi,

Please find the details below:

1. The PB version you are currently using? Is it PB 2019 R2 Build 2353?
After we have your confirmation, we will provide a debug source file of the corresponding PB version for you to copy to the machine to be debugged. 

 PowerBuilder 2019 Build 2170

2. Has the remote client machine been enabled for public network IP or VPN access?

-  As we will not be able to provide public or VPN access, we will only be able to share screen on a ZOOM conference. We can navigate in the VS2017 remote debugger as per your directions in the meeting.

3. Is the code you provided for remote debug PB source code or exe and PBD file?

- EXE and PBD files

4. Currently, we have made an appointment with our development team for the remote debug at 15:30 ~ 17:00 (we are in UTC+8). If this time period works for you, then we will further check with the development team for the date.

- Above mentioned time is fine. please let me know the date.
 
5. We would recommend we debug the App Crash issue in ticket 5374 first.

- For ticket 5374, we would need our customer as it is replicated only in their environment. We had a call with them yesterday and they too stated that it would not be possible to provide VPN access or public access. We will request them to install VS2017 remote debugger in their systems so that we can look at ticket 5374 first. If they are not able to do the required setup by then, we will look at ticket 5414 first.

Regards,
Harikrishna.S
Mark Lee @Appeon 18 November, 2020
#23
Hi Harikrishna.S,

Thanks for your confirmation.
Just in case, may I check with you once more:
1. The PB version you are currently using? Is it PB 2019 R2 Build 2353?
After we have your confirmation, we will provide a debug source file of the corresponding PB version for you to copy to the machine to be debugged. 
2. Has the remote client machine been enabled for public network IP or VPN access?
3. Is the code you provided for remote debug PB source code or exe and PBD file?
4. Currently, we have made an appointment with our development team for the remote debug at 15:30 ~ 17:00 (we are in UTC+8). If this time period works for you, then we will further check with the development team for the date.
5. We would recommend we debug the App Crash issue in ticket 5374 first.

Regards,
Mark Lee
Sreerama Harikrishna 17 November, 2020
#22
Hi Mark Lee,

we have installed 2017 remote debugger for remote debug.
Please let me know the your preferable time for remote debug. so that i will send my zoom invite.
Mark Lee @Appeon 10 November, 2020
#21
Hi Harikrishna.S,

In yesterday’s meeting, we have located the problematic code based on the log files and reproduced the crashing issue of using the instance variable, but once replace the instance variable code with a local variable, the issue didn’t happen.
 
The problematic code is as follows:
IF ib_locfuturedated =false then //(ib_locfuturedated  is instance variable).
 
Since this issue is caused by incremental build, whereas full build doesn't have this issue, we suspect that is because during the incremental build, it doesn't fully compile all objects or may lose some objects.
 
Therefore, we suggest providing a reproducible case for us for further analysis.
If you can’t provide a small case for us, it is suggested you provide a machine that can reproduce it and with the remote tool installed (e.g., TeamViewer) for us so that we could remotely debug it.

Regards,
Mark Lee
Sreerama Harikrishna 05 November, 2020
#20
Hi Mark lee

sent meeting request as mentioned timings.

Thanks,
Harikrishna.S
Mark Lee @Appeon 05 November, 2020
#19
Hi Sreerama,

About the meeting for this issue, I suggest scheduling it on next Tuesday at 4 PM UTC+8.

As discussed in today's meeting, please provide the Zoom link for us for the meeting next Tuesday. And BTW, my email address is Mark.lee@appeon.com.

Regards,
Mark Lee
Sreerama Harikrishna 04 November, 2020
#18
Hi Mark lee

Not possible to provide the application to replicate the issue.

Please let me know the your preferable time for remote debug. so that i will send my zoom invite.
and provide your email address for invitation.
Mark Lee @Appeon 03 November, 2020
#17
Hi Sreerama,

1. I have checked your code but cannot see any major issue(s) that cause the IDE to not build just a PBD properly.
It is recommended that you manually regenerate the query2 instance objects to see if any compile errors occur. And then try again.
2. Based on the PB trace file you provided, we didn’t find any specific issue.
3. Could you try to open the Database Profiles window and then connect with valid database settings in PB IDE, then go to incremental build test it again?
4. Referring to Chris’s suggestion, is there a simple Test Case PB App (with PBT/PBL) that demonstrates this issue that you can attach to this ticket?
 
If you can’t provide a small case for us, it is suggested you provide a machine that can reproduce it and with the remote tool installed (e.g., TeamViewer) for us so that we could remotely debug it.
 
Regards,
Mark Lee
Sreerama Harikrishna 02 November, 2020
#16
Hi, 
please let me know if you have any updates on this issue.
Mark Lee @Appeon 28 October, 2020
#15
Hi Sreerama,

Thanks for report the problem. We are working on it and we will get back to you after analyzing it.
We'll keep you posted here!

Regards,
Mark Lee
Chris Pollach @Appeon 27 October, 2020
#14
Hi Sreerama;
 
  Thank you for the trace file and extra information - including the code snippet. 

  From the trace and the code provided, I cannot see any major issue(s) tat would cause the IDE to not build just a PBD properly.

  I will now transfer this ticket over to the main Support / Engineering for their review and feedback on what might be causing your build issues.

Regards ... Chris
Sreerama Harikrishna 27 October, 2020
#13
tbs.zip (2394KB)

Hi Chris,

I have attached PB trace file for your reference.
And problematic code is pasted below:
code is not navigate to in side the if condtion:
IF ib_locfuturedated =false then (ib_locfuturedated  is instance variable).

code:
loc_futuredated_cnt = query2.of_getresult(1)
destroy query2
IF SQLCA.SQLCode < 0 THEN
              ib_locfuturedated =false
END IF
IF loc_futuredated_cnt = 1 THEN
              ib_locfuturedated =true
else
              ib_locfuturedated =false
END IF
IF ib_locfuturedated = false then

Please let me know your thoughts on this.
Chris Pollach @Appeon 20 October, 2020
#12
Hi Sreerama;
 
  The next steps would be ...

1) provide a simple test case that reproduces the issue

2) run your application through the PB IDE debugger and locate the failing statement(s) if possible.

3) Execute your PB App EXE with a PB Trace to give us more information around the crash.  For example"

  <YourApp.exe>  /pbdebug 

   Please attach the trace file to this ticket.

Regards ... Chris
Sreerama Harikrishna 20 October, 2020
#11
Hi Chris,

we have executed exe with compatibility and Troubleshoot Compatibility options and then still i am facing the same issue.any other solution/workaround i can try?

@Miguel Leeuwe: we have not used any themes in our application.
Miguel Leeuwe 19 October, 2020
#10
Hi Sreerama,
Not sure if true, but I had a major crash the other day while trying to build a single PBD too. 
Are you using "Themes"? As a test: Can you try to temporarily deactivate the use of themes and do the single build again?
Sorry if it has nothing to do, but it's worth giving it a go.
regards and sorry for the interrupt
:)
Chris Pollach @Appeon 19 October, 2020
#9
Hi Sreerama;
 
  Thank you for he mini-dump. I see that the error is in the "PBSHR190" DLL. This module normally handles requests to the O/S on behalf of the PBVM. 

  Can you try using the MS-Windows "compatibilty" feature? Just use the RHMB on your PB App;s EXE and select the "Troubleshoot Comatibilty" option from the pop-up menu in W10 and see what it recommends?

Regards ... Chris
Sreerama Harikrishna 19 October, 2020
#8
Hi Chris

Not possible to provide application for your reference. is there any other suggestion i can try out. can you any thoughts by seeing below event log:

Event log:
Faulting application name: tbs.exe, version: 1.0.0.1, time stamp: 0x5e03ac98
Faulting module name: PBSHR190.dll, version: 19.0.0.2170, time stamp: 0x5e03ac9c
Exception code: 0x80000003
Fault offset: 0x00129250
Faulting process id: 0x31f4
Faulting application start time: 0x01d69e403066300e
Faulting application path: C:\tbs.exe
Faulting module path: C:\PBSHR190.dll
Report Id: f4c9efe9-1676-46a4-8d03-f639452d6a8e
Faulting package full name:
Faulting package-relative application ID:
Chris Pollach @Appeon 15 October, 2020
#7
Hi Sreerama;
 
  Thank you for confirming that this is a multi-developer issue.

  As soon was we have a test case, we can get Engineering involved to further diagnose this issue.  Many thanks in advance!

Regards ... Chris
Sreerama Harikrishna 15 October, 2020
#6
Hi Chris

Thanks for quick response. Yes other developers also getting same issue.i am in the process of creating test application for your reference.
Chris Pollach @Appeon 15 October, 2020
#5
Hi Sreerama;
 
  Thank you for testing the Full Optimize step to see if that cures your incremental build issue.

  I am not able to replicate your issue in mu PB 2019 build 2170 test applications.

  Would have a simple Test Case PB App that demonstrates this issue that you can attach to this ticket?

  Also, are other PB Developers having this issue?

Regards ... Chris
Sreerama Harikrishna 15 October, 2020
#4
Hi Chris

we have done optimize  for all pbl's and full build successfully done. again generated PBD via incremental build for required PBL's .while placing newly generated PBD in application folder then application is getting terminated.

Event log for above crash.

Faulting application name: tbs.exe, version: 1.0.0.1, time stamp: 0x5e03ac98
Faulting module name: PBSHR190.dll, version: 19.0.0.2170, time stamp: 0x5e03ac9c
Exception code: 0x80000003
Fault offset: 0x00129250
Faulting process id: 0x24ac
Faulting application start time: 0x01d6a2d57f7671c9
Faulting application path: C:\test\tbs.exe
Faulting module path: C:\test\PBSHR190.dll
Report Id: 0d00fe7d-a059-4537-9bfc-77f31a5bf909
Faulting package full name:
Faulting package-relative application ID:
Sreerama Harikrishna 09 October, 2020
#3
i am in the process of all PBLs optimization.
Sreerama Harikrishna 09 October, 2020
#2
i have done optimzer for one pbl and created PBD for the same. still i am getting crash( application terminating with out error). 
Event log:
Faulting application name: tbs.exe, version: 1.0.0.1, time stamp: 0x5e03ac98
Faulting module name: PBSHR190.dll, version: 19.0.0.2170, time stamp: 0x5e03ac9c
Exception code: 0x80000003
Fault offset: 0x00129250
Faulting process id: 0x31f4
Faulting application start time: 0x01d69e403066300e
Faulting application path: C:\tbs.exe
Faulting module path: C:\PBSHR190.dll
Report Id: f4c9efe9-1676-46a4-8d03-f639452d6a8e
Faulting package full name:
Faulting package-relative application ID:
Chris Pollach @Appeon 09 October, 2020
#1
Hi Sreerama;
 
 In searching the support database, I have not encountered any such issue in either PB 2017 Rx or PB 2019 Rx releases. 

  The most likely cause could be a corrupt object or a corrupt PBL that is causing this IDE crash. The first recommendation I would have would be to optimize all your PBL libraries within your application. After that, again perform a Full Build. Then try the PBD generation again.

Regards ... Chris
Sreerama Harikrishna 09 October, 2020
*Phenomenon:
While accessing a newly created PBD via incremental build, application is crashing (which contains all PBDS along with newly generated PBD and Exe). Generated only one PBD without generating all PBDs.
After generating FULL Build and copy all PBDS along with Exe application doesn't crash.

In PB7 we didn't faced this kind of issue, where we were able to successfully generate single PBD and replace in our application folder along with other PBDs. Whereas this is not working in PB2019.

our requirement is delivering problematic  PBD to the customer.
OS:
Windows 10
Platform:
All
Database Type:
Oracle
Database Version:
19c