Bug 7139

PB2019R3 - 64Bit App EXE's will NOT execute under the latest W10 release 04 November, 2021

Chris Pollach
19 August, 2021
Product: PowerBuilder Category: Runtime
Version: 2019 R3 Build: 2728
Classification: Appeon bug Publishing: Public
Priority: P3
Status: Closed Reason: FIXED
Mark Lee @Appeon 04 November, 2021
#19
Hi Chris,

Thank you very much for your response!
We then proceed to close this ticket, please remember that you can always open another ticekt in case you need it.
Have a nice day!

Regards,
Mark Lee
Chris Pollach @Appeon 04 November, 2021
#18
Hi Mark;

  The versioning in the THEME.json files looks great!

  You can close this ticket.  ;-)

Regards ... Chris
Mark Lee @Appeon 03 November, 2021
#17
Hi Chris,

We are glad to inform you that PowerBuilder 2021 MR Build 1311 has been officially released. The bug or enhancement you reported in this ticket has been fixed or implemented in this release. Please download and install it to verify it on your side and let us know your feedback soon!
You can get the installer from our Downloads portal at https://account.appeon.com/download (login required). 
 
We welcome all feedback from you!

Regards,
Mark Lee
Chris Pollach @Appeon 27 August, 2021
#16
Sounds good!

My STD Framework Theme version check is working well now. The latest code for the OrderEntry Demo App for PB2021 GA has this code on the SourceForge website as of yesterday.  ;-)
Mark Lee @Appeon 26 August, 2021
#15
Hi Chris,

We will still leave this ticket open because we will fix the problem with the version of the theme.json file and we need you to verify it. Thanks in advance.

Regards,
Mark Lee
Chris Pollach @Appeon 26 August, 2021
#14
Hi Mark;

  Yes, please close this ticket from the crash aspect POV. After cleaning up the W10 registry, things seem to be working well now 64bit EXE wise.

Regards ... Chris
Mark Lee @Appeon 26 August, 2021
#13
Hi Chris,

Thank you for spending time analyzing this issue and sharing the info.
So for the crash issue, we can ignore it for now. 
For the version of the theme.json file, we will update you once the development team fixes it.

Regards,
Mark Lee
Chris Pollach @Appeon 25 August, 2021
#12
Hi Mark;

  Please ignore the previous post. That was for ticket 7140.

  Replacing the THEME file seemed to be only a temporary fix. Installing the latest PB2019R3 MR on my main development PC and running the OrderEntry 64bit EXE there had no issues. So I went back to my TestPC and searched the Registry for any entries with the keyword "OrderEntry64P" (the application EXE name with the crash issue) - deleting all the entries where I found them. Some registry entries to me looked like they might be "Windows Defender" related ones. After this step & rebooting, the 64bit native EXE now compiles OK (EXE was missing the ICO in the EXE - a tell tale sign to me that the O/S was blocking the compilation - thus maybe a malformed EXE) and it also then ran OK as well. So I am now convinced here on Day #2 of retesting, that the TestPC's issue was O/S related. Probably due to the TestPC machine being used to host the various PB2021 beta's. At some point (I think), one of the beta's caused the O/S to mark the 64bit App EXE as one that needs blocking (for some reason). This then perculated back to PB2019R3 as well as the app name was identical.

  The THEME folder version I now think was a "red herring" (as we say in English) as a bogus fix. Somehow copying this folder from the PB20 GA install folder allowed the O/S to trust the 64bit EXE again. However, that was short lived as the 64bit EXE execution crashes returned again the next day. So I think that we can close this ticket on this problem.

  As far as the THEME version checking, I have now implemented my own on the STD Framework. It seems to be working very well to catch this out-of-balance issue. So I will leave it up to you to pursue this as a possible enhancement with the Engineering Team.

  BTW: Thanks for all your time in trying to help me resolve this weird situation!

Regards ... Chris
Chris Pollach @Appeon 25 August, 2021
#11
Hi Mark;

  Replacing the THEME file seemed to be only a temporary fix. Installing PB2021 GA on my main development PC and running the OrderEntry 64bit EXE there had no issues. So I went back to my TestPC and searched the Registry for any entries with the keyword "OrderEntry64P" (the application EXE name with the crash issue) - deleting all the entries where I found them. Some registry entries to me looked like they might be "Windows Defender" related ones. After this step & rebooting, the 64bit native EXE now compiles OK (EXE was missing the ICO in the EXE - a tell tale sign to me that the O/S was blocking the compilation - thus maybe a malformed EXE) and it also then ran OK as well. So I am now convinced here on Day #2 of retesting, that the TestPC's issue was O/S related. Probably due to the machine being used to host the various PB2021 beta's. At some point (I think), one of the beta's caused the O/S to mark the 64bit App EXE as one that needs blocking (for some reason).

  The THEME folder version I now think was a "red herring" (as we say in English) as a bogus fix. Somehow copying this folder from the PB2021 GA install folder allowed the O/S to trust the 64bit EXE again. However, that was short lived as the 64bit EXE execution crashes returned again the next day. So I think that we can close this ticket on this problem.

  As far as the THEME version checking, I have now implemented my own on the STD Framework. It seems to be working very well to catch this out-of-balance issue. So I will leave it up to you to pursue this as a possible enhancement with the Engineering Team.

  BTW: Thanks for all your time in trying to help me resolve this weird situation!

Regards ... Chris
Mark Lee @Appeon 25 August, 2021
#10
Hi Chris,

Thanks for your feedback.
For the crash issue, we still can't reproduce it even though we use the latest Windows 10 (version 21H1 - build 19043.1165).
Can you confirm that this issue is gone after replacing the theme folder and it won't happen again? Could you please let us know the differences between the original theme folder and the updated one?
Since there is a workaround, could you please confirm whether this issue has nothing to do with W10 version 21H1?
 
I had reported a bug internally, this feature will be optimized in the new version. The version in the theme.json file will be updated along with the PB IDE version you installed.
 
BTW, just to confirm that do you want the EXE deployed by PB to autodetect whether the version of theme.json is different from that of the current runtime package and then provide a log or reminder?
If yes, I suggest you reopen a new ticket about this requirement and we will transfer it to the development team to further discuss it. thanks in advance.

Regards,
Mark Lee
Chris Pollach 23 August, 2021
#9
Thanks Mark!
Yes, I think that it would be prudent to have the runtime report this "out-of-balance" situation. It's so easy for Appeon customers to miss this update step and then wonder why the EXE's are crashing so much.
Mark Lee @Appeon 23 August, 2021
#8
Hi Chris,

Thanks for your feedback. I am glad to hear that you found out the cause of it.
For the version of the theme.json file issue, I totally agree with you.
And I will report it as a bug to our development team to fix it.
We will keep you updated if any progress we would make.

Regards,
Mark Lee
Chris Pollach 21 August, 2021
#7
PB2019R3_Theme_Versioning.png (40KB)

Hi Mark;
  I have located the problem that causes the  crashing. Looks like the THEME.json file that comes with the MR is different than the previous build. Whatever the changes in the MR version, it causes the 64 bit App EXE's to crash when activated. Strange though that the 32bit EXE works OK and the 64bit EXE when run as ADMIN works OK as well. That tells me that the PB runtime is handling the THEME.json differently in these modes vs 64bit normal execution.
  When I copy & update the THEME folder from the installation file (see attached), the 64bit EXE now works OK in normal execution mode. So there most be changes to the THEME.json file in this MR -  however, this is NOT listed in the release notes ... http://docs.appeon.com/pb2019r3/release_bulletin_for_pb/Build-2728-MR-BugFixes.html#d0e742
  Also, there is a serious issue here that the PB runtime or even the PB App itself should be able to check the THEME.json file for the correct version that the Theme file relates to (see attachment). Appeon needs to mark the JSON file with the same versioning & build numbers as the PB runtime. That way, either the PB runtime or PB App (or both) can detect any changes and stop if not in sync.
Regards ... Chris
Miguel Leeuwe 21 August, 2021
#6
Hi Chris,
Yes you're right. It doesn't make sense it works okay when running as admin.
Chris Pollach 20 August, 2021
#5
Hi Mark;
  The PB2019R3 version of the STD Framework Demo App is not the exact one that you located on SourceForge - but, its a very close version. 
  I would hold off further testing right now as I am returning from vacation next Monday and will load the R3 MR onto my main PC and test with the latest OrderEntry build for R3 on that machine. Lets see if the same problem occurs on that platform. FYI: My main PC is also now using the latest MS-Windows update however, I am currently testing the MR on my TEST PC. Let's see what happens on Monday.
Regards ... Chris
Chris Pollach 20 August, 2021
#4
Hi Miguel;
  Thanks but that does not make sense as all the 64bit apps run OK when run as ADMIN. No issues. Also, the 64bit App's all ran OK before the PB MR was released and the latest Windows update was applied. Unfortunately, both of these updates have occurred this past week. So to me, going back to the old rule "The last thing that changed is typically the cause of the problem" ... one of these last changes could be the cause.
Regards ... Chris
Miguel Leeuwe 20 August, 2021
#3
Some google points to maybe the registry being corrupt.
https://www.winosbite.com/fix-error-0x80000003/
sfc /scannow ?

Sorry if that's not helpful.
regards.
Mark Lee @Appeon 20 August, 2021
#2
Hi Chris,

I searched for sourceforge.net and just want you to confirm that whether you use the version in the link below to duplicate this issue. Or can you provide a new download link for me to further verify it? Thanks in advance.

https://sourceforge.net/projects/stdfndclass/files/Applications/PowerBuilder/OrderEntry/STD_FC_OrderEntry_v2021R3_PB2019R3_B2703_2021-07-20.zip/download 

Regards,
Mark Lee
Mark Lee @Appeon 20 August, 2021
#1
Hi Chris,

Thanks for reporting this problem.
I will upgrade my Windows 10 from 1909 to the latest version and then verify this issue. I will keep you updated.

Besides, can you provide a reproducible sample test case (including the PBT/PBL) to us for more analysis? Thanks in advance.

Regards,
Mark Lee
Chris Pollach 19 August, 2021
*Phenomenon:  After compiling any 64bit App exe under the latest W10 (version 21H1 - build 19043.1165 - Feature Experience Pack 120.2212.3530.0  ) it will NOT execute. Instead the App will crash at start-up, as follows:
Faulting application name: orderentry64p.exe, version: 2021.3.395.0, time stamp: 0x6100faa2
Faulting module name: PBSHR.dll, version: 19.2.0.2728, time stamp: 0x6100faa9
Exception code: 0x80000003
Fault offset: 0x0000000000175b31
Faulting process id: 0x1b28
Faulting application start time: 0x01d79566d8c64fdb
Faulting application path: C:\Dev\PB2019R3\OrderEntry\Deploy\orderentry64p.exe
Faulting module path: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2728\x64\PBSHR.dll
Report Id: 1d1a9dac-1c57-42d0-ab27-0ed378f1619d
Faulting package full name: 
Faulting package-relative application ID: 

*Reproduce Steps: Compile P-Code App EXE and try to run it.


Remarks: 
Note1:  the 32bit App EXE of the same application works OK
Note2:  The 64bit Apps work OK if run as "Admin".
OS:
Windows 10
Platform:
64-bit
Database Type:
SAP SQL Anywhere
Database Version:
17.0