SCREW MICROSOFT !!!

Question

Post reply

SCREW MICROSOFT !!!

Raymond van Laake

SSCarpal Tunnel

Points: 4212
More actions
December 2, 2009 at 9:28 am

#218183

Hi there,
I am sorry about the strong language in the subject, but I'm really stuck here. On my "old" SQL2005 machine I can import Excel data with
SELECT * INTO [RAWIMPORT2] FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;HDR=YES;IMEX=1;Database=test.xls', [Sheet1$])
On my very very very expensive brand new Windows Server 2008 / SQL Server 2008 this isn't possible anymore? From what I read all over the internet? If this is true I'm never going to update any server anymore!!!
Basic question: how can I resolve the
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
error??????
Please help me keeping my job,
Thanks, Raymond

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply

GSquared SSC Guru Points: 260824 More actions · Answer 1

Let me guess, you upgraded to a 64-bit system from a 32-bit system?

If so, it's pretty much just a matter of downloading and registering the necessary drivers.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Raymond van Laake SSCarpal Tunnel Points: 4212 More actions · Answer 2

Thanks for your reply!

You are very right about the upgrade from 32 to 64 bit. As for downloading the drivers: MS says that the 64-bit drivers are shipped with Server 2008. My problem is that I really wouldn't know which file to register.... and then I assume it should be registered with regsvr32.exe... or not?

I'm in the dark and spent two days trying to find answers..... so if you (or anyone else) knows how to register what I'd be grateful forever!

Thx,

Raymond

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 3

Uh, there are no 64-bit jet drivers to get an install..

The way around this is usually SSIS being run by the 32-bit version of DTEXEC.

Sorry..

CEWII

GSquared SSC Guru Points: 260824 More actions · Answer 4

I've only had to do it once, and that was almost a year ago, so I'd pretty much have to dig through MSDN and online searching to do it. That's what I did last time. But I didn't have any time pressure on me, since I was setting it up as a personal education and proof-of-concept task on my home computer.

Maybe someone more familiar with it will stop by this discussion, but I wouldn't count on that if I were you. Contact MS directly if this is really an urgent matter. These forums aren't really subject to any sort of SLA, so you're better off spending the $100 necessary for online support from MS, or using an MSDN ticket, or something of that sort.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Greg Edwards-268690 SSC-Insane Points: 20680 More actions · Answer 5

Have a look at this:

http://msdn.microsoft.com/en-us/library/ms141766.aspx

Greg E

Carolyn Richardson SSCrazy Eights Points: 8357 More actions · Answer 6

See http://msdn.microsoft.com/en-us/library/ms141209.aspx you will need to use the 32 bit drivers. Not nice, but there you have it.

Facts are stubborn things, but statistics are more pliable - Mark Twain
Carolyn
SQLServerSpecialists[/url]

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 7

And MS certainly knows about it:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125117

CEWII

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 8

Heh.... you screw Microsoft... I'll hold your coat.:-P

I agree, though... everytime MS does an upgrade, they take away yet another useful feature or deprecate another. I don't know where they actually get their "user intell" from, but it's not from the hard working boys and girls in the field that actually have to put up with disappearing features.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Raymond van Laake SSCarpal Tunnel Points: 4212 More actions · Answer 9

Thanks for all y'r input folks.... I'm pretty disappointed with MS. How can a company that makes the best databaseserver software let the users so down???

I'll dig into your hints and let know how it works out....

Thanks,

Raymond

Robert Davis One Orange Chip Points: 28027 More actions · Answer 10

The SQL Server team doesn't write the providers to connect to SQL Server. Unfortunately, whoever does the JET provider has yet to write a 64 bit version of it. So the target of your wrath should be whoever is in charge of the JET provider.

If you're going to screw MSFT, you should make sure you get the right person. 🙂

My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url]

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 11

Robert Davis (12/4/2009)
The SQL Server team doesn't write the providers to connect to SQL Server. Unfortunately, whoever does the JET provider has yet to write a 64 bit version of it. So the target of your wrath should be whoever is in charge of the JET provider.
If you're going to screw MSFT, you should make sure you get the right person. 🙂

I guess I'd have to disagree with that. Microsoft is responsible for SQL Server... and all of it's parts. The Jet drivers have been a part of SQL Server for a very long time. Even though the SQL Server team doesn't write the JET drivers, it seems to me that Microsoft should be responsible for those parts because they are a part of a product they sell.

I tell people to get control of their vendors all the time. If what you say is true, then Microsoft needs to get control of their vendors because it's Microsoft that's ultimately responsible for all of the parts.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Robert Davis One Orange Chip Points: 28027 More actions · Answer 12

Don't misunderstand me. I'm not implying that its not MSFT's fault. I'm just suggesting that the wrath be well-focused. 🙂

My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url]

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 13

Robert Davis (12/5/2009)
Don't misunderstand me. I'm not implying that its not MSFT's fault. I'm just suggesting that the wrath be well-focused. 🙂

I am implying that the lack of 64-bit jet drivers IS Microsofts fault. If they don't want us to use jet drivers in 64-bit SSIS then they need to provide a replacement, like a true Excel source that doesn't use jet instead of what they have done.

CEWII

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 14

I would agree. If we are moving toward 64-bit OS's, both server and desktop/laptop, then there really should be 64-bit versions of the drivers needed to access Access and Excel since they are also going 64-bit.