MySQL Bugs: #18069: Request returded with SQL

Bug #18069	Request returded with SQL_ERROR.
Submitted:	8 Mar 2006 11:36	Modified:	1 Jun 2006 8:11
Reporter:	Goodspeed Lin	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	MyODBC 3.51.12	OS:	Windows (Windows Server 2003 std.)
Assigned to:		CPU Architecture:	Any

Description:
I set DSN information in the control panel.
When I select darabase or press "TEST" button, the error occurs :

 "Request returded with SQL_ERROR."

How to repeat:
I use MyODBC to connect MySQL 5.0.
I set DSN information in the control panel.
When I select darabase or press "TEST" button, the error occurs :

 "Request returded with SQL_ERROR."

The MySQL user and pwd is correct, coz I can use it login phpMyAdmin
and run PHP pages.

I got the same problems more than two times(two servers).
I use MyODBC to connect MySQL 5.0 for ASP.

Environment :
 Windows Server 2003 Std.
 Apache 2.0.55
 PHP 5.1.2
 MySQL 5.0.18
 MyODBC 3.51.12/5.0.0alaph

Request returned with SQL_ERROR

Attachment: 未命名--1.jpg (image/jpeg, text), 51.87 KiB.

I use Outpost professional firewall.
I have to try disabled it, but the error is never gone.

like the case :
  http://forums.mysql.com/read.php?37,55400,71229#msg-71229

Hi. Thanks for your report. This usually happens when server you entered in configuration is not running. Try starting server service first. If this is not the case, I'll investigate further.

Hi,

The MySQL service is always on.
Coz the PHP pages is running normally.
The web and mysql server is in the same machine.

And when I use myodbc 5.0.0 alaph, the returned msg can't be showed.

Are you using System DSN or File DSN? If you're using File DSN, what did you put under Advanced tab (connection string and all)? 
What are your settings for System DSN?

Hi,

I use System DSN.

data source name = act
server = localhost
user = mysql user
password = ********
The others settings are by default.

The settings is same as web service.

Are you able to connect from cmd line tool (mysql - u...) with the same parameters?

When I type "mysql -u root -p" in cmd And type the pwd, I got the error message.

ERROR 2013 (HY000): Lost Connection to MySQL server during query

What's happened?
The user and password is corrrect, I can use it to login phpMyadmin.

Strange. This error can also be caused by the windows firewall (depending on what you're doing, like running it manually from the prompt). Try going to start/settings/copntrol panel/windows firewall.
Click on the exceptions tab and make sure mysqld is ticked, you can also click edit change scope and set "my network only" so it has no internet access.
Also can you please post output of show variables and show status commands and your my.ini file.

Can you provide result for netstat -a? Maybe MySQL server is not on port 3306, as expected by default settings? Check firewall by executing "telnet localhost 3306". If there's no answer, then connection is blocked or no program listening on port 3306.

Hi,

I already upload the image.
I have disabled the Microsoft firewall.
About the firewall, I'll check OutPost.

Maybe this will help: http://bugs.mysql.com/bug.php?id=14950

24 Nov 2005 13:00] Nekhayev Dennis

I have got the same problem.

Try to remove Microsoft Firewall Socket Provider from registry.
I did it with Autoruns (www.systeminternals.com).
The registry key:
HKLM\System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9

run autoruns

Attachment: autoruns.png (image/png, text), 17.84 KiB.

I didn't see about "Microsoft Firewall Socket Provider" words.
How do I remove or disable it ?

If we can try one more thing. Please try to remove password from the account you're using to connect (remember to flush privileges!) and then try to connect again. Inform me of the result.

I have been to add a acoount, flush all privilege, and remove the password.
I can use it to login phpMyAdmin with no password.
But I use it to login cmd, it returned:

ERROR 2013 (HY000): Lost connection to MySQL server during query

PS. The time, outpost is on !

I have a very nearly identical situation. Same error messages, same conditions. The only difference is that I am able to successfully login at the cmd prompt using mysql.exe. 

I have tried turning off my firewalls completely. (I'm using ZoneAlarm in addition to the WinXP firewall.)  And the message in the ODBC Data Source Administrator persists. 

I have also tried removing the password on the account as suggested above, with negative results.

I'm running MySQL 5.0 and WinXP SP2.

I should mention: I'm running the database on the localhost.

Sorry for the triple post, but I'm still working on the problem and want to be sure the response I get isn't to go do something I've already done. :)  Anyway, I completely uninstalled ZoneAlert (as suggested elsewhere) and also completely turned off my Windows XP Firewall, and even turned off my antivirus software. Then I rebooted into that completely naked state, and tried to connect. The same error messages still showed up. I can't think of anything else I can do. (I have since turned all the protection back on - just for the heck of it - tried again with predictable results.) Dead end, brick wall. Where can I go from here?

Okay, so now it's a quadruple post. Sorry. 

I now have it working perfectly. I backed up my database, uninstalled MySQL without uninstalling MyODBC, reinstalled MySQL, and restored my database. It immediately started working as though nothing was ever wrong.

Zone Alarm is up and running, and needed no adjustments of any kind, and the same can be said of the Windows Firewall and my antivirus software.

Whatever the bug is, it appears to have nothing to do with Zone Alarm. Hopefully, you'll find that to be useful information.

Hi all. Mashall, tanks for your findings. It was the next thing I would have suggested. These kind of errors ("...does not work on my machine...") are hard to reproduce. Dolittle Lin, can you please do as Marshall sugessted:
"I now have it working perfectly. I backed up my database, uninstalled MySQL
without uninstalling MyODBC, reinstalled MySQL, and restored my database. It
immediately started working as though nothing was ever wrong." and inform me of results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

When I removed the firewall(Outpost), MyODBC is running normally.
I use NOD32 antivirus, so it's not NOD32 business.
I use Outpost for a long time(over five years) and MyODBC together.
The problem seem occur MyODBC 3.51.12 & .11.
I use MySQL 5, so must be upgrade MyODBC.

Hi. I am not familliar with Outpost firewall. Can you point me to where I can get freeware version so I can test?

http://www.agnitum.com/products/outpost/download.php

Outpost Personal Firewall Pro gives you the latest in personal firewall technology, making it the clear security choice for your system. Explore the power and ease of use of Outpost Firewall - download  the free 30-day trial version. 

From 2.1 to 3.5 version, the error has been existed.

Thank for your testing :)

Thanks for your input.

Hi. I installed Outpost firewall with most options set to common settings. I am unable to reproduce the error you get which leads me to conclusion that something about your firewall configuration blocks MyODBC attempt to connect.
Environment:
MySQL server 5.0.22-log (WinXP SP2 - windows firewall completely disabled, localhost), 5.0.23-debug (Suse 10.0 linux, Suse firewall  configured to open ports 3306 and 3307)
MyODBC 3.51.12 GA

Port and address Windows use to set up file DSN

Attachment: 18069.jpg (image/jpeg, text), 24.91 KiB.

Hello,

I just dl MySQL 5.0.22 to try.
The Windows XP platform can be running normally.
But the Windows Server 2003 is still getting the same problem.

1. can't use System DSN to connect MyDOBC.
2. cmd can't connect.

The error statement is same as before.
And I have to try disabled Outpost, it's same as not yet disabled.

Hi. I am informing you that we conducted test on W2k3 machine with Outpost running and found no problem. Please recheck your system / firewall settings.