Hi everyone!

I'm using PhpED as a trial, and I'm impressed. However, I have an issue.

I'm developing on my machine, where I have IIS, PHP, MySQL, and phpMyAdmin installed, and they've all been operating in harmony for a while. I added PhpED to the mix recently, allowing it to install its own PHP. I am also using the PhpED web server, which is configured to use a different port then IIS.

Slick. All is well.

Until I added phpMyAdmin as a project to PhpED and ran it from within the editor. IIS will no longer serve up phpMyAdmin, but I runs fine in PhpED.

More details:
o With my development code, I am working on a copy separate from IIS. IIS does not try to serve the same files.
o With phpMyAdmin, I added the directory where phpMyAdmin was already installed for IIS, under \inetpub\wwwroot\... when adding the project to my workspace.
o No configuration was needed to run phpMyAdmin via phpED. It fired up correctly the first try.
o The error I receive when trying to launch phpMyAdmin normally is:
1.20 I receive the error "cannot load MySQL extension, please check PHP Configuration".
o I can run phpMyAdmin normally using IE (or Opera) if I specify the port that PhpED is using. Otherwise not.

NOTE: I didn't realize this earlier, since I'd been doing all my development in PhpED. But now I can't use MySQL at all via IIS. This was NOT the case upon my original install of PhpED. I was happily using myPhpAdmin in IE7 served up by IIS while running my code (which also uses MySQL) in PhpED. I just tried running an older version of my code still sitting on IIS, and found that IIS can no longer reach MySQL. Again, this wasn't the case when I first installed PhpED.

Any thoughts?

I do not think this is a PhpED issue, but rather some coincidence of events after installing PhpED. The instance of PHP that is installed by PhpED is used by PhpED's built-in SRV web server. There is no reason why one cannot use this PHP installation with IIS too, but in my own setup I prefer using a separate instance of PHP. I suspect that applies to your setup too.

The error message you get suggests that the MySQL extension is not loaded for the PHP instance used with IIS. The easiest way to check this, is to create a PHP script in your \inetpub\wwwroot\phpmyadmin folder that calls phpinfo():


Run this script via IIS and via SRV (with the 8080 port) and compare the output. My guess is that the output for SVR will show a correctly installed MySQL extension (and therefore PhpMyAdmin works), and no MySQL extension for the IIS output (and therefore the MySQL error). If this is indeed the problem, you need to enable the MySQL extension in your php.ini -- check the phpinfo output for the location of your php.ini.

I hope this helps

Right you are! Coincidence of events.

Looking at phpinfo() revealed that I wasn't loading a php.ini file at all when served via IIS!

I believe that happened during the PhpED install, rather than due to phpMyAdmin, but didn't make itself known until I restarted my machine and IIS lost the configuration it was running with. An environment variable that directed PHP to load a specifc INI file had somehow, mysteriously, had a '~' character appended to it. I removed the '~' character, restarted my machine, and now both IIS and PhpED are happily running phpMyAdmin and other MySQL apps.

Thank you!

Mark Morrell
--Old School Developer
--PHP Newbie

I am glad my response steered you in the right direction