Upgrading failure - Error Nr. 2003

#21

On 20-12-2010 1:59, Jerry Stuckle wrote:

Quote:

Since you can connect via the CLI, you can set the password with the
GRANT command. But I don't see why the configuration wizard doesn't
work.

I did that. In order to set the password I did this:

grant all on *.* to 'root'@'localhost' identified by 'my_pwd';

No problem here. I got the message

Query OK, 0 rows affected (0.05 sec)

Try starting it from the command line with the -l parameter and a log
file name, i.e.

MySQLInstanceConfig -lc:\msqlic.log

And see if that shows anything.

And ensure you are actually using the my.ini file you think you are.

I did this an I tried to change the password. Again, I got the same
error as in my first post. The contents of the file msqlic.log are:

----------------------------------------
Welcome to the MySQL Server Instance Configuration Wizard 1.0.17.0
Date: 2010-12-19 23:10:50

Installing service ...

Product Name: MySQL Server 5.5
Version: 5.5.8
Installation Path: C:\Program Files\MySQL\MySQL Server 5.5\

Creating configuration file C:\Program Files\MySQL\MySQL Server
5.5\my.ini using template C:\Program Files\MySQL\MySQL Server 5.5\my-
template.ini.
Options:
DEVELOPMENT
MIXED
DSS
STRICTMODE
CONFIG_ALTERED

Variables:
port: 3306
default-character-set: latin1
basedir: "C:/Program Files/MySQL/MySQL Server 5.5/"
datadir: "C:/Documents and Settings/All Users/Application Data/MySQL/
MySQL Server 5.5/Data/"
old_innodb_log_file_size: 10M

The security settings could not be applied to the database because the
connection has failed with the following error.

Error Nr. 2003
Can't connect to MySQL server on 'localhost' (10061)
----------------------------------------

BTW, this confirms that the file my.ini file is where I thought that
it should be.

OK, so is the data directory in your new my.ini file correct?

Yes, it is.

Quote:

And are you sure you entered the correct userid/password in the configuration
script?

Yes, I am.

There is something wrong with the machine with which I am having this
problem. I did exactly the same thing on two other machines (both of
them using Windows XP) and all went fine there. I have already spent
hours on this problem (it's a slow machine :-( ) and I am not going to
try again.

Having said this, I must add that I am very grateful to you for all your
effort in order to help me. Thanks a lot.

Best regards,

Jose Carlos Santos

#22

On 12/20/2010 5:27 AM, José Carlos Santos wrote:

Quote:

On 20-12-2010 1:59, Jerry Stuckle wrote:

Since you can connect via the CLI, you can set the password with the
GRANT command. But I don't see why the configuration wizard doesn't
work.

I did that. In order to set the password I did this:

grant all on *.* to 'root'@'localhost' identified by 'my_pwd';

No problem here. I got the message

Query OK, 0 rows affected (0.05 sec)

Try starting it from the command line with the -l parameter and a log
file name, i.e.

MySQLInstanceConfig -lc:\msqlic.log

And see if that shows anything.

And ensure you are actually using the my.ini file you think you are.

I did this an I tried to change the password. Again, I got the same
error as in my first post. The contents of the file msqlic.log are:

----------------------------------------
Welcome to the MySQL Server Instance Configuration Wizard 1.0.17.0
Date: 2010-12-19 23:10:50

Installing service ...

Product Name: MySQL Server 5.5
Version: 5.5.8
Installation Path: C:\Program Files\MySQL\MySQL Server 5.5\

Creating configuration file C:\Program Files\MySQL\MySQL Server
5.5\my.ini using template C:\Program Files\MySQL\MySQL Server 5.5\my-
template.ini.
Options:
DEVELOPMENT
MIXED
DSS
STRICTMODE
CONFIG_ALTERED

Variables:
port: 3306
default-character-set: latin1
basedir: "C:/Program Files/MySQL/MySQL Server 5.5/"
datadir: "C:/Documents and Settings/All Users/Application Data/MySQL/
MySQL Server 5.5/Data/"
old_innodb_log_file_size: 10M

The security settings could not be applied to the database because the
connection has failed with the following error.

Error Nr. 2003
Can't connect to MySQL server on 'localhost' (10061)
----------------------------------------

BTW, this confirms that the file my.ini file is where I thought that
it should be.

OK, so is the data directory in your new my.ini file correct?

Yes, it is.

And are you sure you entered the correct userid/password in the
configuration
script?

Yes, I am.

There is something wrong with the machine with which I am having this
problem. I did exactly the same thing on two other machines (both of
them using Windows XP) and all went fine there. I have already spent
hours on this problem (it's a slow machine :-( ) and I am not going to
try again.

Having said this, I must add that I am very grateful to you for all your
effort in order to help me. Thanks a lot.

Best regards,

Jose Carlos Santos

I hope you don't think I'm asking stupid questions, but at this point
I'm grasping at straws. I don't see anything you're doing wrong, and it
should be working fine - signing on from the config wizard isn't that
complicated.

Sorry I wasn't able to help you.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex (AT) attglobal (DOT) net
==================

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Upgrading failure - Error Nr. 2003

comp.databases.mysql comp.databases.mysql

Re: Upgrading failure - Error Nr. 2003 - 12-20-2010 , 04:27 AM

Re: Upgrading failure - Error Nr. 2003 - 12-20-2010 , 07:44 AM