Bug #4987 MySQL Admin crashes - ntdll.dll error on version 1.0.9
Submitted: 11 Aug 2004 2:18 Modified: 12 Sep 2004 6:37
Reporter: David Hartless Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.0.9 OS:Windows (XP PRO)
Assigned to: Assigned Account CPU Architecture:Any

[11 Aug 2004 2:18] David Hartless
Description:
After changing some options in mySQL Admin, I started recieving error message when clicking on the 'service' icon. The message reads - Access violation at address:77FA4032 in module 'ntdll.dll'. Write address of 0040513E. Alos, mySQL will no longer start automatically when XP loads.

How to repeat:
Not sure.
[12 Aug 2004 6:37] Matthew Lord
Dear Sir,

Thank you for your bug report.  I will need more information on what you did in order to try and 
repeat this problem.

If you can provide more detailed information I can try and repeat it.

Best Regards
[15 Aug 2004 11:44] Joël Cannau
Hello,

I have the same problem: when running MySQL Admin v1.0.9 on XP Pro.

When accessing the Startup Variable Menu (Access violation address 77FA4032 in module ntdll.dll) Write of address 0040513E. 

Logged in as root (no password) on localhost.

It seems there is a ' bad loop' on the error log checking (not sure). My 'my.cnf' file is empty, and I launch Mysql 5.0.0-alpha-max as a windows service. When applying new options (service control, Configure service) nothings seems to happen (by example when applying Support for InnoDB) ..and the 'Apply Changes' button is inactive.

Hope it can helps solving...

Joël
[15 Aug 2004 20:34] Joël Cannau
My problem was that I installed Mysql on another drive than c: (drive e:...)

Once mysql re-installed on drive c: , I have no more problem with Mysqladmin...

But I cannot find why installing on e: or z: may cause a problem.
[15 Aug 2004 21:27] Joël Cannau
Problem is back :(((....please forget what I said in the previous message...

I only created a new catalog with InnoDB support, added a new user and...after a while it happened again....
[20 Aug 2004 17:33] Damien FLAMENT
I get the same problem on Windows 2003 and some windows 2000 servers.
Acces violation at 77F4467E in module ntdll.dll. Write of address 00404EAA.

The problem occur when launching the tray monitor and manage MySQL servers.
[20 Aug 2004 19:44] Damien FLAMENT
I have corrected the problem by removing all MySQL services currently installed on the system. Then reinstalling all of them with the MySQL Administrator GUI. After that it said "All OK Captain ;)".

The MySQL Administrator seem to not correctly reconnized previously installed services.

Hope that's help.
[10 Sep 2004 12:28] Scott Furry
Had similar issue...
Used the tray monitor to stop the service. Wasn't sure the service had stopped so I used the Tray Monitor to stop the service again. Any attempt to start or access the MySQL service through MySQL Admin/Tray monitor resulted in the "Access Violation" error in ntdll.dll. Especially at WinXP start up

Machine particulars - PII WinXP SP1 MySQL 5.0 beta MySQL Admin 1.0.11

IS IT POSSIBLE....
that the service could get corrupted or time out?
Even un-installing the MySQL Admin/Tray Monitor didn't resolve the problem. After un-install/re-install the problem was still present. The only way I could fix the problem was to un-install/re-install the MySQL service. WinMySQLAdmin (located in the MySQL/bin/ folder) didn't have this type of problem.
[14 Feb 2005 22:54] Bugs System
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".
[15 Oct 2018 10:19] khushbu kashyap
The user can download ntdll.dll file absolutely error free from click on  https://unfitpc.com/ntdll-dll and install it after downloading.
[14 Mar 2022 15:04] Javier Martínez Outeiro
Please notice previous comment has a phising url claiming you can download main Windows dll for kernel ntdll.dll.
[12 Jan 2023 6:06] Siddhant yadav
@avier Martínez Outeiro, Replying to a 2018 post in 2023, I guess it won't make any affect now.
My blog: https://hedgehogseat.com/