Class not registered - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SSIS and Import/Export (2008)

Class not registered

Author

Topic

Samadhi69
Starting Member

20 Posts

Posted - 2011-07-27 : 13:09:32

I am trying to use and SSIS to export data from a table in my SQL Server DB to an Access 2003 db on a shared drive. This is a job or package that will be run on the machine that hosts the database (IE the server).

I ran into some issues trying to use the package I use on my machine so I did the following on the server:
1. Ran the SQL Server Import and Export Wizard (64-bit)
2. Data source "SQL Server Native Client 10.0" -- entered login etc
3. Data destination. None of these look appropriate:
a-c. .Net Framework Data Provider for (a. ODBC b. Oracle c. SqlServer)
d. Flat File Destination
e-f. Microsoft OLE DB Provider for (e. Analysis Services 10.0 f. SQL Server)
g. SQL Native Client
h. SQL Server Native Client 10.0

So I decided to instead:
1. Run the SQL Server Import and Export Wizard (32-bit)
2. Data source "SQL Server Native Client 10.0" -- entered login etc
3. Destination "Microsoft Access" -- choose appropriate file
4-6. Copy data from etc. Choose table and review.
7. Check "Run immediately" *and* "Save SSIS Package" - File system - Do not save sensitive
8. Finish

Runs like a charm.

However, if I add the saved SSIS as a job in SQL Server Agent or try to run it in Visual Studio I get the following errors:
(Agent)
07/27/2011 09:56:38,TestL2,Error,1,RHASQLENT\EPSQLSERVER,TestL2,Blah,,Executed as user: RHASQLENT\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.0.4000.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:56:38 AM Error: 2011-07-27 09:56:38.67 Code: 0xC0209303 Source: Test0727 Connection manager "DestinationConnectionOLEDB" Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 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". End Error Error: 2011-07-27 09:56:38.67 Code: 0xC020801C Source: Data Flow Task 1 Destination - Eds_cabv [31] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationConnectionOLEDB" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2011-07-27 09:56:38.67 Code: 0xC0047017 Source: Data Flow Task 1 SSIS.Pipeline Description: component "Destination - Eds_cabv" (31) failed validation and returned error code 0xC020801C. End Error Error: 2011-07-27 09:56:38.67 Code: 0xC004700C Source: Data Flow Task 1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2011-07-27 09:56:38.67 Code: 0xC0024107 Source: Data Flow Task 1 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:56:38 AM Finished: 9:56:38 AM Elapsed: 0.125 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,,0

(Visual Studio)
[Destination - Eds_cabv [31]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationConnectionOLEDB" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
[SSIS.Pipeline] Error: component "Destination - Eds_cabv" (31) failed validation and returned error code 0xC020801C.

-------------------
I've seen one suggestion that I have to set this step up as a CmdExec [url]http://www.sqlservercentral.com/Forums/Topic435591-147-1.aspx[/url] which I would love to avoid.

Is it possible to register this class (Access) as 64 bit (I'm guessing that's the problem)?

If con is the opposite of pro, what's the opposite of progress?

Samadhi69
Starting Member

20 Posts

Posted - 2011-07-27 : 16:33:30

I was able to get it to run in BIDS by setting the Run64BitRuntime = False. It's looking like CmdExec is going to be the solution. =(

If con is the opposite of pro, what's the opposite of progress?

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources