Re: ldap-backend-sql

[Dmitry Kovalev <mitya@seismic.geol.msu.ru>]

suresh wrote:

> thanx for replying.I did replace the dbname with dsn name.I have two
dsn
> name -one which easysoft uses which in turn talks to a system dsn
> (myeasysoft server is on a NT box-so i have two dsn s).I have tried
with
> both.May be i should just shift to openlink so i finish it faster.

Please try a little more, because it would be nice to have OOB
experience, and
people say that OOB is better anyway ;)


> Have yu
> tested with openrda?

Nop. not even heard of ;) Some URLs/descriptions?

>
> Suresh
> this is what happened when i changed the dsn name

> ...
> <==backsql_db_init()
> ==>backsql_db_config()
> <==backsql_db_config(): dbname=demo
> ==>backsql_db_config()
> <==backsql_db_config(): dbuser=sa
> ==>backsql_db_config()
> <==backsql_db_config(): dbpasswd=skipped
> ==>backsql_db_config()
> ...

> Return code: 1
> SQL engine state: 28000
> Native error code: 18456
> Message: [unixODBC][Easysoft ODBC (Server)][Microsoft][ODBC SQL Server

> Driver][S
> QL Server]Login failed for user 'sa'.

see, this is much better ;)



> AND THIS IS WHAT HAPPENED WHEN I REMOVED THE PASSWORD

BTW, I suggest that you change it before some of your local hackers
reads this list ;)

> ...
> load_schema_map(): error preparing oc_query: 'SELECT
> id,name,keytbl,keycol,creat
> e_proc,delete_proc,expect_return FROM ldap_oc_mappings'
> Return code: -1
> SQL engine state: S0002
> Native error code: 208
> Message: [unixODBC][Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid
> object
>  name 'ldap_oc_mappings'.
> SQL engine state: 37000
> Native error code: 8180
> Message: [unixODBC][Microsoft][ODBC SQL Server Driver][SQL
> Server]Statement(s) c
> ould not be prepared.
> ...

This means that you have successfully connected to MSSQL through OOB,
which is
_great_, because people had strange problems at this point (hangs, dead
sockets etc), but your experience shows that nothing prevents one to use
OOB
instead of Openlink or any other ODBC-compliant package).

Now for the error message... I am not a MSSQL guru, but I recall that
this
strange message appears when you try to access a table that you don't
own.

In that case, you should issue something like "select * from
username.tablename", not just "select * from tablename". So, create
those
tables as sa,
or connect as other user, or use back-sql conf directives to redefine
default
queries (see log for directive names ;)

WBW, Dmitry

>
> THANX
>
> SURESH
>
> -----Original Message-----
> From: mitya@samovaar.dot.ru [mailto:mitya@samovaar.dot.ru]On Behalf Of

> Dmitry Kovalev
> Sent: Tuesday, October 10, 2000 2:01 PM
> To: suresh
> Subject: Re: LDAP_MSSQL
>
> >
> > Native error code: 0
> > Message: [unixODBC][Driver Manager]Data source name not found, and
no
> > default dr
> > iver specified
>
> This seems to be the key to your problem. Sorry for historical
> confusion, but dbname actually stands for DSN, so please provide your
> datasource name, not database name there. This was in some of
maillists
> or ITS couple of times, and also noted in instructions, but I feel it
is
> better to add dsn directive instead...
>
> Also note that back-sql was tested with Openlink's package, and so far
I
> had no information about using OOB. So could you please send me kind
of
> walkthrough when you are finished, with OOB-specific things (if you
find
> any), so that I add it to instructions?
>
> WBW, Dmitry