Windows Oracle Data Access Components (MOSC)

MOSC Banner

sqlnet traces: nauztk5ainit: Internal Kerberos error for client init "Matching credential not found"

in Windows Oracle Data Access Components (MOSC) 1 commentAnswered

Im trying to setup OracleClientForMicrosoftTools_x64_19 (19.27) for use in PowerBI Cloud via On-premise Gateway on Windows serwer machine to impersonate users to Oracle Database.
The sqlnet kerberos (KERBEROS5/MSLSA:) configuration works for local PowerBI application, yet started via (PROGRAM=C:\Program?Files\On-premises?data?gateway\m\Microsoft.Mashup.Container.NetFX45.exe) does not, with trace as follows:

nauztk5ainit: Configuration name is "C:\app\oracle_instantclient\instantclient_23_9\network\admin\krb5.conf".
nauztk5ainit: Credential Cache Pathname is "MSLSA:".
nauztk5ainit: Error code for Client Initialization "4".
nauztk5ainit: ZTK Context after initialization "000002213B04C860".

nauztk5ainit: ztk_client_init_context.() failed.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center