PHP Startup error message in 9.0.0.97

[robertc]

Hello,
Since upgrading to version 9.0.0.97 the other day, when I am editing some files, I get pop-up messages saying:
"PHP Startup: Unable to load dynamic library "php_mysql.dll' - The specified procedure could not be found."
and
"The procedure entry point mysql_set_character_set could not be located in the dynamic link library LIBMYSQL.dll"

I have checked the setting of 'extension_dir' in php.ini and it points to the correct directory and the file (php_mysql.dll) is there.
I have tried changing the location from ".\" to specifying it absolutely e.g. "c:\Program Files\php\" but the same happens.

All of my local sites work fine and deliver PHP content with no errors being reported (or written to the logs), even the one that is giving the error when editing in Webuilder.

I seem to remember something similar happening when I upgraded to WeBuilder 2007 but can't find any notes about it or entries on the forum.


I'm on Vista Home Premium using:
WeBuilder 9.0.0.97
PHP version 5.2.3
Apache 2.2.4
MySQL Ver 14.12 Distrib 5.0.45 for Win32.

Anyone else having or had similar problems or any ideas?

thanks
Robert

[chrisjlocke]

php is currently at 5.2.6. I don't think its specifically that, but you could try using the latest version of php.

[robertc]

Thanks Chris,
I have thought about upgrading PHP but I've heard that 5.2.6 has quite a few bugs on windows so don't want to break anything else at the moment.

As I said, it all worked fine under WeBuilder 2007.

thanks
Robert

[chrisjlocke]

Ok, have you tried reinstalling your current version of PHP?

[robertc]

I haven't tried that but why do you think that would help when everything else (all of my websites etc.) are working perfectly OK?

The error occurs as soon as I make any changes to a PHP file - even just inserting a newline (CR).

I have gone back to version 2007 of WeBuilder and the problem doesn't happen.
I went back to 2008 and the problem re-occurs.
I have gone back to 2007 and the problem goes away again.
I'm sticking with 2007 for the moment as I have a lot of stuff to complete.

As I also said, I'm pretty sure something similar to this happened when I upgraded to 2007 last year. Although I can't remember exactly what was done to resolve it, I seem to recall a new DLL was posted (although I might have dreamt that!)

cheers
Robert

[chrisjlocke]

but why do you think that would help

I've no idea. Usually the simplest ideas work best!
I was kinda hoping some file has gotten overridden during the installation of another program, and re-installing php may solve it.
I guess you could also try reinstalling WeBuilder 2008. As no-one else has reported this issue, it would seem likely its some file corruption / mismatch somewhere.

[robertc]

OK,
reluctantly, I've now reloaded both PHP and WeBuilder 2008 but it's still the same.
(PHP reluctantly because I know everything - except weBuilder - appears to be working fine.)

It's still the same - WebBuilder 2007 works OK. 2008 still throws the same error.
It happens as soon as a line is added or removed from the source file - even a blank line.
I've tried removing the mapping of the website but it still happens.
Why would it be trying to call this procedure / file in the first place?

cheers again
Robert

[robertc]

Any more advice on this matter please?

It's still causing the same problems and now I'm running the latest versions of php (which did cause a number of other failures on other sites and took a couple of hours to sort out!)

Or am I going to have to stick to 2007?

cheers for your help.
Robert

[chrisjlocke]

Some tips here:
http://www.somacon.com/p447.php

It too suggests checking extension_dir, and disabling extensions.
Try disabling ALL extensions, to see if it works. If it does, enable one at a time to see which one fails.

The above link also suggests adding the php path to your windows path.

[robertc]

OK, thanks for the various help.
It's sorted now and I'm pleased to say it wasn't WeBuilder that was causing the problems but the configuration of PHP.
No idea why it worked under 2007 and not under 2008 but hey-ho.

It seemed to be caused whenever a change to a file was made and for some reason this kicked off PHP interpreter.
As I have it set locally to display startup errors, it was doing just that!
Why does it do that (kick off the PHP)?
Isn't that a bit of an overhead on the pc?

Anyway, it's working so thanks.
Robert