Bug #10636 MSSQL 2000 SP4 Linked Server crashes with MyODBC 3.51.11-2

• Submitted: 13 May 2005 22:24
• Modified: 20 May 2005 22:25
• Reporter: Dean Ellis
• Status: Can't repeat
• Category: Connector / ODBC
• Severity: S1 (Critical)
• Version: 3.51.11-2
• OS: Windows (Windows)
• Assigned to: Dean Ellis
• CPU Architecture: Any
• Tags: ODBC5-RC

[13 May 2005 22:24] Dean Ellis

Description:
MSSQL 2000 Linked servers with Connector/ODBC 3.51.11-2 crash when connecting to (or querying) remote servers (perhaps non-Windows servers), reporting that driver had "unexpected catastrophic failure".

3.51.6 works fine; likely a problem with the recent abstraction layer.

How to repeat:
Create System DSN; create Linked Server (via Enterprise Manager); place DSN name in configuration for linked server; attempt to get table list (again via EM).

[20 May 2005 22:25] Dean Ellis

Cannot repeat this; perhaps misconfiguration of DSN

[30 Dec 2005 2:03] P D

Dean,

I am having the same problem just trying to display the tables of mySQL in the Linked Server Section of MS Enterprise Manager. 

It does work for my development box which is Windows 2000/SQL2000 with mySQL Driver 3.51.06. However when I configured the Win 2003/SQL2000 Server with 3.51.11 or .12 it doesnt work. 

So I reverted Win2003/SQL2000 back to version 3.51.06 and it still doesnt work. The configurations are the same and both boxes are trying to access the same mySQL box. Perhaps its the version of the OS?

Patrick