Openedge Graphical Client Has Stopped Working

[alexc_]

Hi all,

Has anyone found a fix for the "Openedge Graphical Client has stopped working" error? (screenshot attached). Both local users and users on TS are receiving this.

Currently have tried adding outlook, word, excel, prowin32, pdfsaver to the DEP and re ran OCX's but still no luck.

Currently running Proclaim V3.2, Openedge 10.2b SP5, Aloaha 5 with adobe X.

Has anyone seen this before?.. and found a fix?

Thanks for you help in advance.

[steve]

Hi Alex,
Eclipse support should be able to pinpoint the error - persistance is needed with them if this error is causing disruption to your business, but to help,
which subversion are you on (eg 3.2.10)? Upgrading to the latest release can help - I believe this is around 3.2.12 for general release.
Are there any actions in particular that causes the crash - a particular linked action, viewing PDFs , viewing a particular screen, or maximising/minimising?
Aloaha is being replaced for PDF forms - ask Eclipse for the replacement?
I assume your client PCs and TS all meet the minimum spec?

[alexc_]

Hi steve,

thanks for your reply.

we are running 3.1.12, we were upgraded only last week.. we didn't see these issues beforehand. so must have something to do with it, if not all.

spoken to eclipse support, they cant pinpoint the issue, they just told me to what i have done which is what i mentioned in the post. ill go back to them, probably take them another week or two to come back to me like..

the users could be doing anything in Proclaim, its a very random crash.

thanks for you help.

[steve]

persist with the support technicians - get the job passed up the chain if the one you are speaking to can't either fix it, upgrade you to 3.2, or downgrade you to a previous stable version within the next day. Your firm will be losing revenue due to decreased productivity - pull your weight!

3.2 is mature now - would be interested why they only upgraded you to 3.1.12 recently.

[alexc_]

Sorry we 3.2.12, not 3.1.12, there's only so much you can do with the support technicians. its been escalated anyway.

[steve]

right ok that makes sense. . Do the windows application event logs shed any more details on the crash event - possibly even a module name to give you more clue?
good luck

[Nate]

We haven't been updated to the latest version yet (currently on 3.2.10) but we had a similar issue.
Two things helped and may help you:
Use a lower version of Adobe Reader. (anything but X)
Check your registry if you're using 64bit windows. You will need to add a hex line in the aloaha folder. (it was already done initially but i had to re-do this once we got updated)

[revellbikes]

Interesting that this has reared it's head again!

I'd also maybe enquire with them whether this is a wide spread problem on V3.2.12 as I know it was with some of the earlier versions of V3.2.

Can you post the Windows event log from one of the crashes? This may indicate other underlying issues.

Are you up to date with Windows updates etc aswell?

[alexc_]

Here is the Windows Event Log..

Faulting application name: prowin32.exe, version: 10.2.5.1519, time stamp: 0x4e66659f
Faulting module name: MFC42.DLL, version: 6.6.8064.0, time stamp: 0x4d79b238
Exception code: 0xc0000005
Fault offset: 0x0004229e
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

[revellbikes]

I seem to remember that being the faulting module when I've come across this before.

The progress knowledge base does have records of this error with Prowin32.exe and offers the following resolution:

Give the "Create Global Objects" privilege to the user accounts that are experiencing this issue.

To update the Local User Policy go to Control Panel -> Administrative Tools -> Local Security Policy -> Local Policies -> User Rights Assignment.

May be worth giving this a go? If not - escalate with Eclipse.