Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Problems making MySQL connection...URL Prefix Errors

Participant ,
Dec 08, 2006 Dec 08, 2006

Copy link to clipboard

Copied

I'm currently trying to connect to a client's MySQL database hosted by a company called Website Source. Every time I try to make the connection I get a prompt that says:

HTTP Error Code 404 File Not Found. Here are some possible reasons for the problem:

1) There is no testing server running on the server machine.
2) The testing server specified for this site does not map to the http://64.40.144.148/_mmServerScripts/MMHTTPDB.php URL. Verify that the URL Prefix maps to the root of the site.

I've tried various URL prefix's. IP addresses, static URL's, nothing is working. Anyone know where I might be goofing up?

I've done connections like this before but never experienced problems like this and Website Source's Tech Support is of no help.
TOPICS
Server side applications

Views

1.1K
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 08, 2006 Dec 08, 2006

Copy link to clipboard

Copied

databell wrote:
> 2) The testing server specified for this site does not map to the
> http://64.40.144.148/_mmServerScripts/MMHTTPDB.php URL. Verify that the URL
> Prefix maps to the root of the site.

I've just checked that URL, and MMHTTPDB.php isn't there. You're
obviously trying to use a remote server as the testing server. The value
entered as Host directory in the testing server definition must match
the URL prefix. So, if you use http://64.40.144.148/ as the URL prefix,
the pathname in Host directory must be the same as you would use to
upload a file that would be displayed as http://64.40.144.148/index.php.

Usually, this is something like /home/somewebsite/htdocs/.

--
David Powers, Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Dec 08, 2006 Dec 08, 2006

Copy link to clipboard

Copied

Right, I'm using a remote server. I'm not testing locally on my own Mac.

So I followed (or at least I think I did) your instructions but they're still not working right. I found out from the host instead of the IP address I should use 'web11.websitesource.net' as the host name and according to them the path to the home directory is /hsphere/local/home/alison

So I put that path in the host directory fields for both remote info and testing server and changed the URL prefix to http://web11.websitesource.net and unfortunately I'm still getting the same 404 errors.

Tried that but still getting the same errors.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 09, 2006 Dec 09, 2006

Copy link to clipboard

Copied

databell wrote:
> I found out from the host instead of the IP address I should
> use 'web11.websitesource.net' as the host name and according to them the path
> to the home directory is /hsphere/local/home/alison

The URL that you're using gives access to your control panel, not to
your website root. I've had a quick look at the websitesource.net FAQ,
and it says that you need to put your website in a directory with the
same name as your domain name. Have you registered a domain name yet,
and if so, have you created the necessary home directory for it?

You need to get your website sorted out with a test home page before you
can start experimenting with using the remote server to connect to your
database.

--
David Powers, Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Dec 09, 2006 Dec 09, 2006

Copy link to clipboard

Copied

Yes, the domain was registered a long time ago and there already is a site up:

http://www.filmco-op.com/

Now that's a quickie site that the client did herself. I'm currently doing the redesign which will include this form.

So there already is a filmco-op.com folder setup. Now the one thing I wonder about is what the actual path is to get to that folder. Because it's actually a subfolder of the clients main folder as she's on a shared account and has three other domains in the main/root folder. Could that be the problem? Or is it something else?

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 09, 2006 Dec 09, 2006

Copy link to clipboard

Copied

databell wrote:
> So there already is a filmco-op.com folder setup. Now the one thing I wonder
> about is what the actual path is to get to that folder. Because it's actually a
> subfolder of the clients main folder as she's on a shared account and has three
> other domains in the main/root folder. Could that be the problem? Or is it
> something else?

The way that Dreamweaver communicates with MySQL is by using two scripts
in the _mmServerScripts folder, which must be at the same level as the
URL prefix. _mmServerScripts doesn't show up in the Dreamweaver Files
panel, so you may need to check that it's in the right place by using an
ordinary FTP program.

Going by the information you gave earlier, plus what I read on the
hosting company's FAQ, the site is probably in
/hsphere/local/home/alison/filmco-op, which is what you need to use for
the Host directory field. The URL prefix should then be
http://www.filmco-op.com/.

--
David Powers, Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Dec 09, 2006 Dec 09, 2006

Copy link to clipboard

Copied

Actually, no. That's not it. I get an FTP error when I try to test a connection using /hsphere/local/home/alison/filmco-op as the host directory. According to Website Source, /hsphere/local/home/alison/ is the path to the database. Not the web folders. It's really weird.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 09, 2006 Dec 09, 2006

Copy link to clipboard

Copied

LATEST
databell wrote:
> Actually, no. That's not it. I get an FTP error when I try to test a connection
> using /hsphere/local/home/alison/filmco-op as the host directory. According to
> Website Source, /hsphere/local/home/alison/ is the path to the database. Not
> the web folders. It's really weird.

You need the path to the top-level web folder, not the database. Only
the hosting company can tell you the correct path. Ask them where you
would need to upload a file that would become
http://www.filmco-op.com/test.html.

--
David Powers, Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines