This article will contain check-list if nothing appears in the console after the installation of JENNIFER .NET agent.

Helper Utility To check the Problem

Process Explorer: download it from this link: http://technet.microsoft.com/en-us/sysinternals/bb896653.

Is your request sent to the website?

After sending a request, go to the task manager and see if the w3wp.exe process has been created.

Check whether the site is ASP or ASP.NET

In the case of ASP.NET website, when you check the memory in your task manager, you will see that at least 50MB of memory is occupied. If not, then the website is not likely to use .NET framework.

Using the latest version of Process Explorer you can launch the process's property windows and you will see that the ".NET Performance" tab appears in the menu as shown: 

Or in your Process Explorer, you can select the process and press "Ctrl+D" key.

Then, as shown below, you will see a list of DLLs in the process.

The list must be a .NET process only if it has the "System.dll" file.

Is the w3wp.exe process corresponding to the web application subject to monitoring?

In IIS task manager, launch the property windows for the web application subject to monitoring and check the "Application Pool".

Run your process explorer and launch the property windows for the process. Check if the "APP_POOL_ID" value in the environment variable matches the "Application Pool" name of the web application

Check the properties if JENNIFER .NET profiler.

In the Process Explorer, select "Environment" tab and check the following environment variables: 

• COR_ENABLE_PROFILING: 1
• COR_PROFILER: {FF8C2B6C-DBB5-4AED-9876-2CED6FFAF4C9}

Are JENNIFER .NET profiler related DDL's registered in the system properly?

Check if the following items are in "C:\Windows\assembly" folder

• BaseClassLibrary20.Clr??
• BaseClassLibrary20.Web.Clr??
• Jennifer40.Clr??
• Jennifer40.Profiler.Clr??

If .NET framework 4.0 is installed on the server, then you also need to check if the following items are installed in "C:\Windows\Microsoft.NET\assembly\GAC_MSIL" folder

• BaseClassLibrary20.Clr40
• BaseClassLibrary20.Web.Clr40
• Jennifer40.Clr40
• Jennifer40.Profiler.Clr40

Perform registry test

For 32-bit OS: 

Check the DLL path defined in InprocServer32 key in the lower area of the HKEY_CLASSES_ROOT\CLSID\{FF8C2B6C-DBB5-4AED-9876-2CED6FFAF4C9}. (Check if the file actually exists)

For 64-bit OS: 

Check the DLL path defined in InprocServer32 key in the lower area of the HKEY_CLASSES_ROOT\CLSID\{FF8C2B6C-DBB5-4AED-9876-2CED6FFAF4C9}. (Check if the file actually exists)

Check if JENNIFER.NET profiler related DLL are loaded properly

In your Process Explorer, check the process.

• In the case of 32-bit OS, check if the "DotnetProfiler.dll" file is loaded. 
• In the case of 64-bit OS, check if the "DotnetProfiler64.dll" file is loaded.

If they exist, check if the following DLL's have been loaded

• BaseClassLibrary??.Clr??.dll
• BaseClassLibrary??.WebClr??.dll
• Jennifer40.Clr??.dll
• Jennifer40.Profiler.Clr??.dll

Check the property of JENNIFER.NET profiler.

• After performing iisreset, delete all the contents of the [installation folder]\log directory and send another web request to check if "Jennifer_[AppPoolname]_[date].log" file is created in the log directory.
  If the log file exists, then it means that JENNIFER .NET product has been successfully installed.
• Check if "Jennifer_[AppPoolname]_[agentID]_[date].log" file is created in [installation folder]\log. Open the file with an editor and check if the "App Initialized" record exists.
  If the "App Initialized" record exists, then it means that JENNIFER .NET product is operating successfully.

Is JENNIFER server address set correctly?

You need to run the [instalation folder\utility\IISConfigHelper.exe to see if the items such as "JenniferServer", "UDP Port", "Listen Port" and "LWST Port" are configured correctly.