problems installing sqlxml 3.0

I was planning to import data from an XML document to my sql-server using
this guide: http://www.perfectxml.com/articles/X...rtXMLSQL.asp#3
But i can't make the Soap toolkit work (it's shall be installed to use
sqlxml), when i have installed the Soap toolkit and installing the sqlxml it
says that i shall install Soap toolkit to make sqlxml work.
Any that can help me?
//Peter
Soap Toolkit is only needed if you plan on using web services. You should
be able to install SqlXml and use bulkload with no problems even if the
toolkit is not installed. We're working on removing this dependency, not
sure when we'll get that out.
Irwin
Irwin Dolobowsky
Program Manager - SqlXml
http://weblogs.asp.net/irwando
This posting is provided "AS IS" with no warranties, and confers no rights.
"Peter" <dj-pnr@.get2net.dk> wrote in message
news:4061934b@.news.wineasy.se...
> I was planning to import data from an XML document to my sql-server using
> this guide: http://www.perfectxml.com/articles/X...rtXMLSQL.asp#3
>
> But i can't make the Soap toolkit work (it's shall be installed to use
> sqlxml), when i have installed the Soap toolkit and installing the sqlxml
it
> says that i shall install Soap toolkit to make sqlxml work.
>
> Any that can help me?
>
> //Peter
>

problems in Like

hi there,
im facing a wierdo problem

i had data in a foxpro database, i import it to a sqlserver 2000 database with collation Arabic_CI_AS , cause the data is arabic and english

now the data, i can view it and its correct

but the problem is that when i use the like statement to do the search operation

i use this sql:
Select * from Customers where CustomerName like N'%searchText%'

the customerName is of type nvarchar

now if i use one word then it gives me result, but if i use in the search two words (between them space) it dont work, or if i put one word then space it dont work

and in the same time if i copy the customerName from the table and search for it, it gives me the result, even if it was one word or two words or even three!!!

i belive there is a problem in the data, there is something in data i dont know what it is, but this is what it think, i changed the collation, but sometimes it got worst than that

SO IS THERE ANY ONE THAT CAN HELP!!!!!!

:)

thanks in advanceHi,
can you offer more details?
or can you paste your codes in?|||well yeah sure i can offer more details

This is the stored Procedure

CREATE PROCEDURE SP_Customers_GetAllRec

(
@.Searchfield as nvarchar(300)

)

AS
/* SET NOCOUNT ON */
select Customers.ID,CustomerName,RankID,StartDate,EndDate,Address,Username,Password,Email,EnteredBy,CustomerDiscount
from Customers inner join customerDiscount on Customers.CustomerDiscountID = CustomerDiscount.ID
where customername like '%'+@.SearchField+'%' order by CustomerName asc

RETURN
GO

and i send the @.Searchfield as an example N'Super' , this for an example

i tried to write the sql in many forms...but nothing worked!!!

anyone can help?|||Hi,
just to confirm with you, you are using SQL Server 2000?
the query for your statment is something like this format:
SELECT id FROM customer WHERE name like '%ab cd%'
while the query for variables is something like this format:
SELECT id FROM customer WHERE name like '%'+@.testing+'%'

what i dont understand is this :
@.Searchfield as an example N'Super'
if you are searching for the word 'Super', @.Searchfield 's value should be 'Super'
but if you are looking for the word " N'Super' ", i dont think sqlserver can do it because it will take the ' as a quote, thus making your select statment like this :
SELECT id FROM customer WHERE name like '%'N' Super''%'
which obviouslly leads to an error.

in my previous projects what i did was i converted the values ' to ", so that sqlserver will not mistake the quotes.
but of course it needs the assumptions that your data in that field shouldn't have any "s
and that you'll need some extra coding before you call your stored procedure.

Sorry if it didn't help you|||... the N is they way for SQL-Server to treat a string as Unicode instead of ASCII - the N would not be inserted in the LIKE clause.|||:: now if i use one word then it gives me result, but if i use in the search two words
:: (between them space) it dont work, or if i put one word then space it dont work

Ok, example string: "One Two Three".

if you want to find any one of the words "One", "Two", Three" you have to do one LIKE clause per word you try to find and combine them with OR, example:

SELECT
 *
FROM
 Table
WHERE
 column LIKE '%ONE%'
 OR column LIKE '%TWO%'
 OR column LIKE '%THREE%'

... is that what you want to do? If not please post some sample data and search strings that work and that don't.

Hth,

Moon|||Hi All,

Thank you moon, but what the problem is ,its not that i want to find every word, the problem is when i try to find the 2 or 3 words together like :

select * from Table where column like '%one two three%'

all together, i dont know why there is space i cant find the word i want

this is the problem

thank you again|||Further thoughts are: are you sure you have a " " char in you strings? Since you did convert the data from a non-SQL server database, maybe you do not have a real space char that seperates the words but another char that will be displayed as a space (but having different keycode) and thus the query fails.

For testing you could try if one of the following searches will return records:

LIKE '%one%two%three%'
>> match the words in this order with any number of any other chars between them
LIKE '%one_two_three%'
>> match the words in this order with exactly one other chars between them

If so, then you have to find out which char is seperating them, by anylyzing the search result using the SQL-Server string functions for unicode.

Hth,

Moon|||I found some code in Books Online in the section explaining the ASCII function that you might be able to use to help you discover which characters are in your fields exactly. I adapted it slightly - you will need to change the line I have indicated in red:

SET TEXTSIZE 0
SET NOCOUNT ON
-- Create the variables for the current character string position
-- and for the character string.
DECLARE @.position int, @.string char(15)
-- Initialize the variables.
SET @.position = 1
-- change this line of code so that one record from your table is selected
SELECT @.string = somefieldcontainingspaces FROM sometable WHERE someuniquefield = someuniquevalue
WHILE @.position <= DATALENGTH(@.string)
 BEGIN
 SELECT ASCII(SUBSTRING(@.string, @.position, 1)),
 CHAR(ASCII(SUBSTRING(@.string, @.position, 1)))
 SET @.position = @.position + 1
 END
SET NOCOUNT OFF

Normal spaces are ASCII character 32. Which character do you have in your field?

Terri|||hii

sorry i was in an urgent vacation

thank you tmorton i will check it and reply soon

Problems importing TXT files using DTS

Hello,

I've been trying to import a TXT file into an SQL database and I'm having trouble making it work correctly. It is a ASCII text file with over 100,000 records. The fields vary by the number of characters. This can be 2 characters up to 40 (STATE would be 2 characters, CITY is 32 characters, etc.)

I can import the file with DTS. I go in and select exactly where I want the field breaks to be. Then it imports everything as Characters with column headers of Col001, Col002, Col003, etc. My problem is that I don't want everything as Characters or Col001 etc. I want different column names and columns of data to be INT, NUMERIC(x,x), etc. instead of characters every time. If I change these values to anything than the default in DTS it won't import the data correctly.

Also, I have an SQL script that I wrote for a table where I can create the field lengths, data type etc. the way I want it to look, FWIW. This seems to be going nowhere fast.

What am I doing wrong? Should I be using something else than DTS?

Any suggestions are greatly appreciated.

Thanks,
JByou should create a transform data task and connect the text file to the destination though the task.
create the destination table in the xform task and map the data types to the new destinations.

ps while you are there change the column mappings from x individual column copies to 1 single thread it will increase your performance.|||Thanks for the response. I'm going to look into this today. If anyone has any other suggestions, I'd appreciate them too.|||Ruprect,

Come to find out that yesterday I was trying the exact thing you mentioned in your first post. I examined it a little more thorough this morning. The only thing different that I wasn't using 1 thread.

I have 94 columns worth of data. If I select the first 30 columns it will import the text and insert it into the table with appropriate column headings to perfection. The first 30 columns are all character fields.

At Column 31 the first integer field appears. It will stop and give me an error message. It says this, "... conversion error: Conversion invalid for datatypes on column pair 1 (source column 'Col031' (DBTYPE_STR), destination column 'MARKETVALUE' (DBTYPE_I4). There are all numbers as well, no letters or symbols in these columns.

I'm fairly certain I could convert the column to character and it would work fine. The problem is that I need the column to be an integer (as well as my other numeric columns) to perform various mathematical queries.

Thanks again,
JB|||Yeah, you've got bad data...

I would load the data to a table of a varchars...like you have now

Think of it as a staging table

Then audit the data...

For example

Col030 should be a date

Find out all the rows with bad dates

SELECT * FROM myTable99 WHERE ISDATE(Col030)=0

Will show you rows sql doesn't consider a date...

Same with numerics

ISNUMERIC(col1)=0

You won't be able to load those rows to your final destination table

either fix the input file, or ignore the rows...

in any case, go to who ever gave you the file and say...see here...this is garbage...fix it...

and wait a week while they try to figure out what to do...

Golf, Tennis, Long lunches...whatever you want...|||Brett,

You are correct it was bad data. That should have been the first place I looked.

I went into Query Analyzer and ran the query you posted on the columns of data that I wanted to turn into numeric data. 5 out of 32 potential columns had issues. It seems that some of the fields that I wanted to turn into numeric values had blank values. I guess you can't convert a blank character <NULL?> into a blank number.

Anyways, the problem is solved.

Thanks,
JB

Problems importing backup DB into Express

I am trying to import (unless there is a better way) a database (which I made a backup of) from a SQL Server 2005 v8.0 machine into my SQL Server Management Express 2005 machine so that I can have a full complete copy of the backup database in express. The purpose is so that I can treat it as a template, get rid of tables, views, columns I dont need and repopulate them with different data to compliment my other project, which involves auto tagging of .mp3's.

As an analogy: copy an Excel spreadsheet, open it in Excel, delete cells you dont need, keep the rest but fill in with different data. Kinda like that but with SQL.

I can't figure out exactly how to do this with Express 2005. How do you import or otherwise a backup database from SQL Server 2005 v8.0 and get it into Express?

My backup file is called: WebBackup_KUOW_Program_Full

I've tried renaming it using both .mdf and .bak when I Right-Click Databases and select Restore. Fill in everything then click ok. I keep getting this error message:

TITLE: Microsoft SQL Server Management Studio Express

Restore failed for Server 'INTRA\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476

ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program Files\Microsoft SQL Server\MSSQL\Data\kuow_program.mdf" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476

BUTTONS:

OK

Can anyone help me with this please! Keep in mind I'm not a SQL guru. Thanks in advance for any assistance.

Thats pretty easy, the original data and log file is stored in the backup, if you want to store the file in another path than it was originally placed in (e.g. if you don′t have that drive letter on the new machine) you will have to change the path in the restore dialog. The data and logfiles will then be placed at the specified location.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks