Re: mscomctl.ocx error

On Saturday 12 May 2001 08:16, Bryan Leifert wrote: > when i try to install php on windows 2000 server i'm getting an error from > IIS saying that it can't find the file. everything else is working on the > server.. any ideas? > > bryan The installation notes (readme.txt) which the installer will have written to your php installation directory describe how to get round this, however... It's a known problem which we are in the middle of trying to fix - and you may be able to help us here to see if our proposed fix for this problem works - it's something we can only test on a machine which is exhibiting the problem. If you have the time would you mind doing the following and reporting back? >First, a few more words on what the problem is. Some users (and it seems to >be only a very small percentage) report that the php installer fails when >configuring IIS (or PWS) on NT4 or above because an OCX control is not >registered on the system. The OCX control is responsible for displaying the >treeviewer of the IIS scriptmap nodes so the user can select which ones to >map the various php file extensions into. > >The tree viewer is provided by either of two OCX controls, MSComCtl.ocx or >ComCtl32.ocx. These are almost always to be found in the WINNT/System32 >folder on real world machines, however they are not always registered. > >Cynic's modification to the software is to check whether one of the controls >is registered, and if not, to register on or the other. >Download the IISConfig.exe that Cynic posted at >http://www.1st.cz/cynic/IISconfig.zip >Extract the files. >Then from the command line, run "IISConfig.exe <path to your php.exe> .php" > >so for example, on my system this would be: > >iisconfig.exe c:\phpphp.exe .php > >You should hopefully get a message box informing you that the control has >been registered, then the software should do it's stuff and display the >scriptmap nodes. You can tick the nodes where you want php to work, and >then click on OK. Your PHP installation will then have been sucessfully >completed. >Then let us know ihow you got on. NB the >software then unregisters the OCX again so that your system is left in the >same state as it was previously. Cheers -- Phil Driscoll