Bug #36996 | Data provider or other service returned an E_FAIL status | ||
---|---|---|---|
Submitted: | 27 May 2008 6:45 | Modified: | 18 Nov 2009 14:32 |
Reporter: | Alexey Palagin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | 5.1 | OS: | Windows (xp sp2 rus) |
Assigned to: | CPU Architecture: | Any | |
Tags: | ODBC, VB |
[27 May 2008 6:45]
Alexey Palagin
[6 Jun 2008 23:16]
Jess Balint
Verified just as described. Thanks for a good bug report.
[7 Jun 2008 0:17]
Jess Balint
patch + test
Attachment: bug36996.diff (application/octet-stream, text), 2.28 KiB.
[7 Jun 2008 0:18]
Jess Balint
The core issue here is that cp1251 is not supported in the client/driver due to bug#32831. Patch adds an error if it encounters an unsupported client character set.
[17 Nov 2009 20:35]
Lawrenty Novitsky
Approved and pushed as rev#858. Will released in 5.1.7 Bug is actually duplicate of the Bug#39831(or vice versa) Patches intersect. So from with patch was wchar part only used, Testcase doesn't make sense any more since 5.1.6 was already linked against libmysll with Bug#32831 fixed.
[18 Nov 2009 14:32]
Tony Bedford
An entry has been added to the 5.1.7 changelog: When opening ADO.Recordset from Microsoft Access 2003, a run-time error occurred: ErrNo: -2147467259 ErrMessage: Data provider or other service returned an E_FAIL status.