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.
Author |
Topic |
sauce1979
Starting Member
47 Posts |
Posted - 2009-06-21 : 11:19:59
|
I have a SSIS package that uses a Foreach container to dynamically name excel workbooks and deposit data within the worksheets.I ran this package once in development in BIDS and it worked fine. If I want to run it it again I get the following error:Error at Package [Connection manager "Excel Connection Manager"]: 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: "The Microsoft Jet database engine cannot open the file ''. It is already opened exclusively by another user, or you need permission to view its data.".Error at Data Flow Task [Excel Destination [52]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.I have created an excel template. I have an execute sql task outside the Foreach container which creates an object variable, User::CurrentCode, to hold the data which will be used to name the excel file dynamically.Within the Foreach container is a copy file task and data flow. The copy file task copies my template. it is parameterized by a variable,User::TemplateFile, that uses the expression :'ContrctTerms_" + @[User::CurrentCode] + ".xls' to name the Excel workbook.The excel connection is pointing to my template. I set the expression for ExcelFilePath property to: @[User::TemplateFile]. The data flow task then sends data to the excel destination based on a paramatized sql statement.For some reason once it has run. It will not allow ssis to access the files.Does anyone have any information on how I can solve this? |
|
svicky9
Posting Yak Master
232 Posts |
Posted - 2009-06-22 : 05:18:13
|
This is because of the 64 Bit issues with Excel providers. You need to set the runtime to 32 bitRight Click Solution --> Debugging --> under Debug Options --> SetRun64BitTime --> 32 BitIt should be workinghttp://www.sqlserver007.com |
 |
|
|
|
|