467,188 Members | 1,403 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,188 developers. It's quick & easy.

CGI to ISAPI, now no MySQLi

Have been running PHP 5.1.1 successfully for quite some time as CGI in IIS
5.1 on my Windows XP Pro SP2 laptop, with MySQL Server 5.0.18 and the
mysqli extension. I wanted to see if I could get away from some CGI
timeouts I've been experiencing by moving from GCI to ISAPI on PHP. So I
removed the mapping for the CGI .exe and added in the mapping for the
php5isapi.dll, which in C:\PHP. The php_mysqli.dll file is in C:\PHP\ext.
I made sure extension_dir = "C:\PHP\ext" was set in php.ini, and that the
uncommented line extension=php_mysqli.dll was present there as well.
Following the directions of some other discussions I read elsewhere, I also
moved the libmysql.dll file from C:\PHP to C:\WINDOWS\system32. I stopped
and restarted IIS. Now, the error I get on the first line of PHP in my app
that tries to create a new mysqli object is:

Fatal error: Class 'mysqli' not found in C:\Inetpub\wwwroot\vsx\includes
\sessions.php on line 34

What am I missing here! I'm tearing my hair out now. Someone please tell
me what setting I have to change to get MySQLi to work in PHP 5.1.x as an
ISAPI.

Christopher Watson
AAVSO VSX
Jan 15 '06 #1
  • viewed: 1866
Share:
6 Replies
Is your php.ini sitting in C:\PHP? The ISAPI module won't use it if
it's there.

Jan 15 '06 #2
"Chung Leong" <ch***********@hotmail.com> wrote in
news:11**********************@o13g2000cwo.googlegr oups.com:
Is your php.ini sitting in C:\PHP? The ISAPI module won't use it if
it's there.


Yes, as a matter of fact, my php.ini IS sitting in C:\PHP. Where should it
instead go?
Jan 15 '06 #3
Put it in C:\Windows.

Jan 15 '06 #4
"Chung Leong" <ch***********@hotmail.com> wrote in
news:11**********************@f14g2000cwb.googlegr oups.com:
Put it in C:\Windows.


That's exactly where I put it (having read that elsewhere), and all is
working now. Thank you.
Jan 17 '06 #5
On 15 Jan 2006 07:37:36 -0800, "Chung Leong" <ch***********@hotmail.com> wrote:
Put it in C:\Windows.


There's never any need to move things to the Windows system directories, and
it only leads to pain later. You can do it more cleanly with environment
variables.

Use PHPRC to control where the php.ini file is read from.
Use PATH to add DLLs.

--
Andy Hassall :: an**@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Jan 17 '06 #6

Andy Hassall wrote:
On 15 Jan 2006 07:37:36 -0800, "Chung Leong" <ch***********@hotmail.com> wrote:
Put it in C:\Windows.


There's never any need to move things to the Windows system directories, and
it only leads to pain later. You can do it more cleanly with environment
variables.

Use PHPRC to control where the php.ini file is read from.
Use PATH to add DLLs.


Agree. Putting stuff in C:\Windows isn't the best. On the other hand,
it gets really confusing when you put it somewhere else.

Jan 18 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Roy Shaw | last post: by
2 posts views Thread by ojorus | last post: by
12 posts views Thread by davids58@gmail.com | last post: by
2 posts views Thread by Curtis | last post: by
13 posts views Thread by Schmidty | last post: by
21 posts views Thread by Daz | last post: by
2 posts views Thread by Michael | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.