note 84536 added to install.windows.extensions

If you are having trouble getting extensions to run and changes to php.ini don't seem to make a jot of difference you may find that your php.ini is not being read and you are running on defaults. The good news is that Elsint's fix (dated 26-Sep-2006) still works for php 5.2.6 under Windows Server 2003 SP2, on IIS6, running php as an ISAPI module. Diagnostic: run a test file <php phpinfo(); ?php> Load this in a browser and search the results for "Loaded Configuration File". This points to the .ini file in use, which I have found is not always the one I have been editing ... If your problem is with extensions: search for extension_dir in the phpinfo() results. If the entry which follows is C:\PHP5, or some other directory which does not exist on your drive you may need the registry fix. The alternative is to put the php.ini file somewhere along the search path, but this is not quite as clean. Background: If you run the installer packages: php-5.2.5-win32-installer.msi or php-5.2.6-win32-installer.msi and choose the default install directory the following registry entires are added HKEY_LOCAL_MACHINE SOFTWARE PHP InstallDir REG_SZ C:\Program Files\PHP\ WebServerType REG_SZ iis4ISAPI However, the installers above do not create the IniFilePath registry entry. So: you either go for a direct registry hack or create and run a registry file named: "[whatever].reg" If your install directory is the default for the above installers the contents should be the 4 (four) lines below (counting the blank one!) between the pseudo tags. <whatever.reg> Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\PHP] "IniFilePath"="C:\\Program Files\\PHP" </whatever.reg> (Note you have to have the double backslashes for the .reg file to work even though Windows reports it worked without them). Once you have the new registry key in place you may find it sufficient to restart the World Wide Web Publishing Service, which is also restarted if you take the slightly longer option of restarting the IIS Admin Service. If this works for you and you want to backtrack by undoing the registry changes to test if this was the fix that did it: you may need a reboot (not just a service restart) because of some rather irritating persistencies. ---- Server IP: 92.48.74.199 Probable Submitter: 195.112.2.119 ---- Manual Page -- http://www.php.net/manual/en/install.windows.extensions.php Edit -- https://master.php.net/note/edit/84536 Del: integrated -- https://master.php.net/note/delete/84536/integrated Del: useless -- https://master.php.net/note/delete/84536/useless Del: bad code -- https://master.php.net/note/delete/84536/bad+code Del: spam -- https://master.php.net/note/delete/84536/spam Del: non-english -- https://master.php.net/note/delete/84536/non-english Del: in docs -- https://master.php.net/note/delete/84536/in+docs Del: other reasons-- https://master.php.net/note/delete/84536 Reject -- https://master.php.net/note/reject/84536 Search -- https://master.php.net/manage/user-notes.php