ID: 26125 Updated by: [EMAIL PROTECTED] Reported By: nickh at supportteam dot net -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Windows Server 2003 PHP Version: 4.3.3 New Comment:
This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2003-11-06 18:18:43] nickh at supportteam dot net Nope. The php binary is found in e:\php on this particular server. By Default, PHP has always looked (by always, I mean on all 2000 Server installs I've done) in the c:\winnt or c:\windows, whichever you installed to. It is behaving differently under 2003. Eventhough phpinfo says c:\windows, it's not. ------------------------------------------------------------------------ [2003-11-06 14:56:14] [EMAIL PROTECTED] This gives a bit of a hint why: http://www.php.net/manual/en/faq.installation.php#faq.installation.phpini With IIS, the search propably starts where it's binary is located at. I haven't got w2k3 so I can't really test this. ------------------------------------------------------------------------ [2003-11-04 18:35:32] nickh at supportteam dot net Description: ------------ Under Windows Server 2003 when I run a phpinfo() it says the Configuration File Path is C:\WINDOWS. I was having trouble with the sessions path and when running a filemon capture (sysinternals filemon) I saw it was auctually looking for the ini in C:\Windows\system32\inetsrv. Placing the ini there fixed the problem. It appears that the ISAPI version of PHP4 .3.3 says the INI should be in one place but it looks for it elsewhere. I have tested this on 4 different Windows Server 2003 Standard servers that we have and it's the same on all 3. Reproduce code: --------------- N/A Expected result: ---------------- N/A Actual result: -------------- N/A ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=26125&edit=1
