Bug #12483 | ODBC driver failed | ||
---|---|---|---|
Submitted: | 10 Aug 2005 6:50 | Modified: | 2 Dec 2005 14:36 |
Reporter: | varsha s | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MaxDB | Severity: | S1 (Critical) |
Version: | 1.0 | OS: | Windows (Windows XP Professional) |
Assigned to: | Bugs System | CPU Architecture: | Any |
[10 Aug 2005 6:50]
varsha s
[2 Oct 2005 8:46]
Valeriy Kravchuk
Thank you for a problem report. Sorry for not being able to hande it properly for such a long time. When your remote ODBC connection fails, can you, please, try to connect from other machine and inform about the results. Do you have SP2 installed on any of your XP machines used in this setup? Please, try also to use newer ODBC deriver available for download at http://dev.mysql.com/downloads/maxdb/7.6.00.html#ODBC_Driver
[3 Oct 2005 4:53]
varsha s
Thanks for your response though it is after long time. When that problem arised i tried to connect to that system from other system too but I was not able to connect to it. SP2 is installed on that system. Will the newer version installation will be able to solve this problem? Are there any modifications did in newer version related to this issue? If so I can suggest client to use newer version.
[2 Nov 2005 14:36]
Ulf Wendel
Hi, do you keep the connection open over two, three days before you experience the connection break down or do you connect every two minutes? Regards, Ulf
[22 Nov 2005 9:01]
[ name withheld ]
We have same problem on WinServer 2003. It doesn't work when we run it locally, with connection string driver=sap db;servernode=127.0.0.1;serverdb=DB_NAME;uid=USER_NAME;pwd=USER_PASS All ODBC drivers are 7.06.00.00 (as far as I know; I have no access to machine personally)
[22 Nov 2005 9:10]
[ name withheld ]
...and, unlike original poster, it occurs immediately on 1st OdbcConnection.Open call (c#). at the same time, we are able to connect with sql studio.
[3 Dec 2005 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".