On Thu, Jun 18, 2009 at 22:05, Shawn Simmons<elcid...@gmail.com> wrote:
>
> Wrote a small script to connect to the MySql database.  Tried to run the
> script (http://localhost/dbscript.php) and I get a 500 Internal Server
> error.  I have been up and down the web for two days looking for a solution
> and I am completely frustrated.  I HAVE to be missing something.  PLEASE
> PLEASE PLEASE help.  Thanks.

    HTTP code 500 is, as the error message suggests, a *server* error.
 Meaning, it has nothing to do with MySQL, and likely is not related
to PHP, but instead is a problem with the Apache configuration and/or
permissions of the file.  Check to make sure the dbinfo.php file is
owned by the appropriate user and has permissions set to allow it to
be read and executed.  Though not as prevalent as on *nix systems,
permissions errors can and do occur on Windows systems.

    If nothing seems out of place there, the next step is to check the
log files.  See if there's anything in Apache's error log related to
this message (there should be, and being a local server, it should be
one of the only things).

    Finally, if you can't find anything there, the next phase begins
by asking your question in the right place.  Now that you know it's
not a PHP error that's causing it, and since we can also rule-out
MySQL, we know it's an Apache issue.  Best bet in this case is to go
right to the source and ask on the httpd User Support list[1].  It
could be any number of things, from what I mentioned above about
permissions, to improper encoding, to a module not loading correctly,
to gremlin droppings in your upper memory (hey, it's Windows).

    In any case, searching the web for two days was indeed the best
place to start, so showing that intelligence gives you a leg up on
many of the folks on the Internet today --- so there's no doubt in my
mind that you'll have the issue resolved.... frustrating though it may
be right now.  If worse comes to worst, and you just want to move on
with developing, there are several simple options for deploying a WAMP
system.  I would personally recommend XAMPP[1], but there are many
other choices available as well.


    Ref:
        ^1: http://httpd.apache.org/lists.html#http-users
        ^2: http://www.apachefriends.org/en/xampp-windows.html

-- 
</Daniel P. Brown>
daniel.br...@parasane.net || danbr...@php.net
http://www.parasane.net/ || http://www.pilotpig.net/
50% Off All Shared Hosting Plans at PilotPig: Use Coupon DOW10000

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to