I open a package in SSIS I get the following errors.
Validation error. Create TestKeys For Scan Records: TestKeys Table in AEISIT Import db [1]:
The AcquireConnection method call to the connection manager "AEISIT Upload" failed with error code 0xC0202009. ScanUpload.dtsx 0 0
I open my connections in the connection manager and set them to the (local) server and the errors go away.
Then I close and reopen the package and the errors are back.
What am I doing wrong??
I have written an SSIS Package that connects to an Oracle database through SQL Authentication. Whenever I execute the package in BIDS it executes without a problem but when I try to schedule the package as a Job I recieve an AcquireConnection Error. Any help?
I have tried the solutions outlined in http://support.microsoft.com/kb/918760 and have read through the KB but have found few solutions that pertain to connecting to remote Oracle databases through SQL Authentication. Any help would be much appreicated.
I have written some code to programmatically create an SSIS package. The code runs well if I just stick it in a windows form button event handler (e.g. OnClick). The code works well if I wrap it up in a DLL and call the DLL from a windows application. The code works well if I suck the DLL into a Windows Service and a windows client calls the service to create and run the SSIS package. In other words, the code always works when I call from a windows (Forms) application - regardless of how the code is hosted.
Now, if I take the code and stick it in the event handler of a Web Form button - it fails. If I use my DLL that wraps the code and call the DLL from a web form - it fails. It I make a remoting call to a windows service that then calls the DLL - it fails.
Note, in my windows service I have taken every possible measure to disassociate the call from the identity of the client. The windows service has a listener thread that places the arguments for the package creation on a queue. The listener thread then signals an event. A different thread then pulls the arguments off of the queue and creates the package.
Mind you, all of this works great if the client to the windows service is a windows application. In fact, as I said, the code always runs if it is called from a windows application (directly or via the windows service). But, if my client to my windows service is an ASP.Net application, then the code always fails. I have no idea why the service would care who its client is - but it seems to. I printed out the identity of the User that owns the thread that the windows service uses to create and execute the package, it is not NETWORK SERVICE or ASPNET or any other user - it is the windows service user - which happens to be the administrator account on my machine.
The package creation always fails in the same place. A call to AcquireConnections for an OleDBDestination fails with COM error 0xC020801C. I assumed this was some sort of permissions error - though with my windows service running as administrator and doing all of the work related to the package, I cannot really understand why.
So, going down the path of permissions, I gave every user on my machine administrative priviliges on the machine and the database. That did not work. I then created a custom ASP.Net Application Pool so I could create a new user. I gave that new user Administrator permissions and it still does not work.
I am running Windows 2003, IIS6, SQL 2005, all 32bit, all on the same local machine which is not part of a domain.
This is truly magical. The code always works when called from windows and it never works when called from ASP.Net - even with a windows service in between.
I am totally stumped. Any help would be greatly appreciated.
Error at Text Inbound Task [SQL Server Destination [9]]: The AcquireConnection method call to the connection manager "Server.Northwind" failed with error code 0xC0202009. Error at Text Inbound Task [DTS.Pipeline]: component "SQL Server Destination" (9) failed validation and returned error code 0xC020801C.
Please keep me posted with alternate work around(s) /solution(s).
I am facing a problem with the connection method, it says,
"[Store [10069]] Error: The AcquireConnection method call to the connection manager "Data Source Destination" failed with error code 0xC001A004. "
(Store - Look up component.)
This problem occurs only when i am using Transaction option, all the component(Look up,Destination etc) says the same error message in the Pre-Execute phase. But i can open the component and can able to see the data in preview.
And also this is not occuring in our testing environment. We have copied the same pakages in our production, the package failed stating the above. I can not simulate the same problem in my testing server.
Has anyone faced this kind of problem? please help me to solve this.
I'm creating a small test package that copies a value from an Excel 2007 worksheet into a SQL 2005 database (SP2). When I do an Execute Task, I get the following error:
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager \loripMandEScorecardsSQLQueryExample.xlsx failed with error code 0xC0202009.
However, if I do a "Preview" in the Editor for this same Excel Source task that fails, the data comes up as I would expect. What am I missing?
I've got an SSIS package that I've been testing all week and it runs fine in Visual Studio. The package uses an OLE DB connection manager to access the dBase files using the Jet Provider. The dBase files are stored on a remote file share. There are a series of identical files held in different dated folders. I use a ForEach loop to move through the folder list and import the data as I go. When I deploy it to the server and try to run it, I get the following:
The AcquireConnection method call to the connection manager "Aloha" failed with error code 0xC0202009.
Aloha is the ConncetionManager to the dBase files. I've searched everywhere I can for ideas on how to solve this. I've made the SQL Agent Service is running under the same account I used to author the package. I've made sure that the package is using Server Storage. Everything looks like it should be working.
Can anyone give me any other items I can look into?
I have a SQL Server Agent job with a step to execute an SSIS package. The package has as one of it's connection managers the Connection Manager For Excel Files. When I run the job it fails every time. I have implemented logging and in the OnError event it states "The AcquireConnection method call to the connection manager "LOBMappingExcel" failed with error code 0xC0202009".
I've seen the previous threads on this (although maybe not all of them). However, i don't think I'm getting the error for the same reason. The full error I'm getting is:
We are migrating our production environment from 32-bit SQL Server 2005, Windows 2003 server to 64-bit SQL Server 2005, Windows 2003 server environment with 4GB of RAM. We have recompiled the SSIS packages to run in 64-bit mode and stored them in database. But one of the package fails with initial information as
Information: The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. 34720 buffers were considered and 34720 were locked. Either not enough memory is available to the pipeline because not enough is installed, other processes are using it, or too many buffers are locked.
And the subsequent error messages received as
Error Message 1
A buffer could not be locked. The system is out of memory or the buffer manager has reached its quota.
Error Message 2
An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Reading from DTS buffer timed out.".
The package runs fine if I run it by itself. Unfortunately we want to call it from another package and when we do so it fails everytime with the following error; "AcquireConnection method call to the connection manager "BPCSF" failed with error code 0xC0202009." This package is calling an AS400 and pulling data from it into a staging environment. The task that is failing is 4th task on the list and is the 3rd task to call the AS400 environment. If I need to provide more information I would be happy to do so. Any help would be greatly appreciated. Thanks!
I can run this package in Studio and it works fine, but when I run it from SQL Server Agent, it throws this error. Does anybody know what would cause this problem. This appears to occur during validation for the package because none of the data flow steps run. The connection being used is the same connection used in all of the data flows. If validation is done in order, then prior steps using the same connection are passing validation.
I am exporting 350 tables data from SQL Server 2005 to Access 2003.and getting the below error.
SSIS package "Package2.dtsx" starting.
Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at Data Flow Task, DTS.Pipeline: Prepare for Execute phase is beginning.
Error: 0xC0202009 at Package2, Connection manager "DestinationConnectionOLEDB": 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: "Unspecified error".
Error: 0xC020801C at Data Flow Task, Destination 64 - CLIMBINGEXP [8065]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC004701A at Data Flow Task, DTS.Pipeline: component "Destination 64 - CLIMBINGEXP" (8065) failed the pre-execute phase and returned error code 0xC020801C.
I am working on SQL Server 2005 (x64) with Windows Server 2003 (x64) operating system. I am having a major issue in SSIS. Here is the detailed explanation of the issue :
I have an EXCEL file in 2003 / 2007 version. It contains some data. I want to import the data using SSIS into SQL Server 2005 (x64) database table. I have taken "EXCEL FILE SOURCE" and "SQL Server DESTINATION". It was failed on importing data. Surprisingly it works fine in SQL Server 2005 (x32). Can you please explain why it is NOT woking on (x64) ?
Here is the error code i am getting:
[Excel Source [1]] Error: The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.
Hi All, I am getting the following error if I am using the package "Transaction Option=Required" while running through Sql Job: The AcquireConnection method call to the connection manager "<connection name>" failed with error code 0xC0202009.
while I running the SSIS package on BI environment, I am getting the following error: [Connection manager "<connection name>"] Error: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction.".
I know the alternative solution is to make the "Transaction Option=Supported", but in my case I have run the whole flow in a single transaction. I came to know that this has been fixed in the service pack1(ref. to http://support.microsoft.com/kb/914375). FYI.. some time it was running successful.
I have taken all the necessary step to run the SSIS package in a distributed transaction(like the steps for MSDTC) and also created the package flow in a sequence.
I was going through the link - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=160340&SiteID=1 but all those didn't solve my problem.
If anyone can help me it will be great. or it is a bug in SSIS?
I am struggling with this error and it's starting to get to me!
I have setup a simple project with just a data flow task. In this task, it retrieves a simple record "Select * From Table1 WhereId=1". The connection is an OLE Db connection using Advantage Oledb Provider (a provider for accessing dBase). It is accessing a Novell network drive. I have setup the package to both "EncryptSensitiveWithPassword" and "DontSaveSensitive". Both times i have received this error.
The funny thing is, when I set the package to "EncryptSensitiveWithPassword" and I setup a job to run the package, it never asks me for the password even though I set one up! I have a previous package (few months ago I made) that accessed the same database on the same Network drive and it works! It also asks me for a password when I try to modify or run the package (b/c I set it to "EncryptW/Password").
I am using SSIS 2005 on Windows 2003 server. Using Excel Source to dump the data for staging database. I am getting following error while I execute it through BI studio's execute button.
I have deployed my packages into Sql Server and I am using Configuration File. As my Data Source is Excel, I have changed the connection string during deployment with Server Path. But I am getting the following errors. Actually the File Exist in Path. May I know What is cause of the issue? Do I need to give any permission to execute the package.
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.
component "Excel Source Service Contract Upload" (1) failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
DTS_E_OLEDBERROR, Error Code: 0x80004005 Source: "MS JET DB Engine" Description : Path is not valid
SSIS 2005 MSDN Tutorial - Lesson 1 - subsection namely 'Adding and Configuring the Lookup Transformations ' - in that STEP 7 not working. Not able to select the 'columns' tab.
Anybody worked-out this Lesson1 with the step provided by MSDN.
I have created a SSIS package with a Fuzzy lookup transformation.
It matches on 18 columns, looks for a 95 % match and has 50 variables that are passed through the transformation.
When I run the transformation it fails with the following error :-
Warning: 0x8007000E at Data Flow Task, Fuzzy Lookup [228]: Not enough storage is available to complete this operation. Warning: 0x800470E9 at Data Flow Task, DTS.Pipeline: A call to the ProcessInput method for input 229 on component "Fuzzy Lookup" (228) unexpectedly kept a reference to the buffer it was passed. The refcount on that buffer was 2 before the call, and 1 after the call returned. Error: 0xC0047022 at Data Flow Task, DTS.Pipeline: The ProcessInput method on component "Fuzzy Lookup" (228) failed with error code 0x8007000E. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0x8007000E. Error: 0xC02020C4 at Data Flow Task, Flat File Source [1]: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020. Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread1" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread1" has exited with error code 0xC0047039. Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "Flat File Source" (1) returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.
I have tried all suggestions to fix this e.g. implement SQL Server 2005 service pack 2 - didn't fix it, up your virtual memory - didn't fix it.
I am having an issue with SQL 2005 SSIS package...Win 2003 SP2...SQL 2005...
We receive files in the format of .TRK into an input directory...These files then are copied to a local directory on server and a .bat file loops through renaming each .TRK to MyFile.Txt...MyFile.Txt is then uploaded to a SQL table via DTS...Nothing complicated...The DTS runs fine when MyFile.Txt is placed there manually and executed...The rub is the call through batch file...
Error string: [Microsoft][ODBC SQL Server Driver]Packet size change not honored by server, server size used
Error source:
Help file:
Help context: 0
Here's my trouble shooting...Reinstall SP2 on Windows to get MDAC 2.8 version...MS KB article states that the ODBC registry key HKEY_LOCAL_MACHINESOFTWAREODBCINST.INISQLServerDriverODBCVer should be 3.7 or greater...It's 3.5 on this server...MDAC 2.8 (which is installed with Win2003 SP2) is supposed to take care of installing right driver...All registry keys point to the proper version of sqlsvr32.dll in .WindowsSystem32...
I'm at a loss...Currently we are looking at rewriting the bat file in C# or something similar...I would really like to get running as is...
I'm currently receiving the following error message whilst attempting to install SQL Server 2005 Standard Edition on Windows Server 2003 (32 Bit): Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.
This server already has an install of SQL Server 2000 as the default instance. I'm attempting to install a new named instance of SQL Server 2005.
Extract from log:
<Func Name='LaunchFunction'> Function=Do_sqlPerfmon2 <Func Name='GetCAContext'> <EndFunc Name='GetCAContext' Return='T' GetLastError='0'> Doing Action: Do_sqlPerfmon2 PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007 <Func Name='Do_sqlPerfmon2'> <EndFunc Name='Do_sqlPerfmon2' Return='0' GetLastError='2'> PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007 MSI (s) (4C:FC) [10:20:02:833]: Executing op: ActionStart(Name=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing performance counters,) <EndFunc Name='LaunchFunction' Return='0' GetLastError='0'> MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1281,Source=BinaryData,Target=Rollback_Do_sqlPerfmon2,CustomActionData=100Removing performance counters200000DTSPipelineC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INI) MSI (s) (4C:FC) [10:20:02:849]: Executing op: ActionStart(Name=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing performance counters,) MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_sqlPerfmon2,CustomActionData=100Installing performance counters200000C:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INIC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.HC:Program FilesMicrosoft SQL Server90DTSBinnDTSPipelinePerf.dllDTSPipeline0DTSPipelinePrfData_OpenPrfData_CollectPrfData_Close) MSI (s) (4C:94) [10:20:02:864]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI1683.tmp, Entrypoint: Do_sqlPerfmon2 <Func Name='LaunchFunction'> Function=Do_sqlPerfmon2 <Func Name='GetCAContext'> <EndFunc Name='GetCAContext' Return='T' GetLastError='0'> Doing Action: Do_sqlPerfmon2 PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007 <Func Name='Do_sqlPerfmon2'> <EndFunc Name='Do_sqlPerfmon2' Return='2' GetLastError='2'> PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007 Gathering darwin properties for failure handling. Error Code: 2 MSI (s) (4C!F0) [10:23:46:381]: Product: Microsoft SQL Server 2005 Integration Services -- Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.
You can ignore this and it will complete the installation, but subsequently trying to patch with SP2 will fail on the same sections - Hotfix.exe crashes whilst attempting to patch Database Services, Integration Services and Client Components (3 separate crashes).
I've removed SQL Server 2005 elements and tried to re-install, but it's not improved the situation.
A first chance exception of type 'System.MissingMemberException' occurred in Microsoft.VisualBasic.dll Public member 'Variables' on type 'IDTSPackage90' not found.
Parameter passing in SSIS 2005 sometimes appears to be a cumbursome task. I have been digging into this topic for quite some time and here i note down some simple steps to demonstrate parameter passing at Package level.
(1) Create a SSIS project using Business Intelligence 2005 Or VS 2005.
(2) Create datasource (.ds) and Data Source View as required.
(3) A default SSIS Package by the name Package.dtsx is created. Double click this and you are shown tabs for Control Flow, Data Flow, Event Handlers, Package Explorer. On the Control Flow, drap and drop Execute SQL Task from Control Flow Items in the toolbar.
(4) Lets now create a variable at Package level. Right click anywhere in the control flow box (not on the Task created in Step 3 above). Click on the Variables on the context menu displayed. Variables window appears on the left of the screen. Click the Add Variable box in this window to create a variable. Name it var1 (or whatever you may like), Scope as Package, DataType as String and Value as MyValue. This is only the default value.
(5) Now let us edit the SQL Task created in Step 3. Double on it, on the General tab you can change its Name, Description. Set ResultSet as None. We shall proceed to execute a stored procedure by name MySPName and pass it a parameter. Set ConnectionType as OLE DB. Select the connection you creates in step 2. Set SQLSourceType as Direct input. SQLStatement as MySPName ? . Note the ? mark after the name of the stored procedure. This is important to accept the variable value (var1) created in Step 4.
(6) Select Parameter Mapping tab now. Click on Add button. Select the Variable Name as User::var1. This is the user created variable of Step 4. Select Direction as Input, DataType as Varchar and Parameter Name as @var1. Click on OK now.
(7) This sets up the basic of parameter passing. Compile the project to verify everything works. Right Click on the SQL Task and select Execute Task. This will execute the package taking default value of the variable. This can be used along with dtexec command with /set option to pass the parameter at command prompt.
I am trying to execute an SSIS package from an MS Access 2003 database that imports a table from the Access database into a target table in SQL 2005. I saved the package in SQL 2005 and tested it out. If I run it from the Management Studio Console with Run->Execute ... everything works just fine. However, if I try to run it using "Exec master.dbo.xp_cmdshell 'DTExec /SER DATAFORCE /DTS SQL2005TestPackage /CHECKPOINTING OFF /REPORTING V'" the execution will always fail when the Access database is open (shared mode). It will only work when the Access database is not open. The connection manager looks like this: "Data Source=E:Test.mdb;Provider=Microsoft.Jet.OLEDB.4.0;Persist Security Info=False;Jet OLEDB:Global Bulk Transactions=1". The error is listed below:
Code: 0xC0202009 Source: NewPackage Connection manager "SourceConnectionOLEDB" Description: 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 use ''; file already in use.".
I've installed SQL2005 on a server already running SQL2K on my laptop. SQL2K is the default instance, so I'm trying to connect to SQL2005 using MYSERVERSQL2005 as the instance.
The steps that I've taken are to apply SP2 and enable remote connections (TCP & Named pipes). I've also made sure the SQL Server Browser service is running and enabled.
The error message that I get via SQL2005 client tools is "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)"
I dont understand as to why i am unable to connect to 2005.
In a SSIS Package I have defined a ConnectionManager to a SQL Server 2005. Now I am trying to query data in a Visual Studio for Application Script.
I tried the following: Dim local_SQLConnectionManager As Microsoft.SqlServer.Dts.Runtime.ConnectionManager Dim local_SQLConnection As New System.Data.SqlClient.SqlConnection Dim local_SQLDataReader As System.Data.SqlClient.SqlDataReader Dim local_SQLCommand As New System.Data.SqlClient.SqlCommand
local_SQLCommand.CommandText = "SELECT something" local_SQLDataReader = local_SQLCommand.ExecuteReader() If local_SQLDataReader.Read Then Dts.Variables("Just a variable").Value = local_SQLDataReader.GetString(0) End If local_SQLDataReader.Close()
It always stops on the line with the AcquireConnection: Unable to cast COM object of type 'System.__ComObject' to class type 'System.Data.SqlClient.SqlConnection'. and so on ....
I have the following code in my custom source component's AcquireConnection method -
if (ComponentMetaData.RuntimeConnectionCollection[0].ConnectionManager != null)
{
ConnectionManager cm = Microsoft.SqlServer.Dts.Runtime.DtsConvert.ToConnectionManager(ComponentMetaData.RuntimeConnectionCollection[0].ConnectionManager);
ConnectionManagerAdoNet cmado = cm.InnerObject as ConnectionManagerAdoNet;
if (cmado == null)
throw new Exception("The ConnectionManager " + cm.Name + " is not an ADO.NET connection.");
// Get the underlying connection object. this.oledbConnection = cmado.AcquireConnection(transaction) as OleDbConnection;
if (oledbConnection == null)
throw new Exception("The ConnectionManager is not an ADO.NET connection.");
isConnected = true;
}
The value of oledbConnection is null.
I am trying to invoke the above method within a package that I am trying to create dynamically. Any help ?
ConnectionManager cm = DtsConvert.ToConnectionManager(conMgr);
Microsoft.SqlServer.Dts.Runtime.Wrapper.ConnectionManagerAdoNet cmado = cm.InnerObject as Microsoft.SqlServer.Dts.Runtime.Wrapper.ConnectionManagerAdoNet;
OleDbConnection conn= cmado.AcquireConnection(null) as OleDbConnection;
}
}
In the sample above the conn is null.
To this query Darren replied to use the connection of type ADO.NET:System.Data.OleDb.OleDbConnection, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 to create the connection.
Your call to GetConnectionsOfType("OLEDB"); will return native OLE-DB connections, not ADO.NET connections, using the OleDbConnection.
The connection type for the ADo>NET OLE-DB connection is -
but if user creates an New OLEDB Connection from the Connection Manager panel of the BIDS and selects the same from the custom UI how to get the underlying OLEDBConnection? the CreationName in this case is "OLEDB" and not ADO.NET:System.Data.OleDb.OleDbConnection, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.
