-
Title
FLDN agent sets w3wp to run with starter.exe -
Description
FLDN agent sets w3wp to run with starter.exe . starter.exe is the parent for w3wp.exe even though its not an executable and there is no CORE_Profiler setting in Svchost.exe properties. However, all the .NET mnitoring seems to be working.
It uses the windows debugger hook instead of the .NET hook to monitor the w3wp process. The other server of the pair (same config) uses the standard Cor_Enable_Profiling .NET debugging hook. So customer is wondering why does this one use "starter.exe" instead.
Tried a re-install that had helped correct this, but now that also hasn't helped it seems
-
Cause
In order for the agents to function correctly with IIS 7 installations, the IIS 7.0 WMI provider must be installed on the monitored server.
Viacode discovered a bug in the code that determines which IIS version is running. The agent assumes WMI toolkit to be installed for IIS7. In this case, the toolkit wasn't installed, and the bug caused the agent to use instrumentation mechanism intended for IIS5.
Documentation bug DN-393 filed
-
Resolution
Check and see if IIS Management Scripts and Tools is installed on the customer environment
For IIS 7.0 Installations Only
In order for the agents to function correctly with IIS 7 installations, the IIS 7.0 WMI provider must be installed on the monitored server. There are two ways to install the WMI provider so that the Agent will be able to see IIS7:Install WMI Provider
Install the IIS 7.0 WMI provider by selecting the IIS Management Scripts and Tools component under Management Tools (or Web Management Tools). In Windows Vista, this is in the Windows Features dialog under Internet Information Services. On Windows Server® 2008, this is in the Server Manager under the Web Server (IIS) role.
Install WMI Tools (includes CIM Studio)
Install the WMI Tools suite from the Microsoft Download Center at:
I found it under Control Panel->Programs and Features->Turn Windows features on or off->Internet Information Services->Web Management Tool
-
Defect ID
DN-393 -
Additional Information
After performing above steps, if you still see the starter.exe attached, perform the below
Under the Foglight for .NET agent deployment directory, open v5.6.503\Configuration\Standard\Starter.config and change activationMode parameter for w3wp.exe to "Starter", remove applicationType (by default it has "Executable" value), save file and close it.
- Open, then close MMC Console to update registry
- Change it back to "Service" with applicationType = "Executable" added
- Open, then close MMC Console to update registry
-
validate registry settings
-
no debugger key on w3wp, under
HKEY_LOCAL_MACHINE\software\microsoft\windows nt\currentversion\image file execution options\w3wp.exe
- if it's there, delete it
-
Environment should be set for IISADMIN, WAS, W3SVC, under
HKEY_LOCAL_MACHINE\system\currentcontrolset\services\IISADMIN|WAS|W3SVC
-
if the Environment is missing, add it manually
COR_PROFILER={AD5651A8-B5C8-46ca-A11B-E82AEC2B8E78} Cor_Enable_Profiling=1
-
if the Environment is missing, add it manually
-
no debugger key on w3wp, under
- restart IIS