Bug #117271 | ODBC Open has "Catastrophic failure" | ||
---|---|---|---|
Submitted: | 22 Jan 16:02 | Modified: | 23 Feb 3:43 |
Reporter: | Rich Alford | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 9.0+ | OS: | Windows |
Assigned to: | Bogdan Degtyariov | CPU Architecture: | x86 |
Tags: | ODBC Catastrophic vbscript |
[22 Jan 16:02]
Rich Alford
[23 Jan 3:43]
Bogdan Degtyariov
Hi Rich, Thank you for the detailed description of the problem and for the VB test case. I followed the steps you indicated, but was not able to repeat the problem. Here is the output from the batch file: ..................... D:\Projects\bugs\117271>run_test.bat LICDB_CONNECT_STRING=Driver={MySQL ODBC 9.2 ANSI Driver};Server=localhost;DATABASE=odbctest;UID=*******;PWD=*********; D:\Projects\bugs\117271> .................... The script just connected to MySQL Server and exited without errors. However, the problem rings a bell and the script in your environment might be experiencing crash caused by runtime libraries inside Visual C++ Redistributable package 2015-2022 version 14.36. Updating the VC++ package to version 14.40 or newer should resolve the problem with the crashes. Make sure that the redistributable package for x64 architecture is updated. Please try this and let me know if it helped.
[24 Feb 1: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".