ORA-28040 no matching authentication protocol (.NET 11G Client to 12C) — oracle-tech

    Forum Stats

  • 3,716,127 Users
  • 2,242,960 Discussions
  • 7,845,836 Comments

Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

ORA-28040 no matching authentication protocol (.NET 11G Client to 12C)

user563960
user563960 Member Posts: 3
edited August 2019 in ODP.NET

I have multiple .NET Apps and we want to connect to Oracle 12c using 11g client.  From what I have read it is compatible.

I am getting ORA-28040 no matching authentication protocol  each time I try to connect to 12c.

I read posts online about updating SQLNET.ora file (to include the items below) but does that apply to .NET or just JDBC?

SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8

SQLNET.ALLOWED_LOGON_VERSION_CLIENT = 8

SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8

Best Answer

  • user563960
    user563960 Member Posts: 3
    edited August 2019 Accepted Answer

    Following up with the resolution.


    On our Windows development machines we had both 11.2 and 12.2 clients. On our production servers installing both cause issues in both apps that uses 11.2 ODAC and 12.2 ODAC.  After many many attempts to uninstall, reinstall the only thing worked was removing 11.2 and installing 12.2 only. The .NET apps that had the 11.2 DDL still worked calling the 12.2 ODAC.  Going forward we are going to use the Oracle Instant Client to move away from the installed ODAC clients.

Answers

  • Alex Keh-Oracle
    Alex Keh-Oracle Posts: 2,753 Employee
    edited August 2019

    If the root cause is the same, then the answer to your question is yes. SQL*Net is Oracle's networking software and is generic to both thick JDBC and unmanaged ODP.NET.

  • user563960
    user563960 Member Posts: 3
    edited August 2019 Accepted Answer

    Following up with the resolution.


    On our Windows development machines we had both 11.2 and 12.2 clients. On our production servers installing both cause issues in both apps that uses 11.2 ODAC and 12.2 ODAC.  After many many attempts to uninstall, reinstall the only thing worked was removing 11.2 and installing 12.2 only. The .NET apps that had the 11.2 DDL still worked calling the 12.2 ODAC.  Going forward we are going to use the Oracle Instant Client to move away from the installed ODAC clients.

Sign In or Register to comment.