| View previous topic :: View next topic |
| Author |
Message |
GagnierA
-
Joined: 18 May 2004
Posts: 71
Location: Windsor, Ontario, Canada
|
 Posted: Sat Feb 26, 2005 10:34 pm Post subject: MySQL Instance Configuration Problem... |
 |
|
This is a strange one that I've been struggling with for a couple weeks. I tried looking through the MySQL documentation, which yeilded no results...I asked a couple of other people that I know, and that didn't help either....
The problem I'm getting is during the Server Instance Configuration, after the installation (5.0.2). When it comes time to "execute" the settings, it says:
| Code: | | Error 2017: Can't open named pipe host: pipe: mysql (2) |
Maybe if I knew what this means I'd be able to fix it...I don't even know why this happened. All other versions worked perfectly, and so did this one! Which is messed up! It seems like one day it all of a sudden decided that it didn't feel like working anymore, so I uninstalled it and tried the previous versions, but they didn't seem to want to work anymore either. Needless to say, I lost all my databases and all data contained in them....
I had pretty much given up on trying to find the solution and was using other, non-secure, methods (ie. text files and xls files, etc) for my databasing needs....but I hate that, it's such a pain in the neck!
Due to the seemingly random nature of this little problem, it's left me frustrated and ticked off. Any help would be greatly appreciated. I don't know if I've said everything that you'd need to know in order to help me better, but if I missed something you can always ask :)
Thanks in advance to anyone who can help me with this, it's been bugging me for a long time now. OH! My OS is WinXP Pro SP2 "just in case". :) |
|
| Back to top |
     |
 |
aprelium
-
Joined: 22 Mar 2002
Posts: 6800
|
| Posted: Sun Feb 27, 2005 6:01 pm Post subject: Re: MySQL Instance Configuration Problem... |
|
|
We don't have an answer but we can explain some details:
Clients have 2 methods to connect to MySQL server:
* They can use a TCP/IP connection on port 3306. This is usually done when the client and the server are not on the same computers. So they use the network to communicate. If both are on the same computer, they can still use the same method, the client would connect to localhost:3306.
* If the client and the server are on the same computer they can use named pipes to communicate. This is faster than using TCP/IP. Named pipes are a special operating system object that is used as a communication channel between two applications.
_________________
Support Team
Aprelium - http://www.aprelium.com |
|
| Back to top |
|
|
GagnierA
-
Joined: 18 May 2004
Posts: 71
Location: Windsor, Ontario, Canada
|
| Posted: Sun Feb 27, 2005 6:38 pm Post subject: |
|
|
Yeah, I'm aware of that stuff now...I was doing some searching last night. But the thing is, I wasn't specifying for it to use pipes. In any event, for the configuration wizard I just told it to do the "Typical" settings and it seems to have worked....I used to be doing it the "Detailed" way.
I haven't done anything yet to check the integrity of this new install, but I'm sure everything will be ok....if not, I'll be back again! :D
Thanks though :) |
|
| Back to top |
|
|
GagnierA
-
Joined: 18 May 2004
Posts: 71
Location: Windsor, Ontario, Canada
|
| Posted: Sun Feb 27, 2005 7:28 pm Post subject: |
|
|
Well it installed and configured and everything as mentioned before, but it won't connect through a browser and whenever I try to access my databases with Navicat (better alternative to phpMyAdmin, in case weren't aware) MySQL crashes and so does Navicat. What the heck?
Had my hopes up, but still no go :( |
|
| Back to top |
|
|
admin
Site Admin
Joined: 03 Mar 2002
Posts: 1332
|
| Posted: Sun Feb 27, 2005 8:11 pm Post subject: |
|
|
GagnierA,
It seems to be a MySQL bug... Have you tried another version (not 5.0.2)? |
|
| Back to top |
|
|
GagnierA
-
Joined: 18 May 2004
Posts: 71
Location: Windsor, Ontario, Canada
|
| Posted: Sun Feb 27, 2005 8:16 pm Post subject: |
|
|
Yes I have...but 5.0.2 was working fine before....all that is explained in my first post, so I won't go over it again. But I guess I can try to uninstall again and see if 4.1.9 will work (even though I know it probably won't cuz I've tried this a million times).
:-\ |
|
| Back to top |
|
|
|
