Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SSIS with Excel Expand / Collapse
Author
Message
Posted Tuesday, November 24, 2009 1:19 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 9:27 AM
Points: 170, Visits: 398
I'm running into an issue that my 64 bit Windows 2008 R2 server doesn't seem to have drivers for Excel! Locally, I am writing to Excel files on a 08 server, but when I deploy my package, it throws errors that it can't talk to Excel. There has to be a way to connect to Excel from a 64 bit server....any suggestions?
Post #824112
Posted Tuesday, November 24, 2009 3:16 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 16, 2010 2:54 AM
Points: 3, Visits: 21
the 32 bit excel ole db provider should work in a 64 bit environment.

hth
Post #824178
Posted Tuesday, November 24, 2009 3:20 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 8:34 AM
Points: 4, Visits: 136
you must run the ssis package on 32bit mode.

follow these instructions:

http://msdn.microsoft.com/en-us/library/ms141766.aspx
Post #824180
Posted Wednesday, November 25, 2009 6:37 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 9:27 AM
Points: 170, Visits: 398
Perfect! Worked like a charm, thanks much.
Post #824484
Posted Monday, November 30, 2009 7:29 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 9:27 AM
Points: 170, Visits: 398
Correction...didn't work! I switched things in development area and then setup the job to use 32-bit runtime...here's my error code.

Executed as user: VIRCHOWKRAUSE\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:43:55 AM Error: 2009-11-25 08:44:01.76 Code: 0xC00F9304 Source: TEExtract Connection manager "Excel Connection Manager" 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: 2009-11-25 08:44:01.76 Code: 0xC020801C Source: Non Staff Exp Chg to XLSX Excel Destination [73] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" 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: 2009-11-25 08:44:01.76 Code: 0xC0047017 Source: Non Staff Exp Chg to XLSX SSIS.Pipeline Description: component "Excel Destination" (73) failed validation and returned error code 0xC020801C. End Error Error: 2009-11-25 08:44:01.76 Code: 0xC004700C Source: Non Staff Exp Chg to XLSX SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2009-11-25 08:44:01.76 Code: 0xC0024107 Source: Non Staff Exp Chg to XLSX Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:43:55 AM Finished: 8:44:01 AM Elapsed: 6.052 seconds. The package execution failed. The step failed.
Post #826193
Posted Monday, November 30, 2009 11:02 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 8:34 AM
Points: 4, Visits: 136
Open the agent job. Go to the step which executes the ssis package. Then go to Execution options and change the flag "Use 32 Bit runtime"
Post #826489
Posted Tuesday, December 01, 2009 6:28 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 9:27 AM
Points: 170, Visits: 398
I have that box checked, but still doesn't work. Are you saying to uncheck?
Post #826611
Posted Tuesday, December 01, 2009 7:32 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:02 PM
Points: 6,367, Visits: 8,228
From what I've read about this issue, your job step needs to be set to Operating System (CmdExec), and you have to type the full path to the 32-bit version of ssis to run the pkg, complete with all the necessary parameters.

MS has really missed the boat with how to use 64-bit systems and the basic interaction needed with certain key 32-bit things, such as drivers to access Excel and various text files.


Wayne
Microsoft Certified Master: SQL Server 2008
If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
Links: For better assistance in answering your questions, How to ask a question, Performance Problems, Common date/time routines,
CROSS-TABS and PIVOT tables Part 1 & Part 2, Using APPLY Part 1 & Part 2, Splitting Delimited Strings
Post #826668
Posted Tuesday, December 01, 2009 7:38 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 9:27 AM
Points: 170, Visits: 398
where do i set that? In the Command Line tab of Management Studio? Do you have a link to any examples?

Thanks!
Post #826679
Posted Wednesday, December 02, 2009 8:00 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 12:48 PM
Points: 2,218, Visits: 2,075
You can set it on the General tab of the "job step properties".
Just type it in the command box.
Example: "d:\Program Files\Microsoft SQL Server (x86)\90\DTS\Binn\DTExec.exe" /SQL "\<package name>" /SERVER <server Name> /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E


Mike

_____________________________________________________________________________

A word to the wise ain't necessary, it's the stupid ones who need the advice ...Bill Cosby
Post #827496
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse