Bug #14537 Instanse manager crashes with 'access violation' when started on Windows
Submitted: 1 Nov 2005 8:23 Modified: 9 Nov 2005 2:59
Reporter: Omer Barnir (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:Instance Manager Severity:S1 (Critical)
Version:5.0.15 OS:Microsoft Windows (Windows 2003)
Assigned to: Reggie Burnett

[1 Nov 2005 8:23] Omer Barnir
Description:
When starting the instance manager on Windows 2003, the program crashes and a drwatson error log is generated.

A dialog box appears with the following message:
    mysqlmanager.ex.exe has generated errors and will be closed by 
    Windows. You will need to restart the program.

    An error log is being created
Note: "mysqlmanager.ex.exe" is not a typo, '.ex.exe' is the extension that is
         displayed

The DOS windows itself displays messages as if the program started correctly:

C:\MySQL\Server_5015\bin>mysqlmanager --standalone --default-mysqld-path =c:\MySQL\Server_5015\\bin\mysqld-nt.exe 
051031 23:45:56 loaded user omer
051031 23:45:56 accepting connections on ip socket

C:\MySQL\Server_5015\bin>

But the program is not loaded.

Attempting to load 'mysqlmanager as a service (with the --install) is successful, the service is added, but fails to start as well.

Note that is the case of the service there might be another problem since the service is loaded without any command line parameters so I'm not sure it is even created correctly. But can't verify because of the above problem.

Attached is the drwatson log file

How to repeat:
1) Install the msi package of 5.0.15. 
    In my case I installed to  (verify that the MySQL server can starts
    properly, shut down the server)
2) Open a DOS window and cd to the bin directory where MySQL was installed
3) using mysqlmanager --pass generate a password file (use the default name
    set for the file - mysqlmanager.passwd)
4) Start the mysqlmanager program as follows:
mysqlmanager --standalone --default-mysqld-path=  
                                                   c:\MySQL\Server_5015\bin\mysqld-nt.exe 

Suggested fix:
Have mysqlmanager start correctly
[1 Nov 2005 8:25] Omer Barnir
drwatson log file of instance manager crash

Attachment: IM_drwatson_log.txt (text/plain), 13.83 KiB.

[1 Nov 2005 8:59] Omer Barnir
Installation and running of the above was done as the Administrator user
[3 Nov 2005 19:56] Reggie Burnett
fixed in 5.0.16
[9 Nov 2005 2:59] Paul Dubois
Noted in 5.0.16 changelog.