MySQL Bugs: #71042: Event ID 100 - The description for Event ID 100 from source MySQL cannot be...

Bug #71042	Event ID 100 - The description for Event ID 100 from source MySQL cannot be...
Submitted:	30 Nov 2013 8:26	Modified:	27 Jan 2018 19:41
Reporter:	Marvin Miller	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.6.13	OS:	Windows (Server 2008 R2)
Assigned to:		CPU Architecture:	Any
Tags:	Event ID 100

Description:
I don't know why but I always seem to have to chase down event log issues with MySQL, most of which have already been reported as bugs...anyway;

I'm seeing tons of these in the Windows Application Log;

Event ID 100:

The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000

******************************************************************************

and this one comes up all the time;

The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: Forcing close of thread 5  user: 'root'

How to repeat:
Install MySql

Suggested fix:
Ask the people who develop MySQL to pay a LOT more attention to even log errors.

Thre is an older bug report here:
http://bugs.mysql.com/bug.php?id=48042
.. it was marked as closed.  So if this has resurrected in MySQL 5.6 it looks like a regression.

(and just google "event id 100 mysql" (without quotes) and you will find lots of discussions about this).

Anyway I have MySQL 5.6.14 installed on Windows 7/64 and am not able to find such log messages. Maybe I am looking the wrong place?

Peter
(not a MySQL/Oracle person)

Read in http://bugs.mysql.com/bug.php?id=48042

"Noted in 5.1.47, 5.5.5, 6.0.14 changelogs.
On Windows, the server failed to find a description for Event ID 100."

At that time there probably was no 5.6x available.

Hi Peter;

Thanks for the info. I find that error (or similar event id 100 errors) on almost every install of MySQL. It seems every time I upgrade (or do a new install) they crop up. It's as if the developers case it with one release and then screw the pooch on the next release and re-introduce the error.

This seems to gibe with your most recent post.

It can be seem in Windows Administrative Tools => Event Viewer => Application Log

I don't know what causes it, all I know is that several times I've upgraded (new installs) MySQL and it appears often. Certain older releases don't seem to have it.

I wish the people who develop MySQL would eliminate it or change their programming practices to kill them off entirely! :)

@Marvin ..

.. you don't have multiple MySQL servers installed on the system, where one is older than from when the fix I quoted from the other bug report was included?

Hi Peter - no, they were all clean installs on new virtual machines. I only mentioned the bug because, over the years, it seems various releases of MySQL seem to have have the problem.

I think it's very much like you mentioned earlier, they address the issue in some releases and then forget it in others. At least, it seems that way to me. 

Either way, I hate seeing them in the application log and wish the MySQL developers would get it together once and for all on this issue! :)

Related, I filed a feature request internally:
Bug 16097505 - WINDOWS: NEED AN OPTION TO PREVENT LOGGING TO THE NT EVENT LOG 
It was a followup from http://bugs.mysql.com/bug.php?id=24817

Hi.. need some expert advice.
I installed fresh MySQL 5.6.14 Enterprise edition in my VM just to test if the error EVENT ID 100 is been resolve. But when i looked up my EVENT VIEWER (Administrative Events) i saw this error logs.

_______________
The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

the message resource is present but the message is not found in the string/message table
________________________________

Here's my error log.
2013-12-02 17:34:53 1052 [Note] Plugin 'FEDERATED' is disabled.
2013-12-02 17:34:53 1052 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
2013-12-02 17:34:53 460 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-12-02 17:34:53 1052 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-02 17:34:53 1052 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-02 17:34:53 1052 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-02 17:34:53 1052 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-02 17:34:53 1052 [Note] InnoDB: Initializing buffer pool, size = 8.0M
2013-12-02 17:34:53 1052 [Note] InnoDB: Completed initialization of buffer pool
2013-12-02 17:34:53 1052 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-02 17:34:53 1052 [Note] InnoDB: 128 rollback segment(s) are active.
2013-12-02 17:34:53 1052 [Note] InnoDB: Waiting for purge to start
2013-12-02 17:34:53 1052 [Note] InnoDB: 5.6.14 started; log sequence number 1626037
2013-12-02 17:34:53 1052 [Note] RSA private key file not found: C:\ProgramData\MySQL\MySQL Server 5.6\data\\private_key.pem. Some authentication plugins will not work.
2013-12-02 17:34:53 1052 [Note] RSA public key file not found: C:\ProgramData\MySQL\MySQL Server 5.6\data\\public_key.pem. Some authentication plugins will not work.
2013-12-02 17:34:53 1052 [Note] Server hostname (bind-address): '*'; port: 3306
2013-12-02 17:34:53 1052 [Note] IPv6 is available.
2013-12-02 17:34:53 1052 [Note]   - '::' resolves to '::';
2013-12-02 17:34:53 1052 [Note] Server socket created on IP: '::'.
2013-12-02 17:34:53 1052 [Note] Event Scheduler: Loaded 0 events
2013-12-02 17:34:53 1052 [Note] C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
Version: '5.6.14-enterprise-commercial-advanced'  socket: ''  port: 3306  MySQL Enterprise Server - Advanced Edition (Commercial)

Btw 5.6 sources contain fix for bug #48042

Almost a year after, same for me on MySQL Community 5.7.4.0 m14.

"The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."

I can attest that this is also happening with MySQL 5.7.3

Found this thread looking for a potential solution/explanation to the problem.

According to http://bugs.mysql.com/bug.php?id=48042

"The fix is to add message.rc to mysqld.exe source files list."

Is it an issue maintaining that this is included before compiling for future versions?

Please check version 5.6.21. Thanks.

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

Still occurs on 5.6.25

Also happens in 5.6.26, unfortunately...

I was not able to repeat on Windows 10 Pro 64-bit with latest Windows installer, please try with latest releases. Thanks in advance.

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