The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Andre - 29 Jul 2008 03:49 GMT

Microsoft SQL Server 2005 - 9.00.3068.00 (X64)

While trying to access a linked server, I'm getting the error message:
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I've searched the web and see this is an issue with the 64 bit version of
SQL 2005. Are there any updates from MS? Any plans on helping us out?

Thanks, Andre

Reply to this Message

Daniel Crichton - 29 Jul 2008 12:36 GMT

Andre wrote on Mon, 28 Jul 2008 19:49:33 -0700:

> Microsoft SQL Server 2005 - 9.00.3068.00 (X64)

> While trying to access a linked server, I'm getting the error message:
> The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

> I've searched the web and see this is an issue with the 64 bit version
> of SQL 2005. Are there any updates from MS? Any plans on helping us out?

> Thanks, Andre

There is no 64-bit Jet driver, so this isn't possible.

I've seen one workaround though - install SQL Server Express as another
instance which will be 32-bit, and connect to Access from this as a linked
server. Then connect from the 64-bit SQL Server 2005 to the Express 32-bit
instance as a linked server, and you can pull the Access data from there -
SQL Server 64-bit will happily communicate with SQL Server 32-bit, and
you'll be using the Express instance as a "bridge" to the Access mdb. It's a
kludge, but until MS releases a Jet 64-bit driver (which is highly unlikely)
you won't have much choice if you want to continue using SQL Server 64-bit.

Signature

Dan

Reply to this Message

Andre - 29 Jul 2008 17:25 GMT

Is this what we need?

http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be
-ca44d18b059b&DisplayLang=en

Reply to this Message

Russell Fields - 29 Jul 2008 23:17 GMT

Andre,

I am unsure if this will work for you, although you could certainly try it
out. See this conversation, the last post by Charles Wang:
http://www.eggheadcafe.com/software/aspnet/32205147/server64bit-openrowset-c.aspx

RLF

> Is this what we need?
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be
-ca44d18b059b&DisplayLang=en

Reply to this Message

Andre - 30 Jul 2008 06:59 GMT

Great article, thanks for sharing it Russell.

I just tried installing the new driver, and found it doesn't help me import
from Access, so I guess something is still missing like the asam driver
issue in the article. I guess I'm really confused about the 64 bit OLEDB
driver I just downloaded and installed. If it doesn't allow me to import
from an Access db, what does it do? I'm no better off before I downloaded
it.

I got my import to work, but using what I consider a kludge (thanks MS)
approach. I created a new SSIS project and changed the Run64BitRuntime
property to false. I then saved my SSIS package to SQL and changed the job
step from SSIS to Operating System type. I then used the dtexecui to
capture the command line exec. In the job step, I then had to reference the
32 bit ssis executable prior to the command line exec - like this:
C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe /SQL
"\MySSISPackage" /SERVER "MyServer" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/REPORTING N

IMHO, this is a huge freaking kludge, and I'm very disappointed that I have
a brand new quad-core box with gobs of ram and HD space on it, running a 64
bit OS and 64 bit SQL...and I have to junk up my server with a kludge such
as this just to get it to do what it used to do with a 32 bit OS/SQL no
problem. Something seems wrong there. If MS wants us to adopt their latest
technologies, which I'm a huge proponent of by the way, they need to make
their latest technology work. I've seen other posts here as well as a lot
of places on the Internet with people who are just as disappointed as I am
too, so I know I'm not the only one.

Andre

Reply to this Message