Re: Debugging malfunctioning ODBC -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Debugging malfunctioning ODBC
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Sat, 11 Dec 2021 16:21:36 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hello,

a follow-up from my post on August 20 for any interested reader:

Today I downgraded the ODBC components on two machines from version 2.3.7 (Debian 10) to 2.3.4 (Debian 9) of Unixodbc, because I firmly believe things have worked with Debian 9 before.

Reference: https://archive.midrange.com/midrange-l/202108/msg00487.html

Result: Same behavior as before: Error in host server data stream. So I guess it might be indeed something date-related.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Debugging malfunctioning ODBC , Stephen Landess

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.