Prev: Problem with SOAP Toolkit and web service authorization
Next: RSExecutionLog Error: DTSER_FAILURE (1). Options
From: jaylou on 30 Jan 2009 11:38 Hi all, In SQL Server 2008 64-Bit I am trying to create a stored Proc that calls an SSIS packacage to import an Excel spreadsheet using both "EXEC xp_cmdshell 'dtexec /f "\\ewrsql18\NetLocFiles\Packages\LOCTrans.dtsx"' And "EXEC xp_cmdshell 'dtexec /sq "LOCTrans" /ser ewrsql18' I can execute the package with no problems but the TSQL seems to choke when it calls the package with this error: 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. Does anyone have a solution for this? TIA, Joe
From: Russell Fields on 30 Jan 2009 11:42 Joe, This means that you need to be using the 32-bit version of dtexec. See this link from the BOL: http://msdn.microsoft.com/en-us/library/ms162810.aspx RLF "jaylou" <jaylou(a)discussions.microsoft.com> wrote in message news:C2C8CDE1-C6AE-427F-B047-EC110A945D04(a)microsoft.com... > Hi all, > > In SQL Server 2008 64-Bit I am trying to create a stored Proc that calls > an > SSIS packacage to import an Excel spreadsheet using both > "EXEC xp_cmdshell 'dtexec /f > "\\ewrsql18\NetLocFiles\Packages\LOCTrans.dtsx"' > And > "EXEC xp_cmdshell 'dtexec /sq "LOCTrans" /ser ewrsql18' > > I can execute the package with no problems but the TSQL seems to choke > when > it calls the package with this error: > > 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. > > Does anyone have a solution for this? > > TIA, > Joe
From: jaylou on 30 Jan 2009 13:26 Thank you. I had to play around with pointing my cmdshell to the 32 bit version, but I got it to work!!! Thanks again!! Joe "Russell Fields" wrote: > Joe, > > This means that you need to be using the 32-bit version of dtexec. See this > link from the BOL: > http://msdn.microsoft.com/en-us/library/ms162810.aspx > > RLF > > > > "jaylou" <jaylou(a)discussions.microsoft.com> wrote in message > news:C2C8CDE1-C6AE-427F-B047-EC110A945D04(a)microsoft.com... > > Hi all, > > > > In SQL Server 2008 64-Bit I am trying to create a stored Proc that calls > > an > > SSIS packacage to import an Excel spreadsheet using both > > "EXEC xp_cmdshell 'dtexec /f > > "\\ewrsql18\NetLocFiles\Packages\LOCTrans.dtsx"' > > And > > "EXEC xp_cmdshell 'dtexec /sq "LOCTrans" /ser ewrsql18' > > > > I can execute the package with no problems but the TSQL seems to choke > > when > > it calls the package with this error: > > > > 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. > > > > Does anyone have a solution for this? > > > > TIA, > > Joe > >
From: Michael Coles on 31 Jan 2009 19:51 You might consider using an alternative to xp_cmdshell. Be aware that enabling it has security implications. -- ======== Michael Coles "Pro T-SQL 2008 Programmer's Guide" http://www.amazon.com/T-SQL-2008-Programmer-rsquo-Guide/dp/143021001X "jaylou" <jaylou(a)discussions.microsoft.com> wrote in message news:C2C8CDE1-C6AE-427F-B047-EC110A945D04(a)microsoft.com... > Hi all, > > In SQL Server 2008 64-Bit I am trying to create a stored Proc that calls > an > SSIS packacage to import an Excel spreadsheet using both > "EXEC xp_cmdshell 'dtexec /f > "\\ewrsql18\NetLocFiles\Packages\LOCTrans.dtsx"' > And > "EXEC xp_cmdshell 'dtexec /sq "LOCTrans" /ser ewrsql18' > > I can execute the package with no problems but the TSQL seems to choke > when > it calls the package with this error: > > 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. > > Does anyone have a solution for this? > > TIA, > Joe
From: jaylou on 1 Feb 2009 12:58 Do you have another way to import an Excel spreadsheet into a SQL table in a srored Proc? I would love an alternative. The data I have to report off of comes from an application that I can not access directly, but they have an export feature. Thanks, Joe "Michael Coles" wrote: > You might consider using an alternative to xp_cmdshell. Be aware that > enabling it has security implications. > > -- > > ======== > Michael Coles > "Pro T-SQL 2008 Programmer's Guide" > http://www.amazon.com/T-SQL-2008-Programmer-rsquo-Guide/dp/143021001X > > > "jaylou" <jaylou(a)discussions.microsoft.com> wrote in message > news:C2C8CDE1-C6AE-427F-B047-EC110A945D04(a)microsoft.com... > > Hi all, > > > > In SQL Server 2008 64-Bit I am trying to create a stored Proc that calls > > an > > SSIS packacage to import an Excel spreadsheet using both > > "EXEC xp_cmdshell 'dtexec /f > > "\\ewrsql18\NetLocFiles\Packages\LOCTrans.dtsx"' > > And > > "EXEC xp_cmdshell 'dtexec /sq "LOCTrans" /ser ewrsql18' > > > > I can execute the package with no problems but the TSQL seems to choke > > when > > it calls the package with this error: > > > > 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. > > > > Does anyone have a solution for this? > > > > TIA, > > Joe > > >
|
Next
|
Last
Pages: 1 2 Prev: Problem with SOAP Toolkit and web service authorization Next: RSExecutionLog Error: DTSER_FAILURE (1). Options |