Kbase P182125: Remote DataServer connection from OE Architect causes error 560
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/02/2011 |
|
Status: Unverified
SYMPTOM(s):
Remote DataServer connection from OE Architect causes error 560
Remote DataServer connection from OE Architect causes error 560 as a result connection to MS SQL Server fails
Entry 5 is outside the range of list CRM,, -db <path>/<schemaholder_name>.db -H -S -RO -db <ODBC DSN name> -dt MSS -ld <logical name> -H <DataServer broker host IP> -S ,Dataserver broker port> -Dsrv svub,1. (560)
Entry <entry#> is outside the range of list <list-string>. (560)
FACT(s) (Environment):
Windows
OpenEdge 10.2x
DataServers
CAUSE:
Bug# OE00203866
FIX:
Currently there is no fix for this issue. The workaround is to install OE 10.x DataServer license on the same machine and on the same installation as the OE 10.x Architect and use self-serviced connection instead of the remote DataServer connection.
You can still use client/server connection on the schema holder itself but for the DataServer portion, you can not use DataServer broker.
Example:
On the DB Navigator, you can use the connection to schema holder using -H -S and -N but on the other connection parameter, you just have to use the following if it is windows authentication:
-db <ODBC DSN Name> -dt MSS -ld <logical name>
If not Windows authentication use the following on the other connection parameters section:
-db <ODBC DSN Name> -dt MSS -ld <logical name> -U <SQL Server user name> -P < <SQL Server user password>