ODBC install problem

ODBC install problem

am 17.10.2006 17:40:44 von nark

I just downloaded ODBC drivers from the mySQL web site but whenever I try
to create a DSN I get a system 1157 error

The driver does show up ok in the windows control panel

I cant find any information on this at all can anyone help please?

nark

Re: ODBC install problem - ODBC Manager freezes when creating DSN

am 17.10.2006 23:39:34 von Kunle Odutola

> I just downloaded ODBC drivers from the mySQL web site but whenever I try
> to create a DSN I get a system 1157 error
>
> The driver does show up ok in the windows control panel
>
> I cant find any information on this at all can anyone help please?

I may have the same problem. I using mysql-connector-odbc-3.51.12-win32.msi
with a MySql 4.1.9-nt server instance running on Windows Server 2003 SP1.

After installing the driver, I tried to create a DSN using the ODBC Manager
in Windows. I get as far as the MyODBC dialog. After entering the connection
details, I press "Test" to test the connection. At this point the process
simply freezes - with little CPU activity - and has to be forcibly
terminated. The same thing happen if I enter no connection details at all
and just press the Test button.

Has anyone else experienced this issue (and hopefully has a
solution/workaround)?.

Thanks

Re: ODBC install problem - ODBC Manager freezes when creating DSN

am 18.10.2006 02:04:12 von Kunle Odutola

I've just had the same result with mysql-connector-odbc-3.51.14-win32.msi
trying to connect to a MySql 4.1.21-community-nt server instance running on
Windows Server 2003 SP1.

The ODBC Manager process freezes (couldn't kill it via task manager - it
froze task manager too). Everything else seems to continue working fine
(there is minimal-low cpu usage).

Re: WORKAROUND - ODBC Manager freezes when creating DSN

am 18.10.2006 20:16:49 von Kunle Odutola

This issue seems to be triggered by the presence of the ZoneAlarm firewall
product (perhaps other firewalls too?). Not sure why MySql/MyODBC objects
particularly since other Client/Server RDBMS systems work fine with
ZoneAlarm and other firewalls. In any case, **uninstalling** ZoneAlarm is an
effective workaround for this issue here.

It isn't a satisfactory situation by any means and effectively kills off
MySql/MyODBC for me.