Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
3.1.7
-
None
-
Windows Server 2019 Datacenter; MariaDB Server 10.3 x64
Description
Similiar to odbc-275 the process using the odbc driver crashes after some time
(mostly while idling) with only the following output dumped in the event log:
Name der fehlerhaften Anwendung: #########, Version: 0.1.0.0, Zeitstempel: 0x5e9d5491 |
Name des fehlerhaften Moduls: maodbc.dll, Version: 3.1.7.0, Zeitstempel: 0x5e8ce4bc |
Ausnahmecode: 0xc0000409 |
Fehleroffset: 0x000a119f |
ID des fehlerhaften Prozesses: 0x1658 |
Startzeit der fehlerhaften Anwendung: 0x01d6171314a8a0f3 |
Pfad der fehlerhaften Anwendung: C:\Users\########\Desktop\Local\#########
|
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\MariaDB\MariaDB ODBC Driver\maodbc.dll
|
Berichtskennung: 06c71983-5062-4674-8934-29d5d32041c1 |
followed by a mysql warning entry with the text similiar to:
Aborted connection xxxx to db: '#########' user: '############' host: 'localhost' (Got an error reading communication packets) |
Contrary to the linked issue, my connection string already contains the full ip adress of the host (127.0.0.1 on the current configuration). I could not reproduce the issue on our old Windows Server 2012 development machine.
Attachments
Issue Links
- duplicates
-
-
- Closed
-