[AccessD] MySQL is broke now

Well, I did an uninstall and reinstall and now I am able to connect to the MYSql server from outside 
of the VM, using the Hamachi IP, root and the password.  Unfortunately from inside of the vm I still 
cannot get WampServer to talk to the server.  It still gives me an error message about the username 
or password being wrong - (using password: No).  I set the password in the phpmyadmin init file but 
no joy.

What I have discovered is that when running MySQL as a service, wampserver will not start correctly. 
  If I stop MySQL service, wampserver now starts (though it still cannot connect to MySQL) but it is 
now green instead of orange.  however with Wampserver started MySQL service will not start. 
quitting wampserver allows the MySQL Service to start again.

The bottom line is that I can now get at MySQL from outside of the VM with the service startwd, 
which I could not do with the service not started.  I need access from outside of the vm, so i guess 
(for now) I just give up on wampserver.

Sigh.

John W. Colby
www.ColbyConsulting.com

On 9/22/2011 6:04 PM, Jim Lawrence wrote:
> Post a message on OT_SQL...Hans will help you. ;-)
>
> Jim
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Thursday, September 22, 2011 12:55 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] MySQL is broke now
>
> The service never ran.  I did some stuff including modifying my.ini to add
> federated.
>
> Doing that stopped the error log being generated but the service still would
> not start.  I found
> something that discusses deleting the service (which worked) but the thing
> that adds the service
> does not work.
>
> My windows paste buffer is not working between my VM and my laptop so the
> following is just typed in.
>
> The line is:
>
> mysql --install MySQL --defaults-file="C:\Program Files\MySQL\MySQL Server
> 5.5\My.Ini"
>
> This does in fact add a line to the services but the problem is that the
> service thinks that
> MySQLd.exe is in thesame location as that my.ini whereas it is in fact down
> in a bin under that dir.
>
> I.e. the "path to executable" is looking for the MySQLD.exe in the wrong
> place and thus cannot be
> started.
>
> This is getting annoying.  I have been trying various things for hours and
> just cannot get MySQL to
> run as a service and now the entry in the service table (or registry?) is
> corrupted.
>
> Sigh.
>