How to solve ora 28040 error: no matching authentication protocol SQL Server 2012?

Question

Hello, I have the next problem.

In SSMS 2012 I had an oracle 11g linked server, recently this oracle DB has been migrated to oracle 19c, in the server where I'm running SQL Server we installed the Oracle 19c client, so now we have two oracle clients installed, the 11g and the 19c, but now that I try to link this new DB in SSMS it shows the ora 28040 error:

I have read that this could be solved configuring the sqlnet.ora file in the destination server adding the SQLNET.ALLOWED_LOGON_VERSION=8, but I also read that this is more like a workaround and the solution would be to install the new client (the 19c in this case), but now, since I already have installed the 19c client I would like to know how to link this serverver without configuring the sqlnet.ora file in the destination server.

This are the linked server properties

Thank you in advice

Answer 1

That error is an Oracle error. You would probably get a better answer from an Oracle forum.

However, online answers to this question seem to indicate the Oracle JDBC driver needs to be updated in order to connect to v19.
https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html

Answer 2

SSMS is not using any provider - SQL Server is. SSMS is only the frontend tool.

I don't know much about the Oracle providers, but if the two versions have the same name and GUID, you may need to uninstall the old version before you slap on the new one.

Answer 3

Hi @Juan Manuel Eugenio Popoca ,

This is a article for those who encounter similar problems to refer: https://logic.edchen.org/how-to-resolve-ora-28040-no-matching-authentication-protocol/

Best regards,
Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

so now we have two oracle clients installed, the 11g

You may have, but you use OleDB, that's a ActiveX (COM) provider, and only one can be registered on a machine; wellcome to DLL hell: https://en.wikipedia.org/wiki/DLL_Hell

You have to ensure that the new OleDB for Ora 19c is registered.

Answer 5

The error you are receiving indicates the driver you have installed on the SQL Server is not compatible with the Oracle server you are connecting too. SQL Server uses the Oracle client installed on the server. You need to upgrade the client on the server to a client compatible with Oracle 19c.