Based on the error you describe, I am pretty certain you hosed your
own machine. Maybe it was unknowingly following instructions, etc, and
you no longer remember the steps... but don't just blame Windows
Update. Take responsibility for your own actions.
[quoted text, click to view] > Failed to find the RegisterModule entrypoint in the module DLL C:\bin
> \php5\php-cgi.exe. The data is the error.
>
> This was a module I created at one time, but I later removed it. I
> have check my modules both at the machine level, the web site level,
> and the application/folder level and there are no references to this
> anywhere.
IIS7 looks for RegisterModule entrypoint of image files named within
<globalModules> section of %windir%\System32\inetsrv\config
\applicationHost.config. I am pretty certain you will find a C:\bin
\php5-php-cgi.exe globalModule reference in that file.
If you want to install PHP on IIS7, just read:
http://blogs.msdn.com/david.wang/archive/2006/06/24/HOWTO-Install-and-Run-PHP-on-IIS7-Part-3.aspx
[quoted text, click to view] > I searched the registry and all files in c:\windows and found nothing
IIS7 does not keep any configuration in the Registry nor in C:
\windows.
- Registry contains legacy hacks as well as non-runtime tweaks which
are not relevant in your scenario.
- %windir% does not include any IIS7 file other than the installation
log, %windir%\IIS7.log
[quoted text, click to view] > I don't know what is referencing this and how to find it so I can't
> get rid of it. My IIS is completely useless. I've uninstalled and
> reinstalled IIS but when I reinstalled all of my metadata settings
> reappeared, I wanted a clean install of IIS.
Try the following command to search for text:
pushd %SYSTEMDRIVE% & findstr /spinc:"C:\bin\php5\php-cgi.exe" *
Why should reinstalling IIS result in a "clean install of IIS". Please
define what you mean by "clean install of IIS".
I can only say that it is technically impossible since IIS7 consists
of 40+ Components, of which any combination could be a user's
"default" or "clean" install. But wait, what if user first installs 40
components but later removes 5 components and considers the 35
component installation to be "clean default install" -- how in the
world can IIS setup know that? All IIS setup knows is that users are
adding and removing components. It doesn't know what is "default" or
"clean".
Suppose you magically indicate to IIS setup that an installation with
42 components is the "default clean install". IIS still cannot backup/
restore the configuration for you because if you later add/remove
components, the backup configuration file may no longer be valid
because it can be referencing removed modules and fail to reference
added modules.
In other words, there is no default/clean install of IIS7, and
expecting reinstallation to magically clean things up and fix one's
mistakes is hardly realistic.
//David
http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //