Re: Missing OCX Controller.

On Wednesday 01 August 2001 12:00, James Newburrie wrote: > Hi All, > I have setup a development server at work, running NT4 Server, with IIS4 > which is all good, except when I try to install to PHP using the > precompiled version, I get a missing OCX controller error. Now I > understand that I will have to edit the configuration file manually at this > point, but I am unsure which settings do what mostly because of my > inexperience in having to do such things. > > Is there a way I can work around this by downloading the controllers > required, placing them where they should be, and then reinstalling the PHP > to find that it configures itself automatically, and my heartache can end? Honestly, it's not worth the effort - you don't have to edit any config files. All you have to do is set a script mapping in the Internet service manner. Here's the relevant section from the install.txt file - be brave, just do it :) To install PHP on an NT/2000 Server running IIS 4 or newer, follow these instructions. You have two options to set up PHP, using the CGI binary (php.exe) or with the ISAPI module. In either case, you need to start the Microsoft Management Console (may appear as 'Internet Services Manager', either in your Windows NT 4.0 Option Pack branch or the Control Panel=>Administrative Tools under Windows 2000). Then right click on your Web server node (this will most probably appear as 'Default Web Server'), and select 'Properties'. If you want to use the CGI binary, do the following: Under 'Home Directory', 'Virtual Directory', or 'Directory', click on the 'Configuration' button, and then enter the App Mappings tab. Click Add, and in the Executable box, type: c:\php\php.exe (assuming that you have unzipped PHP in c:\php\). In the Extension box, type the file name extension you want associated with PHP scripts. Leave 'Method exclusions' blank, and check the Script engine checkbox. You may also like to check the 'check that file exists' box - for a small performance penalty, IIS (or PWS) will check that the script file exists and sort out authentication before firing up php. This means that you will get sensible 404 style error messages instead of cgi errors complaing that php did not output any data. You must repeat from 'Click Add...' for each extension you want associated with PHP scripts. (.php is recommended. although .phtml and .php3 may be required for legacy applications.) Set up the appropriate security. (This is done in Internet Service Manager), and if your NT Server uses NTFS file system, add execute rights for I_USR_ to the directory that contains php.exe -- Phil Driscoll