ID:               41350
 Comment by:       OPunWide at hotmail dot com
 Reported By:      graham at directhostinguk dot com
 Status:           No Feedback
 Bug Type:         MySQL related
 Operating System: Windows 2003
 PHP Version:      5.2.3
 New Comment:

I'm a newbie at this, and am installing php for the first time. Very
basic setup, running WinXP, using IIS 5.1 and PHP 5.2.5, installed using
the Windows installer. 

When I first installed I included support for MySQL in the options, but
had not installed MySQL. The error happened with a psp script consisting
only of pspinfo(). I went back to the installer and removed support for
MySQL and the problem went away.

I don't think the folks at MySQL can be blamed for this one.


Previous Comments:
------------------------------------------------------------------------

[2008-02-07 22:27:08] WS6TA at txlanes dot com

I have to agree about the impression this makes on potential LAMP
adopters.  I am a long-time Windows/MSSQL person looking at the LAMP
stack as an alternative to MS.  However, I download PHP 5.2.5 and start
reading the manual only to get the error "Error in
my_thread_global_end()" the first time I used the CLI.  So, I go
searching and find all kinds of references to dll swaps for PHP side AND
the MySQL side.  I don't even have MySQL installed yet...  I was looking
at PHP's ability to be a standalone scripting tool as well as a
web-database tool.

Anyway, I then find this thread where it appears the bug has been
around since approximately May 2007 and PHP version 5.2.3.  I commented
out "extension=php_mysql.dll" in the php.ini to stop the error, but I
think I will want this extension once I install MySQL.

My hat's off to the people that started and have contributed to the PHP
codebase.  Please understand that I am not trying to bash anyone.  I
simply want to reiterate the PHP is crucial component to the LAMP stack
and having to search for a bug fix on the very first run discourages
potential new adopters.  I'm very impressed with what I know about PHP
thus far and would hate to think a potential  adopter could be
discouraged at square one in their evaluation.

------------------------------------------------------------------------

[2008-01-22 20:30:48] codeslinger at compsalot dot com

Ping,
Can we get php updated please?  This problem is now one year old.

Everyone who updates to the latest Windows php = 5.2.5 encounters this
bug, it results in total breakage of loading the mysql dll.

This bug has cost thousands upon thousands of man-hours to be
expended/wasted by site admins in trying to locate the cause of the
problem and the fix for it.  In some cases it has also caused people to
abandon the use of php-mysql programs altogether.

According to MySQL Bug: http://bugs.mysql.com/bug.php?id=25621

The final resolution is that the problem was with mysql not php and
that the problem was fixed awhile ago, and that all that is needed is
for php to update to the latest mysql library.

Given the fundamental importance of the php mysql interface, as in
LAMP, it is inexplicable that it has taken an entire year to resolve
what appears to have been a fairly simple fix.

------------------------------------------------------------------------

[2008-01-11 21:39:37] jmair at parkcountyre2 dot org

IIS 6 on Windows 2003 server fully patched. php 5.2.5 mysql 

This issue was killing me for a week. I tried every successful attempt
from previous posts and no resolve.

I was also getting this problem with no mysql.

I downloaded and installed fastcgi and followed the manual install for
fastcgi and php, not only is the Php not displaying the error, but it's
running faster than I've ever seen, maybe almost as fast as a linux box
=0

hope this helps somebody.

here is the link.
http://www.iis.net/articles/view.aspx/IIS7/Hosting-Web-Applications/PHP/Using-FastCGI-to-Hos
t-PHP-Applications-on-IIS-6-0-?Page=2

------------------------------------------------------------------------

[2008-01-10 17:49:50] amoo_miki at yahoo dot com

This is caused by windows security:

to be sure:
1) Check if the drive where PHP is installed is an NTFS partition.
2) If yes, "Read & Execute" for "Everyone" for the "ext" folder.

php -v at the command-line should not show you the error anymore.

------------------------------------------------------------------------

[2008-01-07 12:14:01] jaco at jump dot co dot za

I was able to reproduce this on a very basic instalation:

Apache 2.2.4
PHP 5.2.5
Windows 2003 Server
NO Database installed

<?
$fp = fsockopen("192.168.1.105", 3312);
fclose($fp)
echo "DONE";
exit;
?> 

This executes 100%, and gives no errors, but as soon as I stop apache,
it gives me the message in the apache error log

Error in my_thread_global_end(): 1 threads didn't exit

So it seems to me more of a sockets problem than a mysql problem.

When I run the same script in CLI, I get no error.

------------------------------------------------------------------------

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/41350

-- 
Edit this bug report at http://bugs.php.net/?id=41350&edit=1