Kbase P612: Report Builder generates errors 7256 and 1451 when connecting to a Dataserver Unified Broker
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/9/2008 |
|
Status: Verified
SYMPTOM(s):
Report Builder generates errors 7256 and 1451 when connecting to a Unified Dataserver Broker
Unable to establish Unified Broker context. (7256)
Failed to connect to ORACLE database . (1451)
MsgFormatException received on client connection : <MsgFormatException_string> <MsgFormatExceptionMsg_string>. (8083)
Errors occurs when trying to connect Report Builder
Errors are generated when connecting to DataServer Unified Broker from Report Builder (PRORB32.EXE) (in Progress versions 8 & 9) when using the -Dsrv SVUB,1 parameter
Errors are generated when connecting to DataServer Unified Broker from the Report Engine (PRORE32.EXE) ) when using -Dsrv SVUB,1 parameter
Errors 778 and 1451 are generated when removing the -Dsrv SVUB,1 parameter
Error <read/writing> socket, ret=<n>, errno=<n>. (778)
Error reading socket, ret=0, errno=0. (778)
Using Report Builder's Table interface in ABL
Local connections to the DataServer work correctly
Connections via _PROBRKR work correctly
User cannot change the client connection parameters to add -Dsrv SVUB,1
FACT(s) (Environment):
Progress 8.x
Progress 9.x.
OpenEdge 10.x
Windows
CAUSE:
Bug# OE00065419
CAUSE:
Report Builder is unable to connect to non-Progress databases using the DataServer Unified Broker.
As Report Builder is now a Mature product, no further bug fixes, enhancements or add-ons will be provided so this behaviour will not change.
FIX:
Use the command-line DataServer broker (_PROBRKR) rather than DataServer Unified Broker.
Refer to solution P72265 for more information about using the command-line DataServer broker.