Bug #8896 Library Error Number 3
Submitted: 2 Mar 2005 18:19 Modified: 19 Sep 2005 12:42
Reporter: Robert Fox Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.1.5 OS:Windows (Windows XP)
Assigned to: Mike Lischke CPU Architecture:Any

[2 Mar 2005 18:19] Robert Fox
Description:
While attempting to delete several rows in a table from a result set, an error occured during the delete process. After that error occurred, it seemed to corrupt my MySQL Query Browser install. The software began to function inconsistently and I was unable to perform normal query operations. Now, whenever I try to load MySQL Query Browser, it fails to completely load properly after I authenticate to the server and gives me the message Library Error Number 3 at the bottom of the screen. Many of the functions now do not work at all. This continues to happen even after I have re-installed the software several times which suggests that either the Windows registry has entries which are bad relating to the software or the software is no longer functioning with other programming libraries on Windows. This is starnge, since it was working just fine before the error occurred with the delete operation.

How to repeat:
I'm not sure how to get this error to repeat since it occurred when I attempted to delete several rows (over 100) from a result set. I had deleted rows from result sets before and did not receive this error, but perhaps by attempting to delete several hundred rows from a result set, this error could be duplicated.

Suggested fix:
I'm not sure, but I would appreciate some advice on how to get the software operational again since it is leagues better than MySQL CC which is what I've been using for quite a while.
[2 Mar 2005 21:53] Jorge del Conde
Verified when deleting 140 rows:

Access violation at address 00578F6E in module 'MySQLQueryBrowser.exe'.  Read of address 00000006
[2 Mar 2005 22:29] Robert Fox
Update: I'm not sure why the delete operation resulted in an error - that must be a bug. However, I did find out why I wasn't able to run the Browser successfully again. This is possibly only an issue on Windows XP. I found out that there are some XML files that are deposited in the Windows user directory under 'Application Data'. Somehow when the delete operation performed it's error, at least one of those files was corrupted. When I deleted those files and reinstalled the software, it seemed to correct the problem.
[17 Mar 2005 15:06] Leo Eggink
Error started after deletion of 4 records in version 1.1.5
Error persists after removal 1.1.5 and install of 1.1.6
[8 May 2005 17:24] Philip Howarth
Same problem exactly on WIN2K and Query browser 1.1.3
Removing and re-installing SQL Query Browser (updated to 1.1.9) had no effect.
Deleting the XML files, as mentioned above, got things going again.
[16 May 2005 15:33] David Lesieur
I just got the same problem with Query Browser 1.1.5 on XP. Deleting the XML files in Application Data\MySQL fixed the problem. I did not need to re-install the application.

I am unable to reproduce it, but it happened after deleting all the rows from a table (which had only about 5 rows) and refreshing a SELECT on that table in another tab of the Query Browser.
[30 May 2005 0:18] Nikos Sarris
The same thing happened to me with version 1.1.2 . I tried every release since but the problem wasn't resolved. After reading this comment page I deleted the xml files and it worked again without a reinstall (version 1.1.9)
[31 May 2005 9:27] Bernhard Dangl
removing the file "mysqlqb_bookmark.xml" was sufficient.
[1 Jun 2005 4:17] Anand Muthu
I've had a bug similar to the above due to some deleting problems. Uninstalling and reinstalling MySQL Query Browser 1.1.9 didn't work. Deleting the XML files also didn't work. However, deleting the XML files and reinstalling MySQL Query Browser seemed to have worked, which doesn't really make sense to me. But anyhow, I'm happy it worked anyway.
[26 Jun 2005 1:10] Bryan McCaffery
I run the query browser on XP Home and I have no Application Data\Mysql directory.  Are the XML files store some where else?
Please Help
[22 Aug 2005 19:34] Marc Hodgins
This problem persists on v1.1.13 on Windows XP.  Deleting the query-browser specific XML files in Application Data\MySQL has solved the problem.  I think it is specifically related to a corrupted history file.
[13 Sep 2005 11:36] Mark Davies
I've had the same problem with "error number 3" with v1.1.9 of the query browser, same fix seems to cure it..deleted the relevant xml files in application data and re-installed all back to normal....be interested to know if anyone has an idea what causes the corruption of the xml files?
[19 Sep 2005 12:42] Mike Lischke
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html
[13 May 2007 4:16] Mark Rodriguez
RE: [8 May 2005 19:24] Philip Howarth

Running Win2k...

Deleting XML files at

C:\Documents and Settings\Administrator\Application Data\MySQL

Worked!!!

Thanks from Denver!!!