Microsoft Access Odbc Error

Posted on |

-->

Symptoms

When you try to create an ODBC DSN for drivers that are provided by Microsoft Access in the Data Sources ODBC Administrator, the attempt fails. This problem occurs if you're using a Click-to-Run (C2R) installation of Office. Depending on the version of Office, you may encounter any of the following issues when you try this operation:

  • The ODBC drivers provided by ACEODBC.DLL are not listed in the Select a driver dialog box.

  • You receive a 'The operating system is not presently configured to run this application' error message.

  • You receive an 'Unable to load odbcji32.dll' error message.

  • You receive a 'The driver of this User DSN does not exist. It can only be removed' error message together with the platform showing N/A.

Affected drivers:

  • Microsoft Access Driver (*.mdb, *.accdb)
  • Microsoft Access Text Driver (*.txt, *.csv)
  • Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)
  • Microsoft Access
  • Microsoft Excel
Odbc

Additionally, if you try to define an OLEDB connection from an external application (one that's running outside of Office) by using the Microsoft.ACE.OLEDB.12.0 OLEDB provider, you encounter a 'Provider cannot be found' error when you try to connect to the provider.

Cause

Click-to-Run installations of Office run in an isolated virtual environment on the local operating system. Some applications outside Office may not be aware of where to look for the installation in the isolated environment.

Resolution

On the computer that is running Microsoft SQL Server, open SQL Server Management Studio 2005. To open SQL Server Management Studio: a. Click Start, and then click All Programs. Point to Microsoft SQL Server 2005 or Microsoft SQL Server 2008, and then click SQL Server Management Studio. The Connect to Server window opens. For more information about a problem that occurs when you use ODBC Driver for DB2 to access an IBM DB2 table that has a column name that is 30 characters long, click the following article number to view the article in the Microsoft Knowledge Base. Sep 17, 2018  Note This issue may also occur when you try to open the linked table from other applications that are connected to the SQL Database instance table by using Microsoft Open Database Connectivity (ODBC).

ODBC connections to be used in Office applications

You can work around the issue by creating a DSN from within an Office application, such as Access, instead of using the ODBC Administrator. To create a new DSN in Access, follow these steps:

  1. On the ribbon, select External Data > ODBC Database.
  2. Select Import or Link, and then click OK.
  3. Select the tab for the kind of DSN that you want to create (File Data Source or Machine Data Source), and then click New.
  4. Select the appropriate driver along with any required information to complete the entry.
  5. After the DSN is created, click Cancel to exit the remaining Import/Link steps.
  6. The DSN should now appear in the ODBC Administrator, and you can use it in any Office application.

ODBC or Microsoft.ACE.OLEDB.12.0 OLEDB provider connections that will be used outside of Office

Microsoft Access Odbc Connection Failed Error 3151

Call

You must install an MSI installation of the Microsoft Access Database Engine from one of the following sources so that the calling application can locate the driver and provider.

Note If Office 365 is already installed, side-by-side detection will prevent the installation from proceeding. To install the package, perform a quiet installation by running a command such as the following:

<File location>:<File name> /quiet

For example: C:AccessDatabaseEngine.exe /quiet

Ms Access Odbc Error 3146

Hello,

I have an user who pulls report from third party application (Juris) and is trying to open it via MS Access. He was able to open it until 2 weeks ago. Then when he tries to open the report he gets:

Run-time error '-2147467259 (80004005)': ODBC - connection to 'Juris2' failed.

The file size is 474mb. Microsoft Access version is 2010 and machine OS is Windows 7.

Initially, I chased Juris support for help but after extensive troubleshooting they couldn't help and decide to throw the blame to Microsoft Access. So, at this point they became useless and the only hope for remained to ask in this forum.

Here is what Juris support recommended - Now, the Access report database size is well below the 2Gb limit, the tables have been linked, and the reports run but, not smoothly. The reports run if you open a linked table first but, that’s not the way they should function. My suggestion is for you to contact Microsoft support for assistance.

I am not a database guy and really don't know how to troubleshoot this issue. Please advise or ask questions you have any.

Ms Access Odbc Call Failed Error 3146

Thanks,