PHP MySQL Error Code 500

[arnhemcs-QVZdUa]

May be someone can help me out with this problem.

I have setup a new site using PHP MySQL and Dreamweaver 8.02.
Dreamweaver connects to the database but after creating a recordset the recordset cannot be used.

instead Dreamweaver returns:
HTTP Error Code 500 internal Server Error

Any help will be much appriciated.

Jos

[Newsgroup_User]

isn't there an additional & more specific code error in the message? if
you're using IE probably it's configured to friendly error messages. go
to Internet options menu & disable that option

arnhemcs wrote:
> May be someone can help me out with this problem.
>
> I have setup a new site using PHP MySQL and Dreamweaver 8.02.
> Dreamweaver connects to the database but after creating a recordset the
> recordset cannot be used.
>
> instead Dreamweaver returns:
> HTTP Error Code 500 internal Server Error
>
> Any help will be much appriciated.
>
> Jos
>

[arnhemcs-QVZdUa]

Thanks for the reply John.

I am working on Mac OS10.4 and have done this already with another host.
There it worked OK
It is Dreamweaver itself that returns the Error message.

> HTTP Error Code 500 internal Server Error
is the complete message I get.

In the bindingspanel the recordset is shown but has no content

Any idea what I should do?

[Guest]

Hi,

I'm having this exact same problem. Have spent a good 4 hours last night googling for a solution but have found nothing.

Has anybody in the community found a solution to this?

[Guest]

I had this problem. It was in my case due to some faulty code in the php.ini file. It can also be due to the .htaccess file.

[Newsgroup_User]

andysky escreveu:
> Hi,
>
> I'm having this exact same problem. Have spent a good 4 hours last night googling for a solution but have found nothing.
>
> Has anybody in the community found a solution to this?
---------
Take a look at your php.ini, something can be wrong.
Maybe, something with the mysql extension.
-----
zerof

[Palmedia_co_uk]

Hello,

I have also had the same error - namely that whilst I could connect via ftp, upload/download files, and view database tables, any attempt to view of modify recordsets resulted in error 500.

Having checked other potential causes (e.g. selection/non-selection use of passive FTP setting, enabling of php, etc.), on the back of posts here I contacted my host and asked if if could relate to mod security, as further investigation revealed that the issue only occurred on sites where mod security had not been disabled (I don't like to disable mod security for obvious reasons - and I'm told you can't do that site by site with apache2 anyway).

After a few false starts, the problem was resolved - with the following response from my host: "The false positives were being generated by "/_mmServerScripts/MMHTTPDB.php" and that is what we've worked around in the rules. As such, any domain on [servername] using that script in the same way shouldn't generate a false-positive moving forward."

So it seems the answer (assuming your on an apache server of course) may be to modify the rules to allow full access for MMHTTPDB.php.

I hope that is of help to some.

[digimech]

Fastest way to fix this error is to remove the connection scripts:

_mmServerScripts

     MMHTTPDB.php

     mysql.php

In the pulldown on the site files tab, under "Sites" is "Remove Connection Scripts" at the bottom. Do that and try to connect again. DW will generate new ones and that usually does the trick.

[arnhemcs-aeQ5LA]

Thanks Palmedia and digimech,

It was a question from 2006 and a found a workaround to first fully test it locally but it is good to know.

Jos