Kbase P187956: Socket error running a query from 10.2B client to 10.2B dataserver
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/31/2011 |
|
Status: Unverified
SYMPTOM(s):
Socket error running a query from 10.2B client to 10.2B dataserver
SYSTEM ERROR: scrl_xidx: index 1 is not in cache. (6222)
Error reading socket, ret=-1, errno=104. (778)
Error reading socket, ret 10054, error=2 (778)
Error triggers occurs when running a query from the client to the remote DataServer
Tested the above test case with below server & client combination:
----------------------------------------------
server client Result
----------------------------------------------
102B03-64 102B-32 Fail
102B04-64 102B-32 Fail
102B-32 102B03-64 Fail
102B-32 102B04-64 Pass
102B03-32 102B-64 Fail
102B04-32 102B-64 Fail
102B-64 102B03-32 Fail
102B-64 102B04-32 Pass
102B03-32 102B-32 Fail
102B04-32 102B-32 Fail
102B03-64 102B-64 Fail
102B04-64 102B-64 Fail
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.2B
Using the remote DataServer configuration
Using the DataServer Unified broker
DataServer running in multi-user mode
Client can succesfully connect to the schema holder and the dataserver schema
Connecting with older client 10.2B to newer 10.2B DataServer
Connecting with newer 10.2B client 10.2B to older 10.2B DataServer
CAUSE:
Bug# OE00202770
CAUSE:
Bug# OE00204739
CAUSE:
New features and fixes introduced in 10.2B broke the connectivity between 10.2B client and 10.2B dataserver with different patch level. OE00202770 adresses the connectivity issue beetween a newer version of a 10.2B client with an older version of a 10.2B DataServer, whereas OE00204739 adresses the connectivity issue beetween an older version of a 10.2B client with a newer version of a 10.2B DataServer.
FIX:
Upgrade client to same version as DataServer schema holder. As a workaround upgrade the client to 10.2B04 where OE00202770 has been fixed. In 10.2B04 the following compatibility matrix applies: ----------------------------------------------
server client Result
----------------------------------------------
102B03-64 102B-32 Fail
102B04-64 102B-32 Fail
102B-32 102B03-64 Fail(OE00202770)
102B-32 102B04-64 Pass(OE00202770 fixed in 102B04)
102B03-32 102B-64 Fail
102B04-32 102B-64 Fail
102B-64 102B03-32 Fail(OE00202770)
102B-64 102B04-32 Pass(OE00202770 fixed in 102B04)
102B03-32 102B-32 Fail
102B04-32 102B-32 Fail
102B03-64 102B-64 Fail
102B04-64 102B-64 Fail