Geek Answers Handbook

SQL Server 2012 - Unable to create instance of OLE DB provider "Microsoft.Jet.OLEDB.4.0" (Microsoft SQL Server, error: 7302)

I just installed SQL Server 2012 to check the differences and make sure that this is normal for my work. I cannot be pro in SQL, but I do not see how to add the Link to Jet database on my server. I imported the Jet databases, but, going through the GUI to bind the JET database, I don't see the provider for the JET. I am running Access 2003 (I do not like the 2008+ GUI)

I searched for something that was incomparable with my problem; at least I didn't understand anything. Nothing is said about how to add Jet db Provider.

I ran a connection string to the Jet database through QA:

sp_addlinkedserver 'USGEScrub', 'Access', 'Microsoft.Jet.OLEDB.4.0', 'D:\Lead$\SupList\USGEScrub.mdb'

The connection string works until I try to access the data, and then I get this error and, of course, if I click the link, nothing will appear:

 TITLE: Microsoft SQL Server Management Studio Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

For help, click http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476

 ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. Cannot create an instance of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "USGEScrub". (Microsoft SQL Server, Error: 7302)

For help, click http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2100&EvtSrc=MSSQLServer&EvtID=7302&LinkId=20476

+4
source share
3 answers
  • Download Access 2010 Database Engine from Microsoft
  • Allow InProcess
  • Add a linked server using the ACE OLEDB provider.

more details here

+2
source

I had a similar problem, and in my case it turned out to be related to the permissions in the% TEMP% folder for the account under which the SQL Server service was running. See my answer here for more details.

0
source

Sometimes these problems occur on x64 computers with installed versions of Office x84. Try the following:

Install pasive OleDb Driver x64

0
source

More articles:


All Articles