Microsoft Access Database Driver

17.05.2020by

UPDATE: As informed, the security patches with the fix was rolled-out yesterday 11/14. We would request you to test this and verify that the issue is addressed. If not, please let us know. Please find the information below,

Solution: Need to download the ODBC Driver for Microsoft Access Database. See if this will help. Run C:WINDOWSSysWOW64odbcad32.exe. This should bring the odbc Data source administrator (see if you have the 32 bit drivers listed for Microsoft access ) if you see it, set up your DSN. The Microsoft Access Driver (.mdb.accdb) does not appear in the ODBC Data Source Administrator dialog box when the bitness of the operating system and Microsoft Access is different. This mismatch occurs when you setup a data source for a 32-bit Microsoft Access database using a 64-bit MATLAB. Microsoft Office 2007 introduced a new Microsoft Access database format, ACCDB. When creating a database, ACCDB is the new default format in Access 2007 and Access 2010. Note: The proper way of connecting to Microsoft Access databases, either the MDB or ACCDB formats, is through an OLE DB connection. Using Access I can open ACCDB and MDB files. Yet, if I run the x64 ODBC Drivers component there is NO Microsoft Access Database (.mdb,.accdb) driver listed. The only way I can get it listed is if I install the x64 Access 2013 Runtime. In the list of currently installed programs, select “Microsoft Access database engine 2016” and then click Remove or Add/Remove. If a dialog box appears, follow the instructions to remove the program. Click Yes or OK to confirm that you want to remove the program. Dec 20, 2017  Need to download the ODBC Driver for Microsoft Access Database. Question: Need to download the ODBC Driver for Microsoft Access Database. This should be an easy one, but I’m running out of time and need this asap. I need to download the Microsoft Access ODBC Driver so that I can set up a User DSN that my Java programs can connect too.

Windows 2008

https://support.microsoft.com/en-us/help/4050795/unexpected-error-from-external-database-driver-error-when-you-create-o

Windows 7/2008 R2

-Monthly Roll-up - https://support.microsoft.com/en-us/help/4048957/windows-7-update-kb4048957

-Security-only update - https://support.microsoft.com/en-us/help/4048960/windows-7-update-kb4048960

Windows 2012

-Monthly Roll-up - https://support.microsoft.com/en-us/help/4048959/windows-server-2012-update-kb4048959

-Security-only update - https://support.microsoft.com/en-us/help/4048962/windows-server-2012-update-kb4048962

Windows 8.1 and 2012 R2

-Monthly Roll-up - https://support.microsoft.com/en-us/help/4048958/windows-81-update-kb4048958

-Security-only update - https://support.microsoft.com/en-us/help/4048961/windows-81-update-kb4048961

Windows 10 Fall (“November”) Update, version 1511

-https://support.microsoft.com/en-us/help/4048952

Windows 10 Anniversary Update, version 1607, and Server 2016

-https://support.microsoft.com/en-us/help/4048953

Windows 10 , version 1703

-https://support.microsoft.com/en-us/help/4048954/windows-10-update-kb4048954

We have been seeing a recent influx in cases where the JET provider is no longer able to connect after the October update. This update (released October 10th, 2017) includes a security update release that inadvertently affects the JET provider. The update was kb4041678 and included in the patch kb4041681. These patches affected the Operating System, which adversely has an issue with the following technologies: Microsoft Windows Search Component, Windows kernel-mode drivers, Microsoft Graphics Component, Internet Explorer, Windows kernel, Windows Wireless Networking, Microsoft JET Database Engine, and the Windows SMB Server. It is important to note that the changes were not to these technologies themselves.

Types of errors witnessed:

WORKAROUNDS & SOLUTION:

Approach 1:

Use Microsoft.ACE.OLEDB.12.0 or Microsoft.ACE.OLEDB.16.0: (Recommended)

The following updates where not intended to cause any issue with Microsoft Jet Database Engine 4.0, at the same time the product group developers were not verifying these updates would be compatible with Microsoft Jet Database Engine 4.0 data provider as it had been deprecated back in 2002:

As both articles suggest for the below workaround.

In all current known cases, using the ACE provider works to connect to the excel files in lieu of the JET provider. The following download is the most up to date version for the ACE provider:

Odbc Driver For Ms Access

Microsoft Access Database Engine 2016 Redistributable

When looking into this issue, the largest thing to note is: The JET provider has been deprecated as of 2002. The last changes were made to this in 2000. See the following article for more details.

Data Access Technologies Road Map

Excerpt:

So, in short the JET provider has been working for a good 15 years after deprecation, but this most recent update caused a change which requires an update to how you are connecting to the Excel file. For the SSIS packages, we recommend pointing to the Excel by our Excel connector instead of using OLEDB.

You can locate the Excel Connector by opening up an SSIS package within SQL Server Data Tools. Create or go to an existing Data Flow task. You can see the Excel Source in the “Other Sources” Section:

When using JET, this is done through an OLEDB/ODBC source. You can use the same method for the ACE provider. The ACE provider will work, however it is not supported for use with programs such as SSIS, Management Studio, or other applications. Although this doesn’t tend to cause issues, it is important to note. That notwithstanding, the ACE drives provides the same functionality as the JET provider did. The only limitation I am aware of is the same you were encountering with JET which is that you can't have multiple users connecting to and modifying the Excel file.

Microsoft Access Database Engine 2016 Redistributable

Excerpt:

I understand that there are many users that don’t know how many packages might be experiencing this issue. It is possible to look through your dtsx packages using the following method.

If you run a command prompt as an administrator, you can use the find command to look through the packages for the keyword JET. This will state all the files it looks through, but you will see a connection manager result for the files that have this in them. If you have already updated the package from JET to ACE, then this will not show the connection manager and is not affected by this security update.

In a command prompt:

Download GTA 4 Full Version Game For Pc Free – Super Highly Compressed Torrent: a video game of action, adventure, and combat. It’s also one of the most played games today. Compressed games free download. Download Highly Compressed Hitman 4 in 270 MB. Hitman 4 Highly Compressed game, is a action video game developed by developed by IO Interactive and published by Eidos 15 June 2015.Orignal size of Hitman 4 was in gigabyte, after compression the file size of Hitman 4 Highly Compressed is just270MB. Hitman 4 is firslty tested on our local system and than we upload it for our game lovers.Its. Click below to Download Need for Speed Most Wanted 2012 Highly Compressed NFS Most Wanted 2012 is a 2012 dashing computer game created by Criterion Games and distributed by Electronic Arts for PlayStation 3, Xbox 360, Microsoft Windows, Wii, iOS, Android, webOS and Windows Phone. Download Setup File Super Highly Compressed PC Games 100% Free Download. Super compressed or Ultra Compressed pc games is a game compression that has a very small size. You will get the file with a very small size compared to the normal game file size.

Find /I “Jet” “C:SampleFolderSamplePackage.dtsx”

Alternatively, you can search the whole folder at once:

Find /C /I “Jet” “C:SampleFolder%.dtsx”

For more information on the Find command:

Find: https://technet.microsoft.com/en-us/library/bb490906.aspx?f=255&MSPPError=-2147217396

Additionally after the installing and upgrading to ACE providers, you may run into the following error message,

If you are in a scenario where you have both 32-bit and 64-bit processing being performed on the same server that needs to use the ACE data provider, from the Microsoft standpoint, it is recommended to have 2 different servers (1 to process 32-bit mode and the other for 64-bit mode).

But there is an option (workaround) where you can have both the versions installed on the same machine by performing a “/quiet” install of these components from command line. To do so, download the desired AccessDatabaseEngine.exe or AccessDatabaeEngine_x64.exe to your PC, open an administrative command prompt, and provide the installation path and switch /quiet. Ex: C:FilesAccessDatabaseEngine.exe /quiet. Please note that this approach is not recommended and haven't worked in few instances, so would request you to move to 2 different server approach if possible.

Approach 2:

Microsoft Access Database Driver 2007

Uninstall the security patch (Not recommended):

This patch seems to update Excel Jet connector from V4.00.9801.0 to v4.00.9801.1.

One of the workarounds is to uninstall the KB and it may fix the issue. Although, in some instances it may not help to resolve the issue.

Approach 3:

Registry change (Not recommended): [Request you to take a backup of the registry key before making any changes]

Another workaround would be to update the below registry key to point to an old copy of the DLL file:

[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftJet4.0EnginesExcelWin32]

To get an old copy of the DLL, uninstall the patch KB4041681, copy the DLL 'msexcl40.dll' from C:WindowsSysWOW64msexcl40.dll to a new location say 'C:msexclmsexcl40.dll'.

You can now modify the registry key [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftJet4.0EnginesExcelWin32] to point to the new DLL location 'C:msexclmsexcl40.dll' (by default it’d be pointing to C:WindowsSysWOW64msexcl40.dll)

Other workarounds discussed online:

There is a public forum discussion where many customers found various ways to work around this issue.

ODBC Excel Driver Stopped Working with 'Unexpected error from external database driver (1). (Microsoft JET Database Engine)'

Solution:

The best recommended solution is to move to Microsoft ACE OLE DB provider.

Apart from this, Microsoft is working on a resolution and will provide an update in an upcoming release of the security patch. This is expected to be available in another 2-3 weeks or earlier. (Blog is updated with this information). If this is business critical and you are still encountering any related issues, please reach out to the Microsoft Customer Services & Support(CSS) team.

DISCLAIMER:

THE ABOVE INFORMATION IS PROVIDED 'AS IS' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE.

Authors:

Chrone Meade - Support Engineer, SQL Server BI Developer team, Microsoft

Jon Herman - Sr Support Engineer, SQL Server BI Developer team, Microsoft

Microsoft Access Database Driver 2016

Krishnakumar Rukmangathan – Support Escalation Engineer, SQL Server BI Developer team, Microsoft

Issue:

You are trying to install the 64-bit Access Database Engine on your machine that is running 32-bit Microsoft Office (2007, 2010, or 2013) and you are getting an error message:
'You cannot install the 64-bit version of Microsoft Access Database Engine 2010 because you currently have 32-bit products installed..'

Causes:

Microsoft does not support the side-by-side installation of 32- and 64-bit Microsoft Office or their dependent components.

Solution:

VIDEO DEMONSTRATION
WRITTEN INSTRUCTIONS:
Workaround to install the 64-bit Access Database Engine 2010 on a computer with 32-bit Microsoft Office 2007, 2010, or 2013:

Before you begin, open the Registry Editory (type 'regedit' in the Windows search box under the Start menu and select regedit.exe) and check the following registry key for the value 'mso.dll' is NOT present in: 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice14.0CommonFilesPaths'

This registry key value would be present if Microsoft Office 64-bit was installed on the computer, in which case you should be able to install the 64-bit Access Database Engine without using this workaround.
Workaround:

We're here to help you find the very best tools that will make converting written documents to audio files as easy as possible.Text to speech software can be enormously helpful for anyone who's visually impaired, or has a condition like dyslexia that makes reading on screens tricky. Sight reading software free. It can also help overcome language barriers for people who read a language but don't speak it, or are in the process of learning.Text to speech software is also ideal if you want to listen to a document while doing something else, if you find it easier to retain information you've heard, or if you want to sense-check something you've written.Here's our pick of the best free text to speech software for reading either individual paragraphs or whole documents aloud.1.

1. Open the Command Prompt by typing 'cmd' in the Windows search box under the Start menu and selecting cmd.exe
2. Type the file path and file name of the 64-bit Access Database Engine 2010 install file, followed by a space and '/passive' (this runs the installation without showing any error messages).
For example:

3. Open the Registry Editor by typing 'regedit' in the Windows search box under the Start menu and selecting regedit.exe
4. Delete or rename the 'mso.dll' registry value in the following registry key: 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice14.0CommonFilesPaths'

NOTES:

  • If you do not delete the 'mso.dll' registry value, you will get a 'Reconfiguring' message every time you open up an Office application.
  • You will need to use this same workaround to install Service Pack 1 for Access Database Engine 2010 for 64-bit

See Also:

64-bit: Configuring ODBC Excel and Access Connections
Downloads:
Access Database Engine 2010 for 64-bit
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=13255
Service Pack 1 for Access Database Engine 2010 for 64-bit
http://www.microsoft.com/en-us/download/details.aspx?id=26605

Versions:

all;
Comments are closed.