October 12, 2010 at 12:19 pm
I am trying to import excel files into SQL Server 2008. But I get the following error.
"The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code..."
I have set the option of In the Debugging section, change the value of "Run64bitRuntime" to false.I have also set the option for delay validation true.
This is irritating me..what to do?
October 13, 2010 at 11:32 am
SSIS.COM (10/12/2010)
I am trying to import excel files into SQL Server 2008. But I get the following error."The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code..."
I have set the option of In the Debugging section, change the value of "Run64bitRuntime" to false.I have also set the option for delay validation true.
This is irritating me..what to do?
Please post the complete error message. Also what is the type of Excel file you are trying to import ? 2007 or Excel 97-2003 ?
October 13, 2010 at 3:26 pm
Error: 0xC0202009 at EBSKoboUSTAXFileImport, 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 Office Access Database Engine" Hresult: 0x80004005 Description: "The Microsoft Office Access database engine cannot open or write to the file ''. It is already opened exclusively by another user, or you need permission to view and write its data.".
Error: 0xC020801C at Data Flow Task, Excel Source [2374]: 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 am using 2007 excel file....
October 13, 2010 at 3:29 pm
This is the important part:
"The Microsoft Office Access database engine cannot open or write to the file ''. It is already opened exclusively by another user, or you need permission to view and write its data."
You have file permissions problem.
October 14, 2010 at 6:34 am
But, I was able to open the file just couple of minutes back...and I have made a small modification in the derived column transformation after the excel source ..and I got this error....
October 14, 2010 at 7:07 am
CozyRoc (10/13/2010)
This is the important part:"The Microsoft Office Access database engine cannot open or write to the file ''. It is already opened exclusively by another user, or you need permission to view and write its data."
You have file permissions problem.
SSIS.COM (10/14/2010)
But, I was able to open the file just couple of minutes back...and I have made a small modification in the derived column transformation after the excel source ..and I got this error....
Is the file open by anyone in Excel? Excel opens it exclusively, and prevents SSIS (aka OpenRowset) from being able to open it.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
October 14, 2010 at 7:39 am
No I didn't open it in excel...But I think the problem is when the package runs for the first time it opens ..BUt If I run it second time it doesn't open and gives that error..So, I was thinking may be it locks the sheet ..IS that a possibility....It never happened to me before
October 14, 2010 at 9:05 am
I've never seen that happen.
If you can get desktop access to the computer that houses the Excel file, you can see who/what has the file open.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
October 14, 2010 at 9:21 am
Use something like Process Explorer to see what process is locking the file.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply