通过VBA与Oracle的连接不再起作用

本文介绍了通过VBA与Oracle的连接不再起作用的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我一直在使用此连接字符串:

I have been using this connection string:

fn_Connection_String = "Provider=MSDAORA;Data Source=[address]:1521/orcl;User ID=xxx;Password=xxx"

...并且它一直运行良好.为我的客户工作的IT公司报告说，该客户不再能够使用我的软件，它没有连接到数据库.我使用Oracle工具进行了测试，并且一切似乎都很好，所以我认为问题出在提供程序上.

...and it has been working fine. The IT company that works for my client has reported that the client is unable to use my software any longer, it is not connecting to the database. I test with the Oracle tools and all seems to be well, so I assume the problem is with the provider.

我也尝试过这种方法，但是遇到了相同的错误，但是来自不同的软件:

I tried this as well and was met with the same error but from different software:

fn_Connection_String = "Driver={Microsoft ODBC for Oracle}; " & _ "CONNECTSTRING=(DESCRIPTION=" & _ "(ADDRESS=(PROTOCOL=TCP)" & _ "(HOST=[address])(PORT=1521))" & _ "(CONNECT_DATA=(SERVICE_NAME=orcl))); uid=xxx;pwd=xxx;"

有人知道发生了什么吗?也许某些更新破坏了某些东西，或者人们一直在环境中开玩笑?

Does anyone have a clue what is going on? Maybe some updates broke something, or people have been mucking about in the environment?

似乎旧的ODBC连接不再起作用，并且有一个"oracle in Instantclient"连接器有效，但在VBA中不起作用.

It seems like the old ODBC connection no longer works, and there is an "oracle in instantclient" connector which works, but isn't working in VBA.

我收到的消息是Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these component are installed

编辑 发布后，我发现IT公司安装了2个驱动程序，安装了11版，还安装了Instantclient，安装了12版.我尝试使用"Driver={Oracle in instantclient_12_1}; "(因为这是32位ODBC连接管理器中的驱动程序名称)，但这不起作用.

EDIT After posting I found that the IT company installed 2 drivers, version 11 something, and also instantclient, which is version 12 something. I tried using "Driver={Oracle in instantclient_12_1}; " (Since that is the driver name in the 32 bit ODBC connection manager) but that does not work.

推荐答案

Microsoft在2月9日发布了一个补丁程序，该补丁程序已导致此问题.

Microsoft released a patch on the 9th of Feb, which has been causing this issue.

它现在被列为已知问题.

Its now listed as a known issue.

support.microsoft/en-us/kb/3126587