Kbase P121684: Running code in a Appserver side split SDO results in error 6456
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/01/2007 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.1x
SYMPTOM(s):
Dynamics Data Logic procedure not started on AppServer if logical name is wrong
Procedure adm2/remotedynsdo.w has not entry point for <procedurename>. (6456).
Procedure <procedure> has no entry point for <internal-procedure>. (6456)
With the stack trace:
icfstart.p (d:\progress\101A\gui\dynamics\icfstart.r) at line 575
processEventProcedure adm2/visual.p (D:\progress\101A\gui\adm2\visual.r) at line 4642
deptNameTrig sports/SDO/departmentviewvsupr.p
(.\sports\SDO\departmentviewvsupr.r) at line 633
--> retDeptnameSplit sports/SDO/departmentfullologcp_cl.p
(.\sports\SDO\departmentfullologcp_cl.r) at line 2235
Code called on sever side of a split SDO fails with error 6456.
Database logical name is not the same as the logical name used to develop the code.
CAUSE:
This is a known issue being investigated by Development
The Logical name of the database used to run the code on the AppServer is not the same as that used to develop the application.
FIX:
Set the -ld parameter for the database the same as the database name used to develop the code.