OE10.2B (32-bit) Graphical Client Stopped Working

Posted by Tai Li on 20-Aug-2015 04:27

Hi All,

I have a client whom have setup the client application on new Laptops (with touchscreen feature) running on Windows 8.1 OS encounters an error as shown below:

These are the Windows Event Viewer log:

Faulting application name: prowin32.exe, version: 10.2.8.1907, time stamp: 0x5282c51d
Faulting module name: comctl32.ocx, version: 6.0.80.22, time stamp: 0x34c80716
Exception code: 0xc0000005
Fault offset: 0x00030b03
Faulting process id: 0x174c
Faulting application start time: 0x01d0d586364655d7
Faulting application path: C:\OpenEdge\bin\prowin32.exe
Faulting module path: C:\Windows\SYSTEM32\comctl32.ocx
Report Id: cb6014db-4179-11e5-828b-0c8bfd782dd1
Faulting package full name:
Faulting package-relative application ID:

I have tested the application on a laptop (without touchscreen feature) on Windows 8.1 OS and is working fine.

What may have been the cause?

Thank you.

Posted by Quintin on 20-Aug-2015 04:44

Good day Tai

We've had a similar problem in the past; I have found that it is the touch screen services that are causing this problem. On the computer with the touch screen ability, you'll need to disable/stop the services of "touch keyboard and hand writing services".  Once you've done this, run the application... If I remember correctly, you could activate the service once you've gone past the point you received the error.

Regards

Posted by Frank Meulblok on 20-Aug-2015 05:36

comctl32.ocx -> that's the Microsoft Common Controls version 5.

See also:

knowledgebase.progress.com/.../000050296 -> for a way to prove if this is a problem with the controls or with OpenEdge.

support.microsoft.com/.../896559 for a potential, but unconfirmed root cause (which affects any treeview / listview control)

All Replies

Posted by James Palmer on 20-Aug-2015 04:35

 
Comctl32.ocx is your problem.
 
James PalmerApplication Developer & DBA
Tel: 01253 785103 | Fax: 01253 785001 | Web: www.inenco.com | Twitter : @inenco
 
 
[collapse]
From: Tai Li [mailto:bounce-tantaili@community.progress.com]
Sent: 20 August 2015 10:28
To: TU.OE.General@community.progress.com
Subject: [Technical Users - OE General] OE10.2B (32-bit) Graphical Client Stopped Working
 
Thread created by Tai Li

Hi All,

I have a client whom have setup the client application on new Laptops (with touchscreen feature) running on Windows 8.1 OS encounters an error as shown below:

These are the Windows Event Viewer log:

Faulting application name: prowin32.exe, version: 10.2.8.1907, time stamp: 0x5282c51d
Faulting module name: comctl32.ocx, version: 6.0.80.22, time stamp: 0x34c80716
Exception code: 0xc0000005
Fault offset: 0x00030b03
Faulting process id: 0x174c
Faulting application start time: 0x01d0d586364655d7
Faulting application path: C:\OpenEdge\bin\prowin32.exe
Faulting module path: C:\Windows\SYSTEM32\comctl32.ocx
Report Id: cb6014db-4179-11e5-828b-0c8bfd782dd1
Faulting package full name:
Faulting package-relative application ID:

I have tested the application on a laptop (without touchscreen feature) on Windows 8.1 OS and is working fine.

What may have been the cause?

Thank you.

Stop receiving emails on this subject.

Flag this post as spam/abuse.




This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
[/collapse]

Posted by Quintin on 20-Aug-2015 04:44

Good day Tai

We've had a similar problem in the past; I have found that it is the touch screen services that are causing this problem. On the computer with the touch screen ability, you'll need to disable/stop the services of "touch keyboard and hand writing services".  Once you've done this, run the application... If I remember correctly, you could activate the service once you've gone past the point you received the error.

Regards

Posted by Frank Meulblok on 20-Aug-2015 05:36

comctl32.ocx -> that's the Microsoft Common Controls version 5.

See also:

knowledgebase.progress.com/.../000050296 -> for a way to prove if this is a problem with the controls or with OpenEdge.

support.microsoft.com/.../896559 for a potential, but unconfirmed root cause (which affects any treeview / listview control)

Posted by Tai Li on 20-Aug-2015 20:27

Thank you all for your help and advises! Have informed my clients, will update back again!

Posted by Tai Li on 21-Aug-2015 04:50

Hi [mention:c6c024a2f8c14320a54920f9914554a4:e9ed411860ed4f2ba0265705b8793d05],

My client have tested, indeed after disabling the 'touchscreen' service, Progress client is able to operate as usual. But just when the service is enabled back, Progress client will throw the error.

For now I will look into the PKB suggestion as mentioned by [mention:2090e04e4bf94975ad7a1cecc79051d2:e9ed411860ed4f2ba0265705b8793d05].

Thanks.

This thread is closed