Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

Bradley Schacht

Bradley is a consultant at Pragmatic Works in Jacksonville, FL. He was an author on the book SharePoint 2010 Business Intelligence 24-Hour Trainer and tech edited the SQL 2011 Bible. His experience on the Microsoft BI platform includes DTS, SSIS, SSRS, SSAS and migrations and conversions. He has helped numerous companies in successfully developing and implementing new business intelligence solutions into their organizations. Bradley also participates as a speaker in community events like SQL Saturday, Code Camp, SQL Lunch and SQL Server User Groups. He is a contributor on sites such as and SQL Server Central as well as an active member of the Jacksonville SQL Server User Group (JSSUG).

The ‘Microsoft.Ace.OLEDB.12.0' Provider Is Not Registered on the Local Machine

If you have used SSIS to move data from something like Access or more commonly Excel, it is a good possibility you have seen this error at some point:

Error: The ‘Microsoft.Ace.OLEDB.12.0‘ provider is not registered on the local machine.

The reason this error shows up is because the proper components are not present that are required to move data from Office files (I’m looking at you Access and Excel). If you do development on a laptop or desktop then there is a very good chance that Office is installed on the machine and this error will likely never present itself.  However, when the package is run or developed on a server, where Office is generally not installed and shouldn’t be, the proper components for Access and Excel interaction do not exist.

The solution is simply installing the components required from the Microsoft Access Database Engine available here ( at the time of this post. There is a 32 and 64 bit download so be sure to match that to the machine that has the error. Despite the name of the download it actually works for Access AND Excel. A note if you still have issues after installing the components here: The provider portion of the connection string should read Microsoft.ACE.OLEDB.12.0 and if connection to Excel the extended property of Excel 14.0 may need to be added.


Leave a comment on the original post [, opens in a new window]

Loading comments...