Rake aborted! Can't create TCP/IP socket (10106)

Rails
1

If this has been dealt with before then forgive me, then if someone
would be kind enough to point me to the url.

I recently purchased RubyMine and installed it as per instructions
(Windows7).
I have an existing database that I wish to use and searched the internet
an came across a couple of articles dealing with this issue.

I have the follwoing installed ROR 2.2.3, Ruby 1.9.1 and MYSQL. I
adjusted the information in database.yml with the information required.

development:
adapter: mysql
encoding: utf8
reconnect: false
database: amgonline_test
username: root
password: password
host: xxx.xxx.x.x // server
port: 3306

I’'ve checkes that all the paths are correcty setup within RubyMine. I
run rake.migrate and I get the following error.

rake aborted! Can’t create TCP/IP socket (10106)

I have searched via google for information specific to ROR put have
found nothing.

I’m rather new to all this, coming from a clipper/clarion background.
This is my first adventure into this type of development.

Thanking you for your assitance.

2

On Jan 19, 2:55Â pm, Nigels S. [email protected] wrote:

I’'ve checkes that all the paths are correcty setup within RubyMine. I
run rake.migrate and I get the following error.

rake aborted! Can’t create TCP/IP socket (10106)

I have searched via google for information specific to ROR put have
found nothing.

firewall problems ?

Fred

3

Frederick C. wrote:

On Jan 19, 2:55Â pm, Nigels S. [email protected] wrote:

I’'ve checkes that all the paths are correcty setup within RubyMine. I
run rake.migrate and I get the following error.

rake aborted! Can’t create TCP/IP socket (10106)

I have searched via google for information specific to ROR put have
found nothing.

firewall problems ?

Fred

That’s intresting you should say that, yet when I connect to the
database via Navicat it connects successfully. I’ve also pinged via the
CMD prompt, I get a reply. I also at first thought it could be a
firewall problem.

4

Frederick C. wrote:

On Jan 19, 3:32Â pm, Nigels S. [email protected] wrote:

That’s intresting you should say that, yet when I connect to the
database via Navicat it connects successfully. I’ve also pinged via the
CMD prompt, I get a reply. I also at first thought it could be a
firewall problem.

doesn’t windows authorise connections to the outside world on a per
application basis ? I also saw that you’re using rails 2.2.3 with ruby
1.9.1. The first version of rails to be ruby 1.9 ready was 2.3 (and
even then it was a slightly rocky road)

Fred

Hi Fred

Should I change version of ROR and Ruby to a previous version? What are
most developers using currently? I’ve just checked my version of rails
and it’s actually 2.3.5 and Ruby is 1.9.1.

5

On Jan 19, 3:32Â pm, Nigels S. [email protected] wrote:

That’s intresting you should say that, yet when I connect to the
database via Navicat it connects successfully. I’ve also pinged via the
CMD prompt, I get a reply. I also at first thought it could be a
firewall problem.

doesn’t windows authorise connections to the outside world on a per
application basis ? I also saw that you’re using rails 2.2.3 with ruby
1.9.1. The first version of rails to be ruby 1.9 ready was 2.3 (and
even then it was a slightly rocky road)

Fred

6

On Jan 19, 4:15Â pm, Nigels S. [email protected] wrote:

Hi Fred

Should I change version of ROR and Ruby to a previous version? What are
most developers using currently? I’ve just checked my version of rails
and it’s actually 2.3.5 and Ruby is 1.9.1.

2.3.5 & 1.9.1 is probably fine. The majority are probably running ruby
1.8.6 or 1.8.7

Fred