Kbase P88645: Report Builder Runtime Engine PRORE32 GPFs on OpenEdge 10
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  3/24/2010 |
|
Status: Verified
SYMPTOM(s):
Report Builder Runtime Engine PRORE32 GPFs on OpenEdge 10
Report Builder Runtime Engine PRORE32 crashes on OpenEdge 10
Runtime Engine crashes when generating a report
Stack trace generated by the Runtime Engine can vary
Stack trace from PRORE32 reads:
RtlAllocateHeap
prore32.exe
prore32.exe
Stack trace from PRORE32 reads:
RtlRestoreLastWin32Error
prore32.exe
Stack trace from PRORE32 reads:
wcsncpy
prore32.exe
FACT(s) (Environment):
All reports are affected by the problem
Working in a UTF-8 environment
-CPINTERNAL is set to UTF-8
-CPSTREAM is set to UTF-8
OpenEdge 10.x
Windows
CAUSE:
Report Builder does not support UTF-8. If Report Builder picks up a -CPINTERNAL UTF-8 (from STARTUP.PF for example) then it will crash.
FIX:
Set -CPINTERNAL and -CPSTREAM to an alternative codepage in the Report Builder database connection parameters i.e.
-CPINTERNAL 1252
-CPSTREAM 1252
To set these parameters for Report Builder only (i.e. so they do not affect the normal Progress client):
Option #1
Create the file RBSTART.PF in DLC and add the -CPINTERNAL -CPSTREAM parameters, setting them to a non-UTF-8 codepage.
Option #2
Create a new .PF file containing -CPINTERNAL -CPSTREAM parameters set to a non-UTF-8 codepage.
Create an environment variable at operating system level with the following details:
Variable name: RBSTARTUP
Variable value: <path to new .PF file>