• Skip to main content
  • Skip to primary sidebar
  • Skip to footer
  • Technology
    • Development
    • Hardware
    • Intune
    • Microsoft
    • Office
    • Office 365
    • Security
    • SharePoint
    • Software
    • SQL server
  • Personal development
    • Blog
    • Career
    • Freelancer
    • Knowledge
    • NEWS
    • Private
    • Thoughts
  • Consulting services
  • Contact me

Not only IT

About life, IT and other things...

Home » Technology » SQL server » SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR

SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR

March 8, 2013 By Tomasz Szulczewski 1 Comment

Yesterday I had to load some data from Oracle database to my SQL Server 2008 R2. And as many of you my laptop runs 64 bit version of Windows. Task seems to be simple.  When you try to use Oracle Ole DB for the first time from Business Intelligence Development Studio, you’ll get message that you have to install the driver first. So why it’s looks as installed??? Ok, I have to get Oracle Ole DB driver for Windows

So I get my driver from Oracle, and there’s no 64 bit version, you can get only 32 bit. Now simple thing, you have to just create source and destination in simple data flow and that’s all. We press F5 and bazinga! We get: Error: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider OraOLEDB.Oracle.1 is not registered — perhaps no 64-bit provider is available.  Error code: 0x00000000. An OLE DB record is available.  Source: “Microsoft OLE DB Service Components”  Hresult: 0x80040154

I saw different solutions, but  not the simplest one. Check this print screen:

image

 

Go to your SSIS package project properties. And find option “Run64BitRuntime”. Set it to false and now when you press F5 your project will run without error. This is the best solution in my opinion when you can run your package from BIDS.

In case when you have schedule it you have to use 32 bit version of dtexec utility. By default SQL Server use 64 bit. So you will find it at: your SQL Server drive Program Files (x86)Microsoft SQL Server100DTSBinn

Then you can run your package with something like this:

dtexec /FILE “C:UsersUserNameDocumentsVisual Studio 2008ProjectsIntegration Services Project1Integration Services Project1Package.dtsx” /DECRYPT /CHECKPOINTING OFF  /REPORTING EW
[adblockingdetector id=”5770e6ed85560″]

Related

Filed Under: SQL server Tagged With: SQL server

About Tomasz Szulczewski

I've got more than 20 years of IT experience. IT is my passion and I am still increasing my skills. I work as a SharePoint, Office 365 and Azure architect.

Reader Interactions

Trackbacks

  1. Debugging SQL Server integration solutions | About life, IT, and other things... says:
    November 25, 2013 at 2:32 pm

    […] few months ago I wrote a post about problems when you use 32 bit driver in 64 bit SQL Server. Now I had to face another problem linked to this solution. We made an upgrade of existing SQL […]

    Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Join the Newsletter

Social media

  • Facebook
  • Instagram
  • LinkedIn
  • Twitter
  • YouTube

Search this site

Sign up for Wise accounts

Signup and earn $25

payoneer
payoneer

My latest achievement

Microsoft 365 Certified: Enterprise Administrator Expert
Microsoft 365 Certified: Enterprise Administrator Expert

Tags

Azure Azure Active Directory BizSpark Blog career Certification cloud conference edge freelance Freelancer Hardware home office InfoPath Intune Knowledge licensing Microsoft Microsoft 365 News Office Office 365 Personal development Power virtual agent Private security SharePoint SharePoint designer SharePoint online Software SQL server upwork Windows Windows 365 yammer

Footer

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright © 2022 Tomasz Szulczewski