Basically MySQL is not working with PHP5.3 on windows7 with IIS7.
I have found that I might need to move a file, libmysql.dll, to system32… but php3 doesn’t come with it. Has anyone gotten PHP5.3 to work with MySQL5.1 on Windows?
Made a post on servervault about this and no luck there.
“not finding” will produce trivial “could not connect” error
instead of “guessing” I’d suggest to take a look at web-server’s error log
When you going to enable MySQL in PHP, you don’t need sql server at all. At least you can connect to the external one.
When PHP starts with no errors and phpinfo() shows mysql support, only then you can switch to mysql setup. And starting wordpress is even more far away from this point.
yes i have done all that. A file named libmysql.dll is included in the Windows PHP distribution and in order for PHP to talk to MySQL this file needs to be available to the Windows systems PATH.
The above was taken from the php website. I’m running PHP5.3 and there is not find a file named libmysql.dll. I even tried the sitepoint tutorial on this topic. I may have to use php5.2
And there are no errors and phpinfo() shows mysql/mysqli are enabled. All that happens is my sever times out after 60 second like the ini tell it to.
In the official PHP distributions from 5.3 onwards, MySQL Native Driver is enabled by default, so no additional configuration is required to use it. All MySQL database extensions will use MySQL Native Driver in this case.
So was it just a matter of using 127.0.0.1 (I have the t-shirt) instead of localhost?
If so, then a better fix might be to comment out the localhost line in the hosts file, so that IPV6 isn’t used instead.
#::1 localhost
That way you won’t have to make the change in all of your files that use localhost to connect.
The other benefit is that when MySQL version 6 comes out with IPV6 support, you can uncomment the line and have full IPV6 localhost capabilities once again.
This gives me hope. Yesterday I upgraded to the latest version of PHP5.3 and immediately noticed a problem, and ended up downgrading back to my old 5.2 version. I will try this to see if it solves my problem.