MRBS, PHP, IIS 6.0, and one 500 error

[mossj]

When I try to access MRBS on the server it fails reporting a 500 error, I did think this was to do with php but I have confirmed php is working using a example index.php.

Any ideas? Ive not seen this error before so im stumped.

P.S the address is http://webmail.ashlawn.org.uk/booking/web

[Pashers]

I'm going to have to say the obvious I'm afraid... I think there's a programming error in the code. So this is quite a difficult problem without much more info.

[SYNACK]

I got a 404 error so I'm guessing its no longer there, perhaps a screenshot of the error.

[mossj]

I'm going to have to say the obvious I'm afraid... I think there's a programming error in the code. So this is quite a difficult problem without much more info.

The *codes* a unzip of the stright cut mrbs folder without even touching the config (If the config isn't touched it gives a 'can't find database' error, which i would of been happy with). So it can't really be a programming error.

P.S the 404 error was the NM Killing the server.... which he's just done again... Linky won't work anymore as I uninstalled php from it (exchange has thrown its rattle and I'm not up being the last one to make changes the server)

[dgsmith]

Sorry to drag this up (I know it was from January), but I have just come across this problem also when trying to install a fresh copy of the latest MRBS version (was hoping to upgrade over the summer). Is a new install of PHP, on IIS7 (Win2k8), and I have other php files which work ok.

Did you ever find out what the problem was?

[kmount]

A http 500 can be several things, I'm not particularly well versed on IIS but I would imagine there would be an entry in the error logfile which might help?

[mossj]

No didn't bother in the end, just hosted it on an external (linux) based host

[dgsmith]

Having looked for logs, I couldn't actually find any, so I checked the config to see where the logs where located - none where being created! I just uncommented the line which determines where the logs log to (file or sys log) in php.ini and now the error has gone. Default install config had nowhere to log to (log config lines where commented out). I guess a 500 error could be a variety of things, but for us that is all it was.