Re: ORA-12641 with SQLNET.AUTHENTICATION_SERVICES=(NTS)

From: Norbert <iwandraskovic_at_yahoo.de>
Date: 19 Jul 2004 00:43:11 -0700
Message-ID: <8c1a0cde.0407182343.795a9e58@posting.google.com>

iwandraskovic_at_yahoo.de (Norbert) wrote in message news:<8c1a0cde.0407140823.54d6272d_at_posting.google.com>...
> Configuration:
> Database-Server Oracle 8.1.7 Standard Edition on W2K Server
> Application-Server W2K Prof with Oracle 8.1.7-Client connected over
> TCPIP,
> nameresolution via tnsnames.
>
>
> Everytime our process with db-connectivity by OCI starts as a
> windows-service the connect-attempt to the database fails with
> "ORA-12641:TNS:authentication service failed to initialize".
>
> The same process is connecting to the db without problems if we start
> him from the shell (not as a service).
>
> The solution for this problem is to change the
> SQLNET.AUTHENTICATION_SERVICES line in the SQLNET.ORA on the client to
> SQLNET.AUTHENTICATION_SERVICES=(NONE) but our customer is not going to
> accept this because he needs this feature for other applications
> (admin-account to the db with authentication by windows).
>
>
> Here's the sqlnet.ora from server and client (they are the same on
> both machines):
>
> NAMES.DEFAULT_DOMAIN = xx.yy.zz.com
> SQLNET.AUTHENTICATION_SERVICES= (NTS)
> NAMES.DIRECTORY_PATH= (TNSNAMES)
>
> I can't reproduce this problem in my environment, regardless of the
> SQLNET.AUTHENTICATION_SERVICES settings i have no problem to connect
> oracle as
> a service, so any hint will be appreciated.
>
> thanks,
>
> Norbert

Thanks for all replies,

in the meantime we could isolate the problem with the help of a trace. The reason for the 12641-error is the failed loading of the dll "orann8ts.dll".

extract from trace-file:

nau_fad: entry
nau_fad: exit
nau_fad: Windows could not load C:\Oracle\Ora81\bin\orannts8.dll,

maybe the dll is corrupt?

nau_fad: exit
nau_gse: failed with error 12641
nau_gse: exit
nau_cga: failed with error 12641
nau_cga: exit
nau_ccn: failed with error 12641

This dll is only required in conjunction with the setting SQLNET.AUTHENTICATION_SERVICES=NTS in the file sqlnet.ora. The reason for this behaviour must be a wrong patch-level on the client-pc at the customer site.

We solved this problem for us with a local sqlnet.ora in the working directory of our application which overwrites the global setting in ..network/admin/sqlnet.ora SQLNET.AUTHENTICATION_SERVICES=NTS to NONE.

Norbert Received on Mon Jul 19 2004 - 02:43:11 CDT