1. Brad Wery
  2. PowerBuilder
  3. Tuesday, 7 April 2020 20:50 PM UTC

Hi Everyone,

I'm having some major 64 bit issues. The issue is in both PB2019 and PB12.6, so it must be environment related. It worked before and now it doesn't. To confirm that it's not my coding; I created a new application with 1 window, no code. I open the window in the Application Open event. When I compile as 64 bit, I see the window quickly flash, then it's gone. The process is also gone. Nothing is added to the systems event viewer.

If I add a message box to the open event of my window; I see the message box. Once I dismiss it, the window is closed. If I create a shortcut for the exe and add /PBDEBUG; the window display fine.

I used ProcessExplorer and ProcMon to confirm that all resources (DLL's, Registry, etc.) are all 64 bit. If I put the exe into the Shared\PowerBuilder\x64 directory, the issue persists.

Has anyone seen this before?

Accepted Answer
Brad Wery Accepted Answer Pending Moderation
  1. Sunday, 12 April 2020 17:27 PM UTC
  2. PowerBuilder
  3. # Permalink

It turns out I had some failed Windows updates... I fixed that issue, installed the updates, then PB's 64 bit deploy worked. Weird.

 

Thanks every one.

Comment
  1. Armeen Mazda @Appeon
  2. Sunday, 12 April 2020 19:26 PM UTC
Thanks for sharing the solution! Windows updates are finicky.
  1. Helpful
There are no comments made yet.
Brad Wery Accepted Answer Pending Moderation
  1. Thursday, 9 April 2020 14:03 PM UTC
  2. PowerBuilder
  3. # 1

My hunch, Machine A is loading v5 of the comctl dll. I'm not sure why but that's where I'll start looking.

Comment
  1. Brad Wery
  2. Thursday, 9 April 2020 15:41 PM UTC
Forced app to use ComCtl v6, with a manifest file. No luck.
  1. Helpful
  1. Brad Mettee
  2. Friday, 10 April 2020 13:58 PM UTC
Check that the comctl files differ between 32 & 64bit. I've seen some systems where files were written to the wrong directories and there where 32bit duplicates in the 64bit folder.

  1. Helpful
There are no comments made yet.
Brad Mettee Accepted Answer Pending Moderation
  1. Wednesday, 8 April 2020 13:45 PM UTC
  2. PowerBuilder
  3. # 2

Does anything get added to the Application Event list?

System events should only apply to OS related events, so there shouldn't be anything in there.

You can try enabling the PBVM debugger, it doesn't require /pbdebug to be active, and it should log everything going on in the background (and hopefully not cause the app to work right in the process). Roland has made an NVO available for it here - Freecode PBDebug

 

Comment
  1. Brad Wery
  2. Wednesday, 8 April 2020 14:39 PM UTC
Thanks for pointing me to Rolands NVO. That provided some insight as to what's going on. Note that this is all in PB2019. I added the NVO and enabled all the logging options. I see many calls to the following:



(26) Entering ob_get_obinst_class_hndl

(26) Leaving ob_get_obinst_class_hndl



Then an internal error:



(38) MsgWaitForMultipleObjects WAIT_FAILED - GetLastError() returned: 87, The parameter is incorrect.

(38) Queue(05445EE8) exiting ob_run_dispatch_loop: bExitLoop(0), bExitOnIdle(0), bWaitResult(0) result(00000000)

(38) Queue(05445EE8) ob_run_dispatch_loop:

(38) Queue(05445EE8) exiting ob_run_dispatch_loop: bExitLoop(0), bExitOnIdle(1), bWaitResult(1) result(00040C73)



Now I need to figure out the cause of this. The only thing that's changed on my system (PB related) is updating PB2019. But this shouldn't affect PB12.6.
  1. Helpful
  1. Brad Mettee
  2. Wednesday, 8 April 2020 17:35 PM UTC
It might be worth comparing log file output from your system and having the identical exe run on a diff machine with identical PB on it.
  1. Helpful
  1. Brad Wery
  2. Wednesday, 8 April 2020 19:19 PM UTC
It runs on another machine so definitely related to my environment. I'll have to see what's different between the two machines.
  1. Helpful
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Wednesday, 8 April 2020 07:27 AM UTC
  2. PowerBuilder
  3. # 3

PowerBuilder source code handed over from SAP to Appeon was the PB 12.6 source code.
Therefore expected to find same issue in PB 12.6.

Comment
  1. Brad Wery
  2. Wednesday, 8 April 2020 12:07 PM UTC
I'm aware. As per my comment, same thing is happening in PB2019. It's an environmental issue. I just don't know what changed. It worked a couple months ago ( in all 64 but versions of PB).

  1. Helpful
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Tuesday, 7 April 2020 20:54 PM UTC
  2. PowerBuilder
  3. # 4

sounds like anti virus 

Comment
  1. Brad Wery
  2. Tuesday, 7 April 2020 21:10 PM UTC
I white listed the directory in Norton. No change. Norton also doesn't have anything in the logs for this exe or directory.. To be sure, I disabled it but the issue remains.



Note that 32 bit compile works perfectly fine.
  1. Helpful
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.