2

I have a excel connection manager as destination. My local machine is 32 bit and package runs fine locally. When deployed to server which is a 64-bit machine, package fails with below error.

can some one help ?

I tried all online available options:

run64bitruntime to true/false

delay validation to True

etc.....

Error: 2017-06-13 20:33:46.53 Code: 0xC00F9304 Source: RiverStone_Extract Connection manager "RiverStone_Extract" Description: SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available. End Error

Error: 2017-06-13 20:33:46.53 Code: 0xC020801C Source: RiverStone Extract & Tgt Control Totals Excel Destination [1017] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "RiverStone_Extract" failed with error code 0xC00F9304. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error

Error: 2017-06-13 20:33:46.53 Code: 0xC0047017 Source: RiverStone Extract & Tgt Control Totals SSIS.Pipeline Description: component "Excel Destination" (1017) failed validation and returned error code 0xC020801C. End Error

Progress: 2017-06-13 20:33:46.53 Source: RiverStone Extract & Tgt Control Totals Validating: 100% complete End Progress Error: 2017-06-13 20:33:46.53 Code: 0xC004700C Source: RiverStone Extract & Tgt Control Totals SSIS.Pipeline Description: One or more component failed validation. End Error

Error: 2017-06-13 20:33:46.53 Code: 0xC0024107 Source: RiverStone Extract & Tgt Control Totals Description: There were errors during task validation. End Error

Warning: 2017-06-13 20:33:46.53 Code: 0x80019002 Source: RiverStone_Extract Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (5) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

Hadi
  • 36,233
  • 13
  • 65
  • 124
MannyTheGemini
  • 21
  • 3

2 Answers2

0

Given this part of the error message

The Excel Connection Manager is not supported in the 64-bit version of SSIS

It would appear that you are trying to run the package using the 64bit 'execution mode'

Assuming you have a 32bit MS Office installation change your project so that it runs as 32bit.

You may need to take this into consideration if scheduling via SQL Server's Job Agent

Tomas Ingram
  • 11
  • 1
  • Tried setting run64bit to false, didn't work. I am scheduling job through autosys to run ... any other thoughts ? – MannyTheGemini Jun 13 '17 at 20:01
  • I am not familiar with autosys, if it is essentially a command line than try [DTExec](https://msdn.microsoft.com/en-us/library/ms162810.aspx) from "Programs (x86)" – Tomas Ingram Jun 13 '17 at 20:54
  • Autosys is a scheduling tool , just like SQL agent .... the set up we have at client side (which i cannot change) is setting package connections from a table, so command line is out of box situation. – MannyTheGemini Jun 13 '17 at 20:58
  • Can you install the [64bit ACE driver](https://www.microsoft.com/en-gb/download/details.aspx?id=13255) on the server? Is the 32bit driver installed on the server? n.b. You cannot install both the 32bit and 64bit ACE drivers on the same computer. – Tomas Ingram Jun 13 '17 at 21:23
0

Suggested Solutions

1. Install Microsoft Access 2010 Data Engine 64-Bit

You can Install Microsoft Access 2010 Data Engine 64-Bit from the following link:

2. Make the SQL Agent Job run in 32-bit

Follow one of the following links to learn more:

3. Other Helpful Links

Hadi
  • 36,233
  • 13
  • 65
  • 124