Reply to thread

Message

<blockquote data-quote="scythelt" data-source="post: 160605" data-attributes="member: 27879">Sure thing. After installation of MySQL and running the Instance Config Wizard the service refused to start with an &quot;service terminated unexpectedly error&quot;.To fix, I deleted the following files from &quot;C:\Program Files\MySQL\MySQL Server 5.0\data&quot;:<ul>
<li data-xf-list-type="ul">ib_logfile0</li>
<li data-xf-list-type="ul">ib_logfile1</li>
<li data-xf-list-type="ul">ib_data1</li>
</ul>I then re-ran the Instance Config Wizard and the service started successfully! It turns out there was some issue with the InnoDB created by default that Windows Server 2003 doesn't like and deleting those files forces MySQL to recreate the InnoDB files. That's my understanding of the problem anyway, tho I'm still not entirely clear on why the issue arose in the first place.Anyway, hope that helps somebody! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="scythelt, post: 160605, member: 27879"] Sure thing. After installation of MySQL and running the Instance Config Wizard the service refused to start with an "service terminated unexpectedly error". To fix, I deleted the following files from "C:\Program Files\MySQL\MySQL Server 5.0\data": [LIST] [*]ib_logfile0 [*]ib_logfile1 [*]ib_data1 [/LIST] I then re-ran the Instance Config Wizard and the service started successfully! It turns out there was some issue with the InnoDB created by default that Windows Server 2003 doesn't like and deleting those files forces MySQL to recreate the InnoDB files. That's my understanding of the problem anyway, tho I'm still not entirely clear on why the issue arose in the first place. Anyway, hope that helps somebody! :) [/QUOTE]

Verification