Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts

Friday, March 30, 2012

Problems ith Connection string to SQL Express

My application is usningtraditional connection string:

<

addkey="DbConnection"value="driver={SQL Native Driver}; provider=SQLNCLI;server=localhost;trusted_connection=yes;database=ebay" />

It works fine with database attached to SQL Server, how do I make this working with SQL Express attachable file in data directory?

I have tried this, but it does not work:

Provider=SQLNCLI;Server=RAF001\SQLExpress;AttachDbFilename=..\TestSite\App_Data\ebay.mdf;Database=ebay;Trusted_Connection=Yes;

Wednesday, March 28, 2012

problems in editing a record... why? help pls....

can someone help me why it produces an error...

error is: ERROR 22001 Microsoft ODBC SQL Server Driver SQL Server STRING or data of BINARY was cut short.
ERROR 01000 Microsoft ODBC SQL Server Driver SQL Server statement was ended.

This is my code here for editing a record...

Protected Sub Button_save2_Click1(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button_save2.Click
'||||| Create string connection
Dim StrConn As String = "Dsn=MS_PKG01;UID=emiline;APP=Microsoft? Visual Studio? 2005;WSID=MSHNP200603;DATABASE=MS_PKG01;Trusted_Connection=Yes"
'||||| Create connection object
Dim MyConn As Odbc.OdbcConnection = New Odbc.OdbcConnection(StrConn)

'||||| Open connection
MyConn.Open()

'|||| Create odbcCommand object
Dim Update_record As New Odbc.OdbcCommand("UPDATE TM0001 SET TM0001.syain_name = ?, TM0001.syain_pass = ?, TM0001.office_id = ?, TM0001.birth_date = ?, TM0001.empl_date = ?, TM0001.user_iden = ? ", MyConn)

Dim hireYear As String
Dim hireMonth As String
Dim hireDay As String
Dim date_hire As String

hireYear = DropDownList_hire_yr.Text
hireMonth = DropDownList_hire_mo.Text
hireDay = DropDownList_hire_day.Text

date_hire = hireYear + "/" + hireMonth + "/" + hireDay

'|||| Add command parameters
Update_record.Parameters.Add("@.P1", OdbcType.Char, 8).Value = TextBox_id.Text
Update_record.Parameters.Add("@.P2", OdbcType.Char, 20).Value = TextBox_name.Text
Update_record.Parameters.Add("@.P3", OdbcType.Char, 20).Value = TextBox_pswd.Text
Update_record.Parameters.Add("@.P3", OdbcType.Char, 40).Value = DropDownList_office.SelectedValue
Update_record.Parameters.Add("@.P3", OdbcType.Char, 2).Value = date_hire
Update_record.Parameters.Add("@.P3", OdbcType.Char, 10).Value = TextBox_bday.Text
Update_record.Parameters.Add("@.P3", OdbcType.Char, 1).Value = DropDownList_iden.SelectedValue

'|||| Execute command
Update_record.ExecuteNonQuery()

'|||| Close connection
MyConn.Close()
End Sub
End Class

I modify some codes already but still same error...

my code:

'||||| Create connection object
Dim MyConn As Odbc.OdbcConnection = New Odbc.OdbcConnection(StrConn)

'|||| Create odbcCommand object
Dim Update_record As New Odbc.OdbcCommand("UPDATE TM0001 SET TM0001.syain_name = ?, TM0001.syain_pass = ?, TM0001.office_id = ?, TM0001.birth_date = ?, TM0001.empl_date = ?, TM0001.user_iden = ? where syain_id = ? ", MyConn)

id_user = TextBox_id.Text
name = TextBox_name.Text
pass = TextBox_pswd.Text
office_id = DropDownList_office.SelectedValue
bday = TextBox_bday.Text
iden = DropDownList_iden.SelectedValue

hireYear = DropDownList_hire_yr.Text
hireMonth = DropDownList_hire_mo.Text
hireDay = DropDownList_hire_day.Text

date_hire = hireYear + "/" + hireMonth + "/" + hireDay

'|||| Add command parameters

Update_record.Parameters.Add("@.P1", OdbcType.Char).Value = name
Update_record.Parameters.Add("@.P1", OdbcType.Char).Value = pass
Update_record.Parameters.Add("@.P1", OdbcType.Char).Value = office_id
Update_record.Parameters.Add("@.P1", OdbcType.Char).Value = date_hire
Update_record.Parameters.Add("@.P1", OdbcType.Char).Value = bday
Update_record.Parameters.Add("@.P1", OdbcType.Char).Value = iden
Update_record.Parameters.Add("@.P1", OdbcType.Char).Value = id_user


'||||| Open connection
MyConn.Open()

'|||| Execute command
Update_record.ExecuteNonQuery()

'|||| Close connection
MyConn.Close()

|||

Hi,

i think a textfield has more data as permitted, so the update command crashed. You can inspect the prepared SQLCommand inside the Update_record object and try to execute this command direct in the database (Query Analyzer or Database Command Prompt Interface).

Regards
Marc Andre

|||

hmmm i already check it and there is nothing wrong...

and whenever i input a new record it always satisfy the condition in the data type...

but still i dont why when i edit it generates error in my code...

hmmm another thing that i observe in my code is that when

i click the save button when editing it doesnt change anything...but the first record or the initial record always shows...

i tried putting is postback but nothing happens...

everytime i press the save button to saved my changes in the data the initial entry shows...

coz in my pageload the initial entry or the first record in the dabse is shown...

hmmm what do u think?

Problems In Connecting Using New Driver

I tried using the new MSSQL 2005 driver which I downloaded from
http://blogs.msdn.com/dataaccess/ar...28/475032.aspx.
But I had problems in connecting to the database using it.
I used the following lines to make the connection.
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
Connection con1 =
DriverManager.getConnection("jdbc:sqlserver://localhost;databaseName=BCTEST"
,
"fiorano", "fiorano123");
I got the following error.
com.microsoft.sqlserver.jdbc.SQLServerException: Failed
Logon:com.microsoft.sqls
erver.jdbc.SQLServerException: DBComms.error reading input. Context:Read
packet
header, Unexpected end of stream, readBytes:-1, negative read result,
PktNumber:
0, ReadThisPacket:0, PktDataSize:4,096
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown
Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at JDBCTestYukon.main(JDBCTestYukon.java:17)
I even tried with the simpler URL "jdbc:sqlserver://localhost" but I got the
same error.
Please help.If I use Type1 driver like below its working fine.
java.lang.Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connection1 =
java.sql.DriverManager.getConnection("jdbc:odbc:DEV329;user=sa;password=ontr
ack20");
But for the thin driver getteing the same exception..I need to upgrade
my Java version'

Monday, March 26, 2012

Problems executing DML via linked server

Hey folks..
I have a linked server that connects to a DB2 database through the OLE DB
for ODBC Providers driver. I have a DSN created and can, through the linked
server run SELECT statements to my heart's content. When I want to run a
simple DELETE, for example (DELETE HCEDB.APPLQUE2), I get the following
error.
Server: Msg 7345, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' could not delete from table '"HCEDB"."APPLQUE2"'.
User did not have sufficient permission to delete the row.
[OLE/DB provider returned message: Multiple-step OLE DB operation generated
errors. Check each OLE DB status value, if available. No work was done.]
[OLE/DB provider returned message: [IBM][CLI Driver] CLI0150E Driver not
capable. SQLSTATE=S1C00]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::DeleteRows
returned 0x80040e21: DBROWSTATUS_E_PERMISSIONDENIED].
I have gone to a colleague's machine to use a DB2 Client and authenticated
using the same user specified in both the DSN and Linked Server and was able
to execute the DELETE. Any ideas as to cause and resolution?
Thanks..
Peace,
Gary HampsonIf you are using a DELETE FROM (Table Name), beware.
I was doing the same thing on a DB2 Database with some test data given to me
, and I would get the same error when I tried to delete using the Linked Ser
ver, where if I tried to do it straight in the DB2 Console, I could execute
without any problems.
So I ran an Event Monitor. Happens out, the Microsoft OLE DB Provider for OD
BC Drivers turns it into count(*) many "DELETE FROM TABLE WHERE field = ?".
So if your table has 1000 rows, you'll have 1000 Delete Statements run in se
quence. Very inefficent, but it gets the job done. The reason for my error w
as that there were 3 rows that were identical to each other, and so it had 3
identical "DELETE FROM" statements.
My solution: Deleted the replicated rows. It apparantly was an oversight whe
n creating the test data.
I still have an issue with it producing all those Delete Statements though.
I'm currently looking into other ways of doing it.

Wednesday, March 21, 2012

Problems connecting from reporting services to Oracle using odbc connection and asp.net 2.0

Hi,

Anybody have a clear idea why I might have problems connecting from reporting services to Oracle 9i database using the Microsoft ODBC driver? Getting following error

"Cannot create a connection to data source 'oracleName'.

  • ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
  • "

    I have the data source correctly set-up thought. Is it a permissions problem?

    Thanks.

    When you say you have it set up correctly, do you mean that you were able to connect to it from other applications? or what exactly?

    Assuming it is correct, try using the Microsoft OLE DB Provider for ODBC. This always works for me.

    >L<

  • Monday, March 12, 2012

    problems

    Microsoft OLE DB Provider for ODBC Drivers
    error '80004005'
    Specified driver could not be loaded due to system error
    126 (SQL Server).Problem with the MDAC installation of the Driver or dependent component.
    Stop all applications that use SQL Server and ODBC. Try re-installing the
    latest MDAC stack for your client.
    Install the MDAC security patch:
    http://www.microsoft.com/technet/tr...chnet/security/
    Bulletin/MS04-003.asp
    Thanks,
    Kevin McDonnell
    Microsoft Corporation
    This posting is provided AS IS with no warranties, and confers no rights.|||In the article on this link you will find a lot of info how to troubleshoot
    this error: http://support.microsoft.com/defaul...b;EN-US;306518.
    Dejan Sarka, SQL Server MVP
    Associate Mentor
    Solid Quality Learning
    More than just Training
    www.SolidQualityLearning.com
    "pedro" <anonymous@.discussions.microsoft.com> wrote in message
    news:041e01c3dede$90fd4810$a301280a@.phx.gbl...
    quote:

    > Microsoft OLE DB Provider for ODBC Drivers
    > error '80004005'
    > Specified driver could not be loaded due to system error
    > 126 (SQL Server).
    >

    problemas con el SQL 7.0

    Microsoft OLE DB Provider for ODBC Drivers
    error '80004005'
    Specified driver could not be loaded due to system error
    126 (SQL Server).
    alguien puede darme alguna posible solucionTry running Dependency Walker with any ODBC application. There is a
    profiling option that will help you identify the problem component.
    www.dependencywalker.com
    Thanks,
    Kevin McDonnell
    Microsoft Corporation
    This posting is provided AS IS with no warranties, and confers no rights.

    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

    Wednesday, March 7, 2012

    Problem with WHERE clause when column length > 255

    Hello, I am using the JDCB-ODBC driver for my app, but one of the columns in my WHERE clause is 255 characters long. Because of this no rows are returned even though the statement should return 1 or 2 rows. I've tried other JDBC-ODBC drivers too and they have the same problem. Additionally, I've tried using RTrim(), Substring(), etc and it still will not work...any ideas? Is it a driver bug? Anyone know of a driver that will work?

    Sample code...

    ResultSet rs = dbRetrieve.getStatement().executeQuery( sql ) ;
    if (rs.next()) {
    // Never gets here
    }

    Thanx!Have you run the query (verbatim) in Microsoft Query Analyzer and seen the rows returned?

    -PatP|||Originally posted by Pat Phelan
    Have you run the query (verbatim) in Microsoft Query Analyzer and seen the rows returned?

    -PatP

    Yes, I have and it returns results. Additionally, I've removed the column from the where clause in my java file and it returns data, but of course its uselys because I need that column in the where clause...

    Thanks...|||Hmm... Microsoft's JDBC driver says it will support upt to 4000 character strings. Have you used profiler to see exactly what's being sent to your SQL server?|||Since the SQL code works ok from Query Analyzer, we can assume that SQL Server to the MDAC on your client works fine. The problem must be in the JDBC driver or beyond it.

    Which JDBC driver are you using? Does it have any length limitations that you are aware of (or does it keep them as surprises for the unwary)? As Peter pointed out, the Microsoft JDBC driver handles big strings (I've run 2 Kb columns out through it).

    Just as another thought, are you certain that your Java app is behaving and actually submitting what you expect it to.

    -PatP