Anyone having problems running HeidiSQL (5.1) on Win7 x64???

[expired user #4973]'s profile image [expired user #4973] posted 14 years ago in General Permalink
Running even the latest nightly build version is causing my PC to crash when I browse to any table in MySQL database. Basically system freezes, hard drive light comes on and my memory consumption jumps to 90% and then back to 30%. This occurs with no other applications running and ~30% memory consumed by background processes. My machine (T500) has 3 gb. of RAM and is running Windows 7 x64.

J
ansgar's profile image ansgar posted 14 years ago Permalink
I have nearly the same configuration here: Win7 64bit, 4GB RAM, Intel E8400 3GHz. I am running official releases, latest builds, and pre-builds without any problem. So it's unlikely this is a OS related problem. More likely: a wrong or old libmysq.dll ?
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
Tried cleaning out old version of HeidiSQL and reinstalled 5.0.0.3272. Started up without problems but after a period of time, application became unresponsive (after clicking on multiple tables within my database).

Seems the problem is still there. The libmysql.dll does not have a version number when I right-click its properties. Am I going to have to compile/debug this myself?

Thanks.
ansgar's profile image ansgar posted 14 years ago Permalink
You could update to the latest build and hover your mouse over the status bar panel saying "MySQL x.x" - that will show a hint which includes the libmysql.dll version number.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
Ok - I updated to the latest build 5.1.0.3378. The nightly build does not include an updated libmysql.dll. The libmysql.dll is for HeidiSQL 5.0.0.3272 currently. Anything else? I am clicking on multiple tables and switching views in HeidiSQL....and now my computer just crashed. This is really strange - HD light stays illuminated and I can hear it thrashing....then finally my system comes back (icons get distorted, windows are black). After it comes back...system is back to normal but memory(I believe) issue always comes back up in HeidiSQL.

I really think this is a memory leak problem in HeidiSQL - no other application I have freezes up my machine like this. Video driver conflict???

Thanks.

J
ansgar's profile image ansgar posted 14 years ago Permalink
> The nightly build does not include an updated libmysql.dll

Well I didn't say so, I just meant you could update your build as the above mentioned status bar hint was implemented recently.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
Ok - well I was confused by your comment "that will show a hint which includes the libmysql.dll version number" implying I thought that libmysql.dll was included. In any case when I hover over the status bar panel all it says is "5.1.0.3378" so I assume 3378 is the version of libmysql.dll?

Will running in debug mode help (would require downloading source and running the app. in Delphi correct)? Thank you.
ansgar's profile image ansgar posted 14 years ago Permalink
> so I assume 3378 is the version of libmysql.dll?

No, that's the HeidiSQL Subversion revision. It's the "Client version (libmysql.dll)" which is relevant here.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
So...what now? Do you want me to send you my libmysql.DLL?
ansgar's profile image ansgar posted 14 years ago Permalink
I want you to look after the version number which is displayed right besides "Client version (libmysql.dll)" in that hint on your status bar, and then report this version here, so I can tell you if you need a newer dll.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
I really want to help myself here but...wait ok...think I found what you meant by status bar hint (I was holding my mouse over the HeidiSQL icon in my taskbar)! Anyways, the version that comes up when I hold my mouse over the in-application status icon lower center of main application window is:
"Client version (libmysql):5.1.44"

Thanks.

J
ansgar's profile image ansgar posted 14 years ago Permalink
Ok, that version is fine, looks like the original one from the installer. So that's not the problem here.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
Any other suggestions?
ansgar's profile image ansgar posted 14 years ago Permalink
I have no clue, sorry. Never heard that before.
[expired user #255]'s profile image [expired user #255] posted 14 years ago Permalink
Hi,

I'm heaving the same problem after upgrading to heidisql5.1 after working with the 5.0beta for a long time. The horrible thing is that after uninstalling the 5.1 also the 5.0 makes the same problems now!!!! Win 7 x64 freezes and gets black windows!

What the hell is going on???? Please help!!!!!
[expired user #255]'s profile image [expired user #255] posted 14 years ago Permalink
Ah sorry, what I should mention. The application breaks down when I try to open the table tab and view the columns. I can view the tables contents without any problems...

MySQL-Server is 5.1.42-community. Windows und Mysql restartet hundred of times.
ansgar's profile image ansgar posted 14 years ago Permalink
Probably you both have some special configuration, e.g. large fonts / 120 DPI or so?
[expired user #255]'s profile image [expired user #255] posted 14 years ago Permalink
Mmmmhh, I've got 1680x1050 and changed nothing else. What I don't understand is why the problem is now affecting the old version, too. After upgrading to 5.1 and downgrading to 5.0 again. Does the 5.1-installer changes any files which are not deleted with the uninstaller? or changes in the registry?

I will send you an screenshot of the freezing state. Maybe this will help...
ansgar's profile image ansgar posted 14 years ago Permalink
No files are touched since 4.0 release, apart from the libmysql.dll which is likely not a problem here. More likely some registry value which is out of integer range or so.
ansgar's profile image ansgar posted 14 years ago Permalink
Please try r3389 - I blindly fixed some suspicious code there.
[expired user #255]'s profile image [expired user #255] posted 14 years ago Permalink
This leads to the following error when trying to open any database:

date/time : 2010-06-11, 20:49:44, 222ms
computer name :
user name :
registered owner : Microsoft / Microsoft
operating system : Windows 7 x64 build 7600
system language : German
system up time : 5 hours 1 minute
program up time : 19 seconds
processors : 2x Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz
physical memory : 2312/3992 MB (free/total)
free disk space : (C:) 186,13 GB
display mode : 1680x1050, 32 bit
process id : $1ce0
allocated memory : 43,73 MB
executable : heidisql.r3389.exe
exec. date/time : 2010-06-11 20:49
version : 5.1.0.3389
compiled with : Delphi 2010
madExcept version : 3.0k
callstack crc : $00000000, $f0ce2105, $f0ce2105
exception number : 2
exception class : EAccessViolation
exception message : Access violation at address 00000000. Read of address 00000000.

main thread ($119c):
00000000 ???
0074b8ee heidisql.r3389.exe mysql_connection 433 +3 TMySQLConnection.SetActive
006c93f3 heidisql.r3389.exe Main 2665 +8 TMainForm.InitConnection
006f8a95 heidisql.r3389.exe connections 204 +3 Tconnform.btnOpenClick
00544fab heidisql.r3389.exe Controls TControl.Click
004d1fbe heidisql.r3389.exe StdCtrls TCustomButton.Click
004d2a24 heidisql.r3389.exe StdCtrls TCustomButton.CNCommand
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
004d1c84 heidisql.r3389.exe StdCtrls TButtonControl.WndProc
00544664 heidisql.r3389.exe Controls TControl.Perform
0054945b heidisql.r3389.exe Controls DoControlMsg
00549ec3 heidisql.r3389.exe Controls TWinControl.WMCommand
0056f120 heidisql.r3389.exe Forms TCustomForm.WMCommand
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
0056c028 heidisql.r3389.exe Forms TCustomForm.WndProc
005489a8 heidisql.r3389.exe Controls TWinControl.MainWndProc
0049a1b4 heidisql.r3389.exe Classes StdWndProc
77000ad1 USER32.dll CallWindowProcW
00739fa4 heidisql.r3389.exe helpers 1799 +1 CallOld
0073a0ec heidisql.r3389.exe helpers 1846 +44 SizeGripWndProc
76ffcd7c USER32.dll SendMessageW
77000ad1 USER32.dll CallWindowProcW
00549408 heidisql.r3389.exe Controls TWinControl.DefaultHandler
005453fc heidisql.r3389.exe Controls TControl.WMLButtonUp
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
004d1c84 heidisql.r3389.exe StdCtrls TButtonControl.WndProc
005489a8 heidisql.r3389.exe Controls TWinControl.MainWndProc
0049a1b4 heidisql.r3389.exe Classes StdWndProc
76ff7df5 USER32.dll DispatchMessageW
00575129 heidisql.r3389.exe Forms TApplication.ProcessMessage
0057516e heidisql.r3389.exe Forms TApplication.HandleMessage
00570999 heidisql.r3389.exe Forms TCustomForm.ShowModal
006c4c40 heidisql.r3389.exe Main 1557 +94 TMainForm.Startup
00792739 heidisql.r3389.exe heidisql 66 +17 initialization
76b93675 kernel32.dll BaseThreadInitThunk

[expired user #255]'s profile image [expired user #255] posted 14 years ago Permalink
Ups sorry, forgot to copy the file in the programms dir...
This fix helps a little bit! I can now see the top part of the table options, but still not the columns. and only for one table. after clicking the second one the problems return.

I guess you are at the right point... :-)
ansgar's profile image ansgar posted 14 years ago Permalink
I have no more ideas currently.
ansgar's profile image ansgar posted 14 years ago Permalink
jacdc, henkel_1111 solved this (he wrote a pm) by resetting the HeidiSQL registry key:
- quit all Heidi sessions
- start regedit.exe
- rename HCKU\Software\HeidiSQL\ to ...\HeidiSQL___\
- start Heidi

That way all registry keys are recreated as needed. Seems to have fixed one or more particular values which contained huge numbers or probably long strings.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
Just a follow-up to this - I am still experiencing daily crashes of HeidiSQL when I click on the SQL Query window. Doing so creates a memory dump due likely to a column width/size value that allocates more memory than is available. I am running a nightly build - 3272 now and this error still occurs. Thanks!

Resetting the registry seems to work but only temporarily.
ansgar's profile image ansgar posted 14 years ago Permalink
r3272 is 200 revisions behind the latest build - any plans for updating? Not sure but there may have been some change which heals this problem magically.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
I would hope too in 200+ revisions that this issue would have been resolved but my HeidiSQL just crashed again when expanding it to full screen after connecting to my database. This happened with rev. 3489. I just downloaded 3492 which appears to have some column width calculation fixes...keeping my fingers crossed!smileThanks.

[expired user #5151]'s profile image [expired user #5151] posted 14 years ago Permalink
I have the same Problem on a Win7 x64 System and on a win2k system, too.

The registry-hint just solved the problem. So I started with a default configuration and changed it step by step back to the old "crash"-settings. After changing "Preferences->Data->Number of rows displayed in data tab (Step, Maximum)" to 0/0, the program chrashs when I open a data-tab, so I think, there´s the issue.

Btw: The tab-order of that tab ist horrible.

I permanently install all nightly builds. This issue occured ca. two month ago.

What´s the suggested option if you want always see all rows in the data-tab (no step, no maximum) ?
ansgar's profile image ansgar posted 14 years ago Permalink
Just try setting both settings to huge values?
[expired user #5151]'s profile image [expired user #5151] posted 14 years ago Permalink
Yeah, I already tried that. Works fine - even with big tables.
Even though there is a limit at 100000 in the maximum field (bigger values are set to this maximum)

I preliminarily thought that setting this option to 0/0 is the same as a default clicked "show all" button. But that was obviously wrong.

It doesn´t matter for me, if the "always show everything"-option is not available (the big values are workaround enough), but it´s annoying if the program crashes and you don´t know why. And using Heidi without the data-tab is not really funny :)

OT: There is another thing I like to ask: Why was the query-execution-time-info moved from the query-tab to a hint in the SQL-log ?
ansgar's profile image ansgar posted 14 years ago Permalink
> Why was the query-execution-time-info moved ...?
To save space above the sub tabs of the query results. This was already asked by other users and I would be glad to move it again somewhere I only don't know where.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
Just updated to build 3546 as build 3492 still did not fix this crashing issue. Any specific changes to address this in the latest nightly build?

Thanks.

J
ansgar's profile image ansgar posted 14 years ago Permalink
No related changes recently.

Could you please give me an update on what crash you're talking about? Most helpful would be a fresh call stack.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
This was the crash whereby if I click on the Data tab after opening the MySQL database, the application would freeze and all of my other application windows become unresponsive and not refresh. Also, the hard drive light stays on repeatedly indicating a memory dump. If I resize the HeidiSQL window repeatedly for a period of 30 secs., the application window gradually redraws and after about 1-2 minutes of doing this and letting finish the memory flush, do all of my windows come back.

Basically, this is the same problem as I noted at the beginning of this thread with no real improvement seen in 250+ builds. I don't have a call stack or a debug environment to test this. Is there something else I can provide when/if this problem occurs again (it does not happen everytime I use HeidiSQL)?

Again, I just updated to build 3546 from 3492 and hope the problem is fixed.

J
ansgar's profile image ansgar posted 14 years ago Permalink
Why should that be fixed if you downgrade?

I am unable to reproduce such a crash. Probably the table you are trying to view gives us a hint - assumed that it is one specific table, not all tables, is it? If it's one specific table, please post the CREATE TABLE code here. Thanks.
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
No - not a specific table in my db - happens with all tables and I currently have my number of rows set to the default of 300. Also - my previous comment "just updated to build 3546 from 3492" means I upgraded to a newer build correct?
ansgar's profile image ansgar posted 14 years ago Permalink
Oh sorry, I misread your sentencesmileof course that's an upgrade, not a downgrade.

Can you give me some specification of the machine and/or the relevant server which is mentionable? I have no chance to help you if there is nothing special there: Server version, Client OS (still Win2k?).

You can also try to reset all of your HeidiSQL configuration stuff (probably most promising solution, if you did not already try that):
- close all heidisql instances
- start regedit.exe
- go to HKEY_CURRENT_USER\Software\
- rename or delete the "HeidiSQL" subfolder
- restart HeidiSQL and recreate your session parameters (this is of course inconveniant - sorry, just an idea how to fix)
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
Ok - will try the registry reset (think this helped in the past but the crashes started to come up again after a period of 2-3 weeks). My system configuration is the same:

Thinkpad T500
3 GB RAM
ATI 3650 video card
300 GB hard drive

OS: Windows 7 x64

Thanks.
BTW: The newest build 3546 does not seem to improve this crashing issue.


J
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
BTW - that was Windows 7 Ultimate x64

J
[expired user #4973]'s profile image [expired user #4973] posted 14 years ago Permalink
I found the following when going in to reset my HeidiSQL registry entries:

[HKEY_CURRENT_USER\Software\HeidiSQL\WindowPos_0x_0y_1680w_1050h]
"windowstate"="Maximized"
"windowleft"=dword:00000087
"windowtop"=dword:0000018a
"windowwidth"=dword:00000457
"windowheight"=dword:00000226

I did not see this before with previous builds but would this help to try and reproduce the problem? I am running at the max resolution my screen supports - 1680 x 1050 and I think this might have something to do with the column width calculation problem noted earlier in this post.

I will delete this and the HeidiSQL Server entries and start from scratch to see if the problem goes away or improves.

J
ansgar's profile image ansgar posted 14 years ago Permalink
Yes, please just remove the whole HeidiSQL folder and start again.
[expired user #5450]'s profile image [expired user #5450] posted 13 years ago Permalink
I had similar problems on table edit tab with both v.5.1 and v.6.0 on Win7pro x64.

My solution was to disable Aero and now the problems are gone.

It seems that the table edit tab is not compatible with Aero (or perhaps ATI FirePro specifically).


Description:

In 5.1 the interface within tab "Table: <tablename>" changed each time I returned to it (contents within shifted right and down each time and soon disappeared completely). In 6.0 the problem was even more severe: as soon I open the tab and then click on any subtab in there the whole display went weird, like if I after that right clicked on desktop even that context menu went black (it shows then immediately hides behind black rectangle). And when I close heidisql the
taskbar won't redraw for quite some time. When I open task manager in order to see utilization it draws "SYS" parts of the interface while the middle of the window is black. Same for all other programs.

IMO: something must have gone wrong with WM_PAINT events systemwide, I would guess for either resouce leak or backreference of sorts.

hth.
[expired user #5466]'s profile image [expired user #5466] posted 13 years ago Permalink
henkel_1111 said:
This leads to the following error when trying to open any database:

date/time : 2010-06-11, 20:49:44, 222ms
computer name :
user name :
registered owner : Microsoft / Microsoft
operating system : Windows 7 x64 build 7600
system language : German
system up time : 5 hours 1 minute
program up time : 19 seconds
processors : 2x Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz
physical memory : 2312/3992 MB (free/total)
free disk space : (C 186,13 GB
display mode : 1680x1050, 32 bit
process id : $1ce0
allocated memory : 43,73 MB
executable : heidisql.r3389.exe
exec. date/time : 2010-06-11 20:49
version : 5.1.0.3389
compiled with : Delphi 2010
madExcept version : 3.0k
callstack crc : $00000000, $f0ce2105, $f0ce2105
exception number : 2
exception class : EAccessViolation
exception message : Access violation at address 00000000. Read of address 00000000.

main thread ($119c):
00000000 ???
0074b8ee heidisql.r3389.exe mysql_connection 433 +3 TMySQLConnection.SetActive
006c93f3 heidisql.r3389.exe Main 2665 +8 TMainForm.InitConnection
006f8a95 heidisql.r3389.exe connections 204 +3 Tconnform.btnOpenClick
00544fab heidisql.r3389.exe Controls TControl.Click
004d1fbe heidisql.r3389.exe StdCtrls TCustomButton.Click
004d2a24 heidisql.r3389.exe StdCtrls TCustomButton.CNCommand
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
004d1c84 heidisql.r3389.exe StdCtrls TButtonControl.WndProc
00544664 heidisql.r3389.exe Controls TControl.Perform
0054945b heidisql.r3389.exe Controls DoControlMsg
00549ec3 heidisql.r3389.exe Controls TWinControl.WMCommand
0056f120 heidisql.r3389.exe Forms TCustomForm.WMCommand
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
0056c028 heidisql.r3389.exe Forms TCustomForm.WndProc
005489a8 heidisql.r3389.exe Controls TWinControl.MainWndProc
0049a1b4 heidisql.r3389.exe Classes StdWndProc
77000ad1 USER32.dll CallWindowProcW
00739fa4 heidisql.r3389.exe helpers 1799 +1 CallOld
0073a0ec heidisql.r3389.exe helpers 1846 +44 SizeGripWndProc
76ffcd7c USER32.dll SendMessageW
77000ad1 USER32.dll CallWindowProcW
00549408 heidisql.r3389.exe Controls TWinControl.DefaultHandler
005453fc heidisql.r3389.exe Controls TControl.WMLButtonUp
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
004d1c84 heidisql.r3389.exe StdCtrls TButtonControl.WndProc
005489a8 heidisql.r3389.exe Controls TWinControl.MainWndProc
0049a1b4 heidisql.r3389.exe Classes StdWndProc
76ff7df5 USER32.dll DispatchMessageW
00575129 heidisql.r3389.exe Forms TApplication.ProcessMessage
0057516e heidisql.r3389.exe Forms TApplication.HandleMessage
00570999 heidisql.r3389.exe Forms TCustomForm.ShowModal
006c4c40 heidisql.r3389.exe Main 1557 +94 TMainForm.Startup
00792739 heidisql.r3389.exe heidisql 66 +17 initialization
76b93675 kernel32.dll BaseThreadInitThunk

i have the same problem what do i have to do??
i want ot creat thing but i can't without this sql thing.
[expired user #5466]'s profile image [expired user #5466] posted 13 years ago Permalink
henkel_1111 said:
This leads to the following error when trying to open any database:

date/time : 2010-06-11, 20:49:44, 222ms
computer name :
user name :
registered owner : Microsoft / Microsoft
operating system : Windows 7 x64 build 7600
system language : German
system up time : 5 hours 1 minute
program up time : 19 seconds
processors : 2x Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz
physical memory : 2312/3992 MB (free/total)
free disk space : (C 186,13 GB
display mode : 1680x1050, 32 bit
process id : $1ce0
allocated memory : 43,73 MB
executable : heidisql.r3389.exe
exec. date/time : 2010-06-11 20:49
version : 5.1.0.3389
compiled with : Delphi 2010
madExcept version : 3.0k
callstack crc : $00000000, $f0ce2105, $f0ce2105
exception number : 2
exception class : EAccessViolation
exception message : Access violation at address 00000000. Read of address 00000000.

main thread ($119c):
00000000 ???
0074b8ee heidisql.r3389.exe mysql_connection 433 +3 TMySQLConnection.SetActive
006c93f3 heidisql.r3389.exe Main 2665 +8 TMainForm.InitConnection
006f8a95 heidisql.r3389.exe connections 204 +3 Tconnform.btnOpenClick
00544fab heidisql.r3389.exe Controls TControl.Click
004d1fbe heidisql.r3389.exe StdCtrls TCustomButton.Click
004d2a24 heidisql.r3389.exe StdCtrls TCustomButton.CNCommand
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
004d1c84 heidisql.r3389.exe StdCtrls TButtonControl.WndProc
00544664 heidisql.r3389.exe Controls TControl.Perform
0054945b heidisql.r3389.exe Controls DoControlMsg
00549ec3 heidisql.r3389.exe Controls TWinControl.WMCommand
0056f120 heidisql.r3389.exe Forms TCustomForm.WMCommand
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
0056c028 heidisql.r3389.exe Forms TCustomForm.WndProc
005489a8 heidisql.r3389.exe Controls TWinControl.MainWndProc
0049a1b4 heidisql.r3389.exe Classes StdWndProc
77000ad1 USER32.dll CallWindowProcW
00739fa4 heidisql.r3389.exe helpers 1799 +1 CallOld
0073a0ec heidisql.r3389.exe helpers 1846 +44 SizeGripWndProc
76ffcd7c USER32.dll SendMessageW
77000ad1 USER32.dll CallWindowProcW
00549408 heidisql.r3389.exe Controls TWinControl.DefaultHandler
005453fc heidisql.r3389.exe Controls TControl.WMLButtonUp
00544a40 heidisql.r3389.exe Controls TControl.WndProc
00549308 heidisql.r3389.exe Controls TWinControl.WndProc
004d1c84 heidisql.r3389.exe StdCtrls TButtonControl.WndProc
005489a8 heidisql.r3389.exe Controls TWinControl.MainWndProc
0049a1b4 heidisql.r3389.exe Classes StdWndProc
76ff7df5 USER32.dll DispatchMessageW
00575129 heidisql.r3389.exe Forms TApplication.ProcessMessage
0057516e heidisql.r3389.exe Forms TApplication.HandleMessage
00570999 heidisql.r3389.exe Forms TCustomForm.ShowModal
006c4c40 heidisql.r3389.exe Main 1557 +94 TMainForm.Startup
00792739 heidisql.r3389.exe heidisql 66 +17 initialization
76b93675 kernel32.dll BaseThreadInitThunk

i have the same problem what do i have to do??
i want ot creat thing but i can't without this sql thing.
ansgar's profile image ansgar posted 13 years ago Permalink
You have placed the heidisql.r3389.exe into the wrong directory. Move it to where you have installed HeidiSQL and this is fixed. This exception is caused by an outdated libmysql.dll which is somewhere in your system's PATH and taken instead of the one located in c:\program files\HeidiSQL\.

Please login to leave a reply, or register at first.