Bug #20963 Connect to DSN fails: 'driver is incapable of supporting the curr env attr'
Submitted: 11 Jul 2006 8:28 Modified: 21 Nov 2006 21:09
Reporter: Frank Maas (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:5.0.4 OS:Windows (Win2003)
Assigned to: Jess Balint CPU Architecture:Any

[11 Jul 2006 8:28] Frank Maas 
Description:
When connecting to a freshly created DSN from a (third party) product, the connection fails:

DIAG [S1010] [Microsoft][ODBC Driver Manager] The driver is incapable of supporting the current environment attributes. (0) 

Extra logging will be attached in additional comments.

Additional note: problem occurs with both User DSN as System DSN (see Bug #20962)

How to repeat:
Create DSN
Launch 3rd party product

Suggested fix:
N/A
[11 Jul 2006 8:29] Frank Maas 
Debug output spilled by MyODBC connector

Attachment: output_myodbc.txt (text/plain), 5.22 KiB.
[11 Jul 2006 8:29] Frank Maas 
SQL Trace output

Attachment: output_sqllog.txt (text/plain), 2.91 KiB.
[11 Jul 2006 13:39] MySQL Verification Team 
Thank you for the bug report. Verified with Access 2003.
[17 Oct 2006 19:20] Mark Matthews 
Frank,

Which 3rd party product are you using (and I assume you've looked at 5.0.5?). This was verified by our bugs team with Access 2003, but I've tested 5.0.5 myself with Access and can link at least simple tables.
[17 Oct 2006 22:31] Frank Maas 
Mark,

I think the problem has gone, or restated: I do not see the error anymore, but I am not able to retrieve anything either. See bug #23398 for more information.
[17 Oct 2006 22:32] Frank Maas 
Mark,

Sorry, I ignored your question. The 3rd party product I am using is APEX Communications IVR software that has an ODBC module. I have no other ODBC clients, but if you can advise me to something simple, open source that I can use to test, I am more than willing to install this.

Regards!
[21 Nov 2006 21:09] Frank Maas 
Successful connected with 5.00.09