Discussion:
SSIS 2005: Using Execute SQL Task to work with Excel Connection Ma
(too old to reply)
Craig Stewart
2008-10-28 19:19:02 UTC
Permalink
I am trying to export data to an Excel file from from SQL Server Integration
Services (2005). The details of the error I'm encountering are below.
Thanks for any help that can be provided.

Details:

Connection Manager: ChangeSummary.xls
- Connection Manager type: Excel Connection Manager
- Conenction Manager "Excel version:": Microsoft Excel 97-2005

Execute SQL Task: The objective of the task is to create a worksheet in the
Excel file. It uses the "ChangeSummary.xls" connection manager described
above.
- SQLSourceType: Direct input
- SQLStatement: CREATE TABLE Summary (ActionCD varchar(50),CNT varchar(10))


If I click the Parse Query button on the task, I get the following error
message:
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error
code: 0x80004005.
An OLE DB record is available. Source: "Microsoft JET Database Engine"
Hresult: 0x80004005
Description: "Could not find installable ISAM.".

If I try to execute the task, the task fails with the following error:
[Execute SQL Task] Error: Failed to acquire connection "ChangeSummary.xls".
Connection may not be configured correctly or you may not have the right
permissions on this connection.

The connection manager points to a path on my local C:\ drive; permissions
to the file should not be an issue. My expectation is that the task will
create the Excel file if it does not exist, but I've tested the task both
with and without the file being present and I get the same result either way.

I want to be able to parse this query and execute the task without error.

Thanks,
Craig
Craig Stewart
2008-10-29 21:03:03 UTC
Permalink
Craig,

This will happen if some certain dll’s are not registered properly.

Please check whether the following files exist:

c:\windows\system32\odbcjt32.dll
c:\Program Files\Common Files\system\Ole DB\oledb32.dll
c:\windows\system32\msjet40.dll
c:\windows\system32\msexcl40.dll
C:\program files\common files\system\ado\msado15.dll

If they are, please manually register them: Run each of the following
commands from the “start->run” dialog:

Regsvr32 “c:\Program Files\Common Files\system\Ole DB\oledb32.dll”
Regsvr32 “c:\windows\system32\msjet40.dll”
Regsvr32 “c:\windows\system32\msexcl40.dll”
Regsvr32 “C:\program files\common files\system\ado\msado15.dll”

Please let me know whether the regsvr32 is successful and if it corrected
the problem.
If not, we may need to use FileMon and RegMon utilities to check what DLL was
being initialized and failed.

Darron Jennings
Post by Craig Stewart
I am trying to export data to an Excel file from from SQL Server Integration
Services (2005). The details of the error I'm encountering are below.
Thanks for any help that can be provided.
Connection Manager: ChangeSummary.xls
- Connection Manager type: Excel Connection Manager
- Conenction Manager "Excel version:": Microsoft Excel 97-2005
Execute SQL Task: The objective of the task is to create a worksheet in the
Excel file. It uses the "ChangeSummary.xls" connection manager described
above.
- SQLSourceType: Direct input
- SQLStatement: CREATE TABLE Summary (ActionCD varchar(50),CNT varchar(10))
If I click the Parse Query button on the task, I get the following error
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error
code: 0x80004005.
An OLE DB record is available. Source: "Microsoft JET Database Engine"
Hresult: 0x80004005
Description: "Could not find installable ISAM.".
[Execute SQL Task] Error: Failed to acquire connection "ChangeSummary.xls".
Connection may not be configured correctly or you may not have the right
permissions on this connection.
The connection manager points to a path on my local C:\ drive; permissions
to the file should not be an issue. My expectation is that the task will
create the Excel file if it does not exist, but I've tested the task both
with and without the file being present and I get the same result either way.
I want to be able to parse this query and execute the task without error.
Thanks,
Craig
Loading...