Bug #79124 | myodbc5w.dll causes crash in Web Application using Crystal Reports | ||
---|---|---|---|
Submitted: | 4 Nov 2015 17:32 | Modified: | 11 Feb 2016 12:17 |
Reporter: | Phil Smith | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 5.3.4 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash, crystal, myodbc5w, ODBC, windows |
[4 Nov 2015 17:32]
Phil Smith
[1 Feb 2016 11:35]
Chiranjeevi Battula
Hello Phil Smith, Thank you for the bug report. I tried to reproduce the issue at my end using Microsoft Visual Studio 2013, with MySQL Connector / ODBC 5.3.4, but not seeing any issue in calling Crystal Reports. Could you please provide repeatable test case (exact create table statements, MySQL version, sample data, sample rpt etc. - please make it as private if you prefer) to confirm this issue at our end? Thanks, Chiranjeevi.
[11 Feb 2016 11:03]
Phil Smith
Chiranjeevi, Many thanks for your efforts so far. I knew this would be difficult to track down and at the moment I can't even reproduce it myself. However, on the production server (2012) I mentioned, it's still happening on average about once a day. I will keep trying to produce a repeatable test case, but in the mean time is it possible to glean anything from the DebugDiag crash dump? Or is there anything else I can run on the production server to give us useful information whenever the crash occurs? Thanks, Phil.
[11 Feb 2016 12:17]
Chiranjeevi Battula
Hello Phil Smith, Thank you for your feedback. I could not repeat this issue at my end with the provided information. If you can provide more information with exact test case, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL. Thanks, Chiranjeevi.