ID: 29224
Comment by: MikeTodd13 at hotmail dot com
Reported By: marcschroeder at hotmail dot com
Status: Bogus
Bug Type: *Configuration Issues
Operating System: Microsoft Windows XP
PHP Version: 5.0.1
New Comment:
I was having the same problem, running Apache 2.0.50 and PHP 5.0.1
under WinXP Professional. The only way that I could fix it was to copy
libmysql.dll to the system folder. I have no clue why it can't be found
when I have the PHP directory in the PATH environment variable, but it
can't. Rather annoying; I would assume that this happens with all
extensions, and I certainly hope that it gets fixed in the next version
of PHP. I really don't like having to copy things into my system
directory if it can be avoided.
Previous Comments:
------------------------------------------------------------------------
[2004-08-27 23:27:52] at989 at earthlink dot net
I think this is a IIS problem, not PHP. I had the same thing several
times, and each time it goes away after I tweak something in IIS.
I changed the dll to which the php extension is maped to see if I got a
similar message or not (to see if this was indeed a php or iis problem).
I got "module not found" message. After I restored the mapping,
everything worked fine :-/
I have no idea why this happened. But i hope this will help someone who
knows more about iis to figure this out.
------------------------------------------------------------------------
[2004-08-23 18:31:01] bentrafford at yahoo dot com
Make that six users with the same problem. I've searched the bug
database, the net, newsgroups, and found no resolution to this issue,
other than PHP developers declaring it bogus.
Well, I've got my path updated, and the following set in my php.ini:
extension_dir = ".;c:/php/ext/"
I'm still getting the same issue as described above. This is either a
bug with PHP or a bug with the documentation.
------------------------------------------------------------------------
[2004-08-03 00:58:50] marcschroeder at hotmail dot com
Who set the status to 'Bogus'? Why?
I pretended that the current installation of PHP 5.0.0. does not
install PEAR DB?
5 users claimed that they could reproduce the bug.
The suggested solutions consisted in moving files around on a computer
to places where "it might work". The solutions only claim to "solve the
problem", but do not claim that there is no problem.
Somebody else suggests that I change the system path.
But I did add the following system variables already:
"PHP_PEAR_SYSCONF_DIR"="C:\\php"
"PHP_PEAR_INSTALL_DIR"="C:\\php\\pear"
"PHP_PEAR_DOC_DIR"="C:\\php\\pear\\docs"
"PHP_PEAR_BIN_DIR"="C:\\php"
"PHP_PEAR_DATA_DIR"="C:\\php\\pear\\data"
"PHP_PEAR_PHP_BIN"="C:\\php\\php.exe"
"PHP_PEAR_TEST_DIR"="C:\\php\\pear\\tests"
Do these environment variables have no effect?
I start to believe that PHP is a tool for hackers only, and that the
need of a controlled installation procedure is not present in the mind
of the PHP community.
This is really sad, as I like PHP a lot.
------------------------------------------------------------------------
[2004-08-02 14:02:47] dinojazz at hotmail dot com
I am having the issues as well. My php_mysql.dll is located in c:\php
and php.ini knows this. I've moved libmysql.dll to c:\windows\system32
as well. On top of this all, the extension=php_mysql.dll in php.ini has
been uncommented.
Yet, I get errors when I try to have mysql/php things loaded in my
webpage. It comes up with 'Unable to load dynamic library
'c:\php\php_mysql.dll\' - The specified procedure could not be found'.
I've tried the suggestions like php_mysql.dll to c:\windows\system32
and all the stuff. Even moved libmysql.dll to various places, but
nothing worked. I am kind of stumped here, looks like there's some
heavy bug in there.
------------------------------------------------------------------------
[2004-08-02 11:24:40] [EMAIL PROTECTED]
Either add c:\php to your system path, or copy all dlls from that
folder to system32.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/29224
--
Edit this bug report at http://bugs.php.net/?id=29224&edit=1
