P
pauldownie
Guest
Thanks Paul. It is running and registered. Querying the Nameserver reminded me that the Adminserver is not running on the default port. but that shouldn't matter should it? It looks like the "Data Service odbbrokertest not found at NameServer..." error I was getting was after trying an alternate value (the logical name defined in the schema holder) for the -db parameter for the DSN. Running with -db set to the data source name returns "non-PROGRESS database test1 unknown. (1008)". Sorry for the mistake. I should add that running that connect statement also fails with the same error on the server. If I just run the connect shDB -H w2k3DS -S portion it will connect when you run a procedure referencing the database. That is not the case on the client. If I run that it will connect to the SH and the data dictionary will show the schema for the ODBC database but running a procedure referencing the ODBC database returns the error S1000: [Microsoft][ODBC Microsoft Access Driver] Could not find file '(unknown)'. Paul
Continue reading...
Continue reading...