![microsoft webmatrix mysql 5.1 freeze microsoft webmatrix mysql 5.1 freeze](https://docs.microsoft.com/en-us/iis/web-hosting/joining-the-web-hosting-gallery/setup-mysql-with-webmatrix-support/_static/image6.png)
- #MICROSOFT WEBMATRIX MYSQL 5.1 FREEZE INSTALL#
- #MICROSOFT WEBMATRIX MYSQL 5.1 FREEZE 64 BIT#
- #MICROSOFT WEBMATRIX MYSQL 5.1 FREEZE WINDOWS 7#
Mysqld -defaults-file="path_for_my_ini\my.ini" -standalone -console Here a dump starting from the resulting errors following this command: Tried everything possible I could imagine, including all of the above.
#MICROSOFT WEBMATRIX MYSQL 5.1 FREEZE WINDOWS 7#
Karsten Habay Having the same problem on a Windows 7 Ultimate with mySQL-5.1.42-win32.msi When (re)starting fails, rollback to the previous working situation can be a huge feat. An error (as apparently appears here) should be presented instead of causing 100% CPU and freeze-up.Īpparently some access violation occurs (0xc0000005), this shouldn't cost 100% CPU.Īlternatively, but rather a feature request: changing configuration should backup the previous configuration.
![microsoft webmatrix mysql 5.1 freeze microsoft webmatrix mysql 5.1 freeze](https://i.stack.imgur.com/1vMeI.jpg)
If it is not created within X seconds or so, give an information message to the user. Use a separate thread that creates the service to prevent freeze or lockup. Result: when the wizard tries to start the service, it stops responding and brings the CPU to 100%. Start MySQL Server Instance Config Wizard and choose "reconfigure instance"ģ.
#MICROSOFT WEBMATRIX MYSQL 5.1 FREEZE INSTALL#
Install MySQL 5.1 using MSI install or MS Web Platform InstallerĢ.
![microsoft webmatrix mysql 5.1 freeze microsoft webmatrix mysql 5.1 freeze](https://www.helicontech.com/articles/wp-content/uploads/2013/07/image12.png)
#MICROSOFT WEBMATRIX MYSQL 5.1 FREEZE 64 BIT#
Logged in as Administrator, follow the following steps on a freshly installed Windows 2008 Web Server R2 64 bit (possibly any other Windows version, considering scattered reports on the internet):ġ. Strange fact: doing this twice (hit back and "Execute", no changes) then it freezes again. The error in the event log is equal to the errors above. NOTE: there's one exception to the freezing/100% CPU: if you select Transactional + deselect "Enable TCP/IP" + deselect "Modify security settings". It is remarkable that when you select InnoDB (i.e., Transactional) and change the path, the process *does* create a new ibdata1 file in the new directory. The event viewer logged the following errors when using the wizard or when starting the service:įaulting application name: mysqld.exe, version: 0.0.0.0, time stamp: 0x4af32fccįaulting module name: mysqld.exe, version: 0.0.0.0, time stamp: 0x4af32fccįaulting application start time: 0x01ca8efdc9d8440cįaulting application path: C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exeįaulting module path: C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe Trying to start the service manually does *not* solve the problem, it fails. Killing MySQLInstanceConfig.exe is the only way out (and subsequently eases the stress on services.exe, which goes to 0% CPU). It shows "Prepare configuration" and "Write configuration file" as successful. After a default installation (using Microsoft Web Platform Installer) trying to reconfigure using the MySQL Server Instance Config Wizard fails on all accounts: it freezes ("not responding" in the caption bar) and eats 100% of CPU (separated over services.exe and MySQLnstanceConfig.exe).