Just a wild hunch: Is touch-screen active?

Hi Miguel,

there is no touch-screen. Which option do you mean exactly?

Could it be that there's more than one PB run-time on the failing computers?

What happens if you temporarily rename the  "OLEACC.DLL" in the windows system32 folder?

HIH

Hi Benjamin;

    One possible reason ... then OLEACC DLL may not be registered on the odd PC where this is happening.  Have you tried running .... regsrv32 oleacc.dll  ?

Also, make sure that the PBACC170.dll is deployed as well to those PC's where your App is running.

HTH
Regards ... Chris

@Miguel:

We have more than one PB-runtime on our developer computers.

It doesn't work for me, but it works for my colleague without any problems.

Same Windows 10 Pro 1903 with current updates. Same manufacturer.

Older Windows Versions 7 / 8.1 do not have the problem.

I would rather not rename the DLL, because it belongs to the core DLLs of Windows.

@Chris:

The PBACC170.dll is deployed but we have never had to register the OLEACC.DLL before.

Furthermore, the DLL is correctly registered. I checked that.

Ok, so there's more than one runtime on the computers.

The pb program is the same, the OS is the same, so in my opinion there's only one possible difference:

- maybe the path, can you compare the path of a pc on which the program works with the path of a pc where the program crashes? Set the path to the correct runtime to be the first bit of the path and test again.

I wouldn't know what else to suggest, sorry.

Even if we prepare the environment via a VBS script, it behaves differently.

What can't be is that a 32-bit application calls a 64-bit DLL (.\Windows\System32).

By the way, the PowerBuilder IDE also crashes when working with the Windows magnifier and the Datawindow painter. I've worked in this way before to place objects pixel by pixel. And there have never been any problems so far.

So we think that it is primarily a problem with the Windows magnifier, which may be triggered by the PowerBuilder runtime (Datawindow SetItemFocus) or at least conflicts with it. Especially the Datawindow runtime, because windows without a Datawindow control don't crash.

Unfortunately we still don't have a solution except to turn off the options in the Windows magnifier.

Thank you for your ideas so far.

I also checked the PATH folders. All fine.

Good news (for reporting it to Appeon or Microsoft):

I've been able to kind of reproduce the problem several times on my PC, as you can see here (from application log event vierwer). I can't really pin down when it happens but it seems to have something to do with clicking in the title bar

The way to reproduce it:

0) set my display settings of windows to be 125 % scaling instead of 100%. Not sure, because after setting it back to 100% I could still reproduce the problem.

1) open winglass.exe

2) open magnifier by using windowsKey and type magnifier, then click on the app to open it

3) Click once in the title bar of winglass window, while magnifier in full screen and some magnification +500 for example.

4) Click in the title of the floating magnifier windows toolbar. The winglass application closes down ....

5) then check eventviewer logs:

Faulting application name: winglass.exe, version: 1.0.0.1, time stamp: 0x5db1840c
Faulting module name: OLEACC.dll, version: 7.2.18362.1, time stamp: 0xcdf7325e
Exception code: 0xc000041d
Fault offset: 0x00019322
Faulting process id: 0x3cd8
Faulting application start time: 0x01d58b264b221db7
Faulting application path: C:\Users\miguel.LYSANDER\Desktop\WinGlassesTest\winglass.exe
Faulting module path: C:\WINDOWS\SYSTEM32\OLEACC.dll
Report Id: 0eb7c389-70f8-4f76-b433-4a90582f601e
Faulting package full name:
Faulting package-relative application ID:

Then somewhere there's a .wer file with this:

Version=1
EventType=APPCRASH
EventTime=132164761120065322
ReportType=2
Consent=1
UploadTime=132164761123243487
ReportStatus=268435456
ReportIdentifier=38de2746-9548-4f54-a10f-3a9c69b26591
IntegratorReportIdentifier=0eb7c389-70f8-4f76-b433-4a90582f601e
Wow64Host=34404
Wow64Guest=332
NsAppName=winglass.exe
AppSessionGuid=00003cd8-0001-004d-b71d-224b268bd501
TargetAppId=W:00066f79f31db1cfbbf9cd45864349679e1d00000904!0000c1ff1ad51f12a59f5dd72db08ef6befe1a831355!winglass.exe
TargetAppVer=2019//10//24:10:59:24!0!winglass.exe
BootId=4294967295
ServiceSplit=43173440
TargetAsId=5621
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=44d72099c21054f8affc06d91f672c67
Response.BucketTable=1
Response.LegacyBucketId=2304724638911376487
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=winglass.exe
Sig[1].Name=Application Version
Sig[1].Value=1.0.0.1
Sig[2].Name=Application Timestamp
Sig[2].Value=5db1840c
Sig[3].Name=Fault Module Name
Sig[3].Value=OLEACC.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=7.2.18362.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=cdf7325e
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=00019322
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18362.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a977
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a97797f1d1a570f517b515c2e688184d
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=ce9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=ce9e8e251cbfbe86df8b676c1e340a27
UI[2]=C:\Users\miguel.LYSANDER\Desktop\WinGlassesTest\winglass.exe
LoadedModule[0]=C:\Users\miguel.LYSANDER\Desktop\WinGlassesTest\winglass.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\Program Files\AVAST Software\Avast\x86\aswhook.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\System32\USER32.dll
LoadedModule[6]=C:\WINDOWS\System32\win32u.dll
LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[9]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[10]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[11]=D:\Appeon2017\Shared\PowerBuilder\PBSHR170.DLL
LoadedModule[12]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[13]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[14]=C:\WINDOWS\System32\combase.dll
LoadedModule[15]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[16]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[17]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[18]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[19]=C:\WINDOWS\System32\sechost.dll
LoadedModule[20]=C:\WINDOWS\System32\shcore.dll
LoadedModule[21]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[22]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[23]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[24]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[25]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[26]=C:\WINDOWS\System32\profapi.dll
LoadedModule[27]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[28]=C:\WINDOWS\System32\UMPDC.dll
LoadedModule[29]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[30]=C:\WINDOWS\System32\cryptsp.dll
LoadedModule[31]=C:\WINDOWS\System32\ole32.dll
LoadedModule[32]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[33]=D:\Appeon2017\Shared\PowerBuilder\PBVM170.DLL
LoadedModule[34]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.418_none_2e73e95e27897f63\COMCTL32.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[36]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\WSOCK32.dll
LoadedModule[38]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[39]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.418_none_5f5edc43821bf931\gdiplus.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\MSVCR100.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\MSVCP100.dll
LoadedModule[43]=D:\Sybase\Shared\PowerBuilder\libjcc.dll
LoadedModule[44]=D:\Appeon2017\Shared\PowerBuilder\PBUIS170.dll
LoadedModule[45]=C:\WINDOWS\System32\IMM32.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\oledlg.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\UxTheme.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\ATL100.DLL
LoadedModule[50]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[51]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[52]=D:\Sybase\Shared\PowerBuilder\libjutils.dll
LoadedModule[53]=D:\Sybase\Shared\PowerBuilder\libjtml.dll
LoadedModule[54]=D:\Sybase\Shared\PowerBuilder\nlwnsck.dll
LoadedModule[55]=D:\Sybase\Shared\PowerBuilder\libsybunic.dll
LoadedModule[56]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9659_none_d08cfd96442b25cc\MSVCR80.dll
LoadedModule[57]=C:\WINDOWS\SYSTEM32\OLEACC.dll
LoadedModule[58]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[60]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[61]=D:\Appeon2017\Shared\PowerBuilder\pbjson170.dll
LoadedModule[62]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[63]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[64]=D:\Appeon2017\Shared\PowerBuilder\pbdwe170.dll
LoadedModule[65]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll
LoadedModule[67]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll
LoadedModule[68]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll
LoadedModule[69]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[70]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[71]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[72]=C:\Program Files\Bitdefender\Tools\BDAntiRansomware\InjectionDll.dll
LoadedModule[73]=C:\WINDOWS\system32\UIAutomationCore.DLL
LoadedModule[74]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[75]=D:\Appeon2017\Shared\PowerBuilder\pbacc170.dll
LoadedModule[76]=C:\WINDOWS\SYSTEM32\sxs.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18362
OsInfo[3].Key=ubr
OsInfo[3].Value=418
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=2057
OsInfo[7].Key=geoid
OsInfo[7].Value=242
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=1
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=120029
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.418.18362.0-11.0.155
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16257
OsInfo[19].Key=svolsz
OsInfo[19].Value=419
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.418.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=2DBEA21E-0A44-4747-A2EE-416EECF243AD.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=winglass.exe
AppPath=C:\Users\miguel.LYSANDER\Desktop\WinGlassesTest\winglass.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=AC47427CE056363E893C1B74CAEAD483
MetadataHash=-752404674

Here's the .Wer file attached.

Here's a log PML file generated with Process Monitor v3.20 (https://docs.microsoft.com/en-gb/sysinternals/)

See attached in zipped format.

Wow, thank you Miguel!

I hope someone from Appeon will take care of this now. Or should I open a support case?

Hi Benjamin;

   Thank you for opening a Support Ticket on this issue. I was able to reproduce magnifier issues with my own applications as well as yours. While they did not crash when the magnifier was on - the app did not behave at all properly. Like their keyboard, mouse & Windows messages / message queue were being hampered with when the magnifier was active.

  After turning the magnifier off - the same hampered behaviour continued. However, after closing the PB App and then restarting with the magnifier feature off, the PB Apps returned to normal behaviour.

  The that reason my PB Apps might not have crashed could be because I might be using a newer O/S build than you. I am on MS-Windows W10 build 18362.

Regards ... Chris