OpenEdge 10.2B Graphical Client error

[Chrispo1]

Good Morning,

We are running a database on OpenEdge 10.2B and have recently upgraded our version of OpenEdge. We use a Terminal Services enviroment on Windows Server 2003/Office 2003. We are getting the below message when user's login to Terminal Services:-

OpenEdge Graphical Client encountered a problem and needed to close, do you wish to send this error report to Microsoft

szAppName: prowin32.exe
szModName: prow32.dll

Has anyone come across this message before and if so how to resolve it? We are also getting users reporting issues in using Outlook with it freezing occasionally, our database has a COM link into Outlook, could this be related?

Any help or advice would be appreciated.

Kind Regards,
Chris

 

[adisney]

We have had a similar problem with Windows Server 2008 and OpenEdge 10.2B - have not gotten to the bottom of it, since it doesn't occur consistently in our environment. It occurs when a user logs into our Progress software application. It may be related to some code we have in our startup program:
sessionrinter-name = lv-defaultPrinter no-error.
wapiSetDefaultPrinter(sessionrinter-name).
Apparently the error occurs when the default printer is a remote RTS printer and there is some issue with the printer driver and Windows (perhaps a conflict between the versions on the user's local system and the RTS system).

I know this is vague, but might give you something to pursue - if a user's default Windows printer is something innocuous like a local printer, does the issue still occur, etc.

 

[drago1977]

Good Morning,
We are facing the same issue, on Windows 2008R2 and Windows 7 with OpenEdge 10.2B SP7 and SP5.
Any news how to solve this issue or troubleshoot?


Faulting application path: C:\Progress\OpenEdge\bin\prowin32.exe
Faulting module path: C:\Progress\OpenEdge\bin\prow32.dll

Best Regards,

Bart

 

[gareth.roberts]

Try turning DEP off for the Progress and Office processes.