SSIS package failing

Question

 

We are porting an existing package from SQL Server 2005 to Katami and are getting the following error:

 

Code: 0xC0209303     Source: MasterSSIS Connection manager "SSISOperations"     Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider is not registered -- perhaps no 64-bit provider is available.  Error code: 0x80040154.  An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".  End Error  Error: 2007-09-14 09:43:35.00     Code: 0xC0209303     Source: MasterSSIS Connection manager "SSISOperations"     Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider is not registered -- perhaps no 64-bit provider is available.  Error code: 0x80040154.  An OLE DB record is available.  Source: "Microsoft OLE DB Service Component...  The package execution fa...

 

Katami is installed on Longhorn Server

Answer 1

> The requested OLE DB provider is not registered -- perhaps no 64-bit provider is available.

 

And what OLEDB provider you are using? Does it exist for 64-bit, is it installed?

Answer 2

It is the Flat-File provider.  Importing from a .csv file into a table.

 

Thanks,

 

Ed

Answer 3

The error seems to indicate that  "SSISOperations" connection manager is OLEDB connection manager, but the appropriate provider is not installed. So which provider is it?

Answer 4

The SSISOperations in an OLEDB connection - it connects to a SQL database that drives the rest of the SSIS package execution.  Shouldn't the 'standard' providers be installed as part of Katmai?

 

Thanks,

 

Ed

Answer 5

If you used SNAC provider, the SQL 2005 version of this provider is not installed with SQL 2008. You can either install it from SQL 2005 disk, or change the connection manager to use SNAC 2008 (this should happen automatically in future, but this code is not in CTP yet).

 

You do it individually by clicking on the connection and editing the ConnectionString property, or bulk edit .dtsx files with Find/Replace.

 

Replace

 

Provider=sqlncli.1

 

with

 

Provider=sqlncli10.1

 

And your connections will use SNAC for SQL 2008.

Answer 6

Getting the same problem but with a little different situation.
I created a new connection to an access database, and I get this error:
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC020801C at Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "apa" failed with error code 0xC0209303.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.

The connection tests, and when I run the preview, I see the data I want. However when I run the dtsx, it fails on the source.

Answer 7

Same happens here.

 

Migrating package from Vista + Sql 2008 to W2K8 + Sql 2008.

 

Connecting to oracle provider.

 

[Connection manager "ERP"] Error: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider MSDAORA.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  Description: "Class not registered".

 

Can test, can preview data, get error when we want to run the package.

 

 

 

Answer 8

Hello,

I have exactely the same problem. Could you tell me please, what was the solution to it?

SSIS package "Package.dtsx" starting.

Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.

Error: 0xC020801C at Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "STAMMDAT" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.

Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.

Error: 0xC0024107 at Data Flow Task: There were errors during task validation.

SSIS package "Package.dtsx" finished: Success.

Answer 9

I got it to work using the RUN 64  BIT RUN TIME to FALSE on project properties.

Answer 10

Thank you very much. It works also in my case!

Answer 11

You are smart :)

Answer 12

Hi it Works in desing. but if U try put it on a Job. an schedulle it  happend  the same erro can anyone help me ?

Answer 13

Run64BitRuntime will have no effect.

You should start a new thread with your situation.  Please provide more information on how you're executing the package on your server.

---

Talk to me now on

Answer 14

I was having exactly the same problem - I managed to get it to work in designing by following the steps already described above - setting the RUN 64  BIT RUN TIME to FALSE on project properties but was getting the SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider is not registered -- perhaps no 64-bit provider is available message when I tried scheduling it as a job.

The solution I found was to edit the job property in SQL Server (Select Steps, then the Execution tab and tick the Use 32 bit runtime checkbox).
 

Answer 15

Thank you, been very helpful ^^

Answer 16

Great!!!!!!! This is the solution. 

Thanks

Answer 17

Great! It worked fine for me as well.