IISAdmin is not started on instrumenting ISAPI Filter with Memory Leak detect tool
I am finding problem in starting W3SVC/IIS Admin service when I instrument
any memory leak detecting tool( bounds checker, insure++ , Rational purify)
with ISAPI Filter applicaton.
Actually the steps to follow for setting is all same as mentioned in MSDN To
debug an ISAPI extension using a debugging tool that cannot attach to a
I have copied and pasted the steps for the reference.
In the Control Panel, double-click Administrative Tools, double-click
1.. In the Component Services window, click Services.
2.. In the list of local services, right-click IIS Admin and click
3.. In the Log On tab, click the Local System account button, and select
the Allow service to interact with desktop check box and click OK.
4.. Repeat steps 3 and 4 for all processes that run under the IIS Admin
process, for example the World Wide Web Publishing Service and the FTP
5.. Open the Registry Editor. This can be done with the following command:
start regedit6.. In the Registry Editor, browse to the to
Execution Options key. Right-click that key, click New, and click Key. Type
the name Inetinfo.exe as the new key name.
7.. Right-click the Inetinfo.exe key, click New, and click String Value.
Type Debugger as the new string value name. Click Debugger to edit the
string value. Type in the full path to the debugger that you want to use,
for example, C:\Program Files\Debugging Tools for Windows\cdb.exe.
8.. When the World Wide Web Publishing Service is started, your debugger
will also be launched. You can now set appropriate breakpoints in your ISAPI
extension.You will not be able to set breakpoints in a component's source
code until the extension has been loaded into memory. For ISAPI extensions,
you will need to start Internet Explorer and request the ISAPI URL. As soon
as the page is loaded, you should be able to set breakpoints in your
component. Refresh the page to trigger the breakpoints you selected. If the
extension or filter cannot be loaded even once, for instance, if the fault
occurs in component startup code, you will need to load the ISAPI DLL prior
to starting the debugging session.
Just after setting the Image File Execution key , I am not able to
Error that comes is as follows:
Could not start the World Wide Web Publishing service on Local Computer.
Error 1068: The dependency service or group failed to start.
This gets solved immediately after removing the key under Image File
Execution. IIS Admin service gets started with no hiccups.
Does any one got an idea of such type of an error.
Thanks and Regards