MySQL Bugs: #48679: Unhandled exception error when trying to start service

Bug #48679	Unhandled exception error when trying to start service
Submitted:	11 Nov 2009 2:32	Modified:	7 Dec 2016 18:31
Reporter:	Paul Bibby	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	5.1.40	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any

Description:
In the last step of the installation wizard, after the 'Write configuration file' step has run, when trying to start the service I get an 'Unhandled Exception in mysqld.exe' error.
If the error is sent to a debugger it indicates it is failing on the following line in the _callthreadstart procedure (don't know enough about MYSQL to know if this is the actual problem)

( (void(__CLRCALL_OR_CDECL *)(void *))(((_ptiddata)ptd)->_initaddr) )
            ( ((_ptiddata)ptd)->_initarg );

I have uninstalled and re-installed twice and still have the same problem.

The first time I installed, I set the data store to be an external drive on my laptopand all installed OK. I then decided I needed the data store on my laptop, so uninstalled and re-installed with default settings and that's when the problems started. Am going to try and roll back my machine to before the first install and try again. Very frustrating... 

How to repeat:
Just try startting the service manually from the services window in XP and the error message is shown again.
I re-botted the machine and it came up again as the service tried to start automatically.

Thank you for the bug report. Which is the exactly package server version that you are trying to install 5.1.XX?. Thanks in advance.

Apologies - the version is 5.1.40
Since then I have rolled back Windows by using a restore point before the original installation and installed again and got the same error.

Thanks
Paul

One thing that I noticed on the re-install is that it asked for the current root password, even though I have uninstalle, and I just lleft that blank before.
So, I went into the MySQL directory in Program files and deleted everything out of that and also in the AllUsers folder in Documents and settings.
When I re-installed this time, I entered the original password and the service started, but now I get the error the Security settings could not be applied

Error Nr. 1045 Access denied for user 'root'@'localhost' (using password: YES)
Pretty sure the old password I entered was correct.

Getting closer....

OK, have got there.
It seems that when I did the re-install and left the 'current password' field blank, it changed it to blank (?) When I re-ran the configuration wizard, and left the current password as blank, it all seems to have worked. Phew..

So, do we have anything to be called a bug here or not?

I think there is a bug, yes, but I found a workaround.
After re-installing the first time , I did not enter a password (just left it blank) in the 'Current root password' field of the installation wizard, as I wasn't aware that it would still pick up the original data file and wasn't paying attention.
Once I got to the last page of the installation wizard, the wizard then crashed when it tried to start the MySQL Service with the error message as described.

Once I had uninstalled again AND deleted the MySQL folder in Program Files, the next installation was fine and the service started successfully.

Did you have some 5.1.x version ever installed on this machine before your first attempt to install 5.1.40?

No, this is the first time I have installed MySQL of any version

There are one or more reports already about 'failure to apply security settings'.  But if 'currrent password' is not entered correctly that is logical in this case, I think.

an idea: if you install on top of an existing version and change datadir in the wizard, service may be looking the wrong/an invalid place for the system tables and thus fail to start?

Hi Peter,
>>But if 'currrent password' is not entered correctly that is logical in this case, I think.

Yes I agree it is logical that it wouldn't work, but not that it would crash with an unhandled exception error. What I would expect in the wizard was that it checked the current root password that was entered and if it was wrong, pop up a message to say so and not let you continue. It didn't do this, it just accepted a blank password, then crashed at a later stage.
Sorry I don't know enough about MySQL to know where it looks for system tables etc. as this is the first time I have used it, but I would still expect the service to fail a bit more elegantly {:o)

I am getting an error here as well. After the "Write Configuration File" step it seems to hang and never starts the service. When I kill the configuration wizard and try to start it manually, it also hangs. So I looked in the installation directory (C:\Program Files\MySQL\MySQL Server 5.1) and there's no data directory, so of course it won't start. But why isn't there a data directory?

I see the following in Event Viewer. The first two are "Information" events, the rest are "Error" events.

Product: MySQL Server 5.1 -- Installation operation completed successfully.

The description for Event ID ( 100 ) in Source ( MySQL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Plugin 'FEDERATED' is disabled.

The description for Event ID ( 100 ) in Source ( MySQL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Plugin 'InnoDB' init function returned error.

The description for Event ID ( 100 ) in Source ( MySQL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

The description for Event ID ( 100 ) in Source ( MySQL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unknown/unsupported table type: INNODB

The description for Event ID ( 100 ) in Source ( MySQL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Aborting

FYI, I'm on Windows XP Pro, SP3.

Also, note that the workaround described above (deleting the MySQL folder in Program Files) is not an option for me because I have other sub-folders there (i.e. a 4.0 and 5.0 server, and some Enterprise stuff.

OK, I found a successful workaround.  Instead of installing in C:\Program Files\MySQL\MySQL Server 5.1, I installed it in C:\Program Files\MySQL2\MySQL Server 5.1 instead, and now it's working (note the MySQL -> MySQL2 difference), but this is a stupid thing to have to do.

Had you installed as a user who is a member of (local) Administrators group?

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".

For the cause of the error 'The description for Event ID ( 100 ) in Source ( MySQL ) cannot be found.' 
and workaround, See Bug #48042.

Hello, dear all

see the http://bugs.mysql.com/bug.php?id=49637, it works.

Posted by developer:
 
This relates to EOL (no longer supported) versions of MySQL Server. Furthermore, the old plain msi installers have been superseded by the MySQL Installer for Windows. Thus closing.