Page 1 of 1
Windows xp event viewer error messages
Posted: Sun Dec 18, 2011 6:44 am
by fyc2001
my open dental software crashes a few times a day, I thought it was no big deal. But today I took a look at the event viewer in xp.
I see about 10 errors a day on the server computer. Before I upgraded to sql 5.5 from 5.0
the message was "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe: Sort aborted" or
"C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe: Table 'signalod' is marked as crashed and should be repaired"
after the 5.5 upgrade the message was "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe: Sort aborted: Table 'signalod' is marked as crashed and should be repaired"
what was wrong???
Re: Windows xp event viewer error messages
Posted: Sun Dec 18, 2011 8:57 am
by jordansparks
Sounds like you need to repair that table. You can do so by running our database maintenance tool.
http://www.opendental.com/manual/databa ... nance.html
Re: Windows xp event viewer error messages
Posted: Thu Jan 05, 2012 8:53 am
by fyc2001
Hi Jordan: I followed the steps to database maintenance. Now I am getting these different errors about once a day. I wasn't in the office today, but the server had blue screen (first time since the datbase maintainence) and had to be restarted. Thank god it restarted without restoring the OS drive which I had to do a few times in December.
All mysql errors:
Native table 'performance_schema'.'events_waits_history' has the wrong structure
Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
Native table 'performance_schema'.'mutex_instances' has the wrong structure
Please help.
Re: Windows xp event viewer error messages
Posted: Thu Jan 05, 2012 1:46 pm
by jordansparks
I've never seen errors like that before. A blue screen on the server and multiple restoring of OS drive would be a big warning flag to me to ditch that machine and move on. Or you could approach it piecemeal by replacing the hard drive and seeing if that helped. But I would just switch completely if it were me. That machine could become a workstation.
Re: Windows xp event viewer error messages
Posted: Thu Jan 05, 2012 2:20 pm
by fyc2001
Actually I switched out everything except the original software. New RAM, CPU, motherboard, power supply, hard drive. I moved all the data from C to D, so when I restore C drive OS, the data is current. I guess the next step is a fresh installation of XP professional? I don't mind that, except I have to reinstall xdr, open dental, kodak imaging. any other ideas?
Re: Windows xp event viewer error messages
Posted: Thu Jan 05, 2012 6:45 pm
by jordansparks
You've been busy. I don't have any brilliant ideas for you.
Re: Windows xp event viewer error messages
Posted: Fri Jan 06, 2012 12:05 pm
by Justin Shafer
http://dev.mysql.com/doc/refman/5.5/en/ ... ation.html
Interesting....
If you install MySQL over a previous installation that was configured without the Performance Schema (or with an older version of the Performance Schema that may not have all the current tables), run mysql_upgrade after starting the server to ensure that the performance_schema database exists with all current tables. Then restart the server. One indication that you need to do this is the presence of messages such as the following in the error log:
[ERROR] Native table 'performance_schema'.'events_waits_history'
has the wrong structure
[ERROR] Native table 'performance_schema'.'events_waits_history_long'
has the wrong structure
...
Re: Windows xp event viewer error messages
Posted: Fri Jan 06, 2012 3:20 pm
by jsalmon
Here's another link that suggests running mysql_upgrade to correct the errors.
http://bugs.mysql.com/bug.php?id=57008
Re: Windows xp event viewer error messages
Posted: Tue Jan 10, 2012 6:41 am
by fyc2001
Thanks for the last two replies.
After my last post, I upgraded the server mysql from 5.5.15 (from opendental site download) to 5.5.19 from mysql.com. That seems to solve the problem, I haven't had an error in 4 days.