1. Siju Antony
  2. PowerBuilder
  3. Tuesday, 30 November 2021 23:48 PM UTC

Powerbuilder 2017 R3 Application Frequently crashing/Freezing in Windows 10 Computer.


Windows Event viewer shows the below error messages

Faulting application name: whs.exe, version:, time stamp: 0x5b6318c2
Faulting module name: OLEACC.dll, version: 7.2.19041.746, time stamp: 0x226b3f7b
Exception code: 0xc0000005
Fault offset: 0x00018922
Faulting process id: 0x1624
Faulting application start time: 0x01d7e0afd1b16abb
Faulting application path: C:\Pathfinder\EXE\whs.exe
Faulting module path: C:\WINDOWS\SYSTEM32\OLEACC.dll
Report Id: 340cd1ad-264a-4987-b417-d758f0baf817


Done the below recommended settings, however the issue still exists.

Settings -> Ease of Acess -> Magnifier.
1. Turn off the Magnifier
2. Turn of the Magnifier view
    Keyboard focus
    Text Insertion Point

Attachments (1)
Aron Cox Accepted Answer Pending Moderation
  1. Tuesday, 14 December 2021 12:10 PM UTC
  2. PowerBuilder
  3. # 1

Bit late here, but seeing as I just fixed one of these for a customer I thought I'd post mu solution.

As stated by Chris it was Windows Magnifier related, however Windows Magnifier was not turned on. I ended up goiong to the magnifier settings in Ease of Access in the Windows settings and setting the zoom level to 100%. It was set to 200%. This appeared to resolve the issue and the user no longer crashed every time she tried to do anything in our PowerBuilder application.

  1. Chris Pollach @Appeon
  2. Tuesday, 14 December 2021 12:34 PM UTC
Hi Aron;

Thanks for the feedback. Yes, the magnifier or the zoom setting can create instability. I'm not sure why though but this has been an issue for a while now.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 1 December 2021 15:32 PM UTC
  2. PowerBuilder
  3. # 2

Hi Siju;

   The  0xc000041d error code relates to ....



Regards ... Chris

There are no comments made yet.
Siju Antony Accepted Answer Pending Moderation
  1. Wednesday, 1 December 2021 13:34 PM UTC
  2. PowerBuilder
  3. # 3

Hi Olan,


Thanks. Let me try as you suggested.



There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Wednesday, 1 December 2021 00:07 AM UTC
  2. PowerBuilder
  3. # 4

I'm sure you've already done this, but on the off chance you have not yet done so:

1. Do a full REBUILD of your app.
2. Re-deploy your app.
3. Ensure that all required DLLs and all required PBS, and the EXE are included in the deployment.

4. Collect all required files, DLL, INI, PBD into a single folder called TEST on the target Windows 10 computer
5. Run the app from the TEST folder.
6. If the issues vanish, you know you have a deployment issue and you can maually replace the deployed files with the contents of the TEST folder.

7. If you are still having crash issues, copy the TEST folder into a new TEST2 folder on the target Windows 10 computer
8. Return to the 2017 folder on your development PC and grab EVERY DLL and put it into the TEST2 folder

   - I'm using 2019R3, so I would grab all the DLLs from:
              C:\Program Files (x86)\Appeon\PowerBuilder 19.0    and  
              C:\Program Files (x86)\Appeon\PowerBuilderCompiler 19.0

9. Test again.
10. If the problem vanishes, you are missing at least one DLL.
     If the problem recurs, try repeating steps 1 - 10 on a different target platform.

Good Luck,


  1. Krithika BS
  2. Wednesday, 1 December 2021 08:04 AM UTC
One more thing is to remove all runtime files from previous 2017 (R1, R2) version, if any.
  1. Helpful 2
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.