How can we help you today? How can we help you today?

ANTSProfiler_6.0.0.587 - Registry keys not removed properly

I noticed .net errors in the event viewer ".NET Runtime version 2.0.50727.3053 - Failed to CoCreate profiler." after installing the EAP.

There was profile environment settings pointing to redgate in the Environment key under the W3SVC Service. I think this was failing because the build I was using was expired.

Shouldn't these keys only be present when you are attached with the profiler? These keys were still present after an uninstall of the EAP.
aspence
0

Comments

2 comments

Sort by
  • Andrew H
    They should, and the profiler tidies them up when it shuts down a session with IIS. Unfortunately there's no opportunity to do this if the UI suffers an unexpected shutdown, so the keys will remain in this case.

    The message is annoying but harmless (it will show whether the profiler is installed or not: the profiler core will refuse to load when it's not needed).

    It's not easy to decide what the right behaviour is when this has happened: as the condition has arisen due to a failure, it's possible that attempting to clean up later on could compound the problem and obfuscate the cause, which would be bad for a service like IIS.

    We've been considering an alternative approach for IIS 6 and later, which is to set the variables via an ISAPI extension. The main disadvantage for us with this approach is that it won't work with IIS 5 due to the way that ASP.NET is started there, so we'd still need to maintain the old method for as long as we support Windows XP. It also depends on knowledge that IIS initialises things in a certain order, so it would have the potential to mysteriously stop working with a Windows update (or if the extension was disabled somehow)
    Andrew H
    0
  • aspence
    Thanks for the response. Removing the keys stopped the error from being produced.

    The profiling took place on a server that was probably taking 100+ requests per second and held at least a 3 GB Heap. It produced a 2+ GB results file. I had to manually stop IIS as the profiler timed out while our app was flushing buffers etc.

    Here are the logs from the server that the profile took place.

    28 Jan 2010 13:20:45.043 [1] INFO RedGate.Profiler.Logging.LogService - Starting new ANTS Performance Profiler 6 session
    28 Jan 2010 13:20:45.074 [1] INFO RedGate.Profiler.Logging.LogService - Assembly version: 6.0.0.587
    28 Jan 2010 13:20:54.449 [1] WARN RedGate.Profiler.OS.Local.LocalWindowsVersionInspector - Detected Windows version: Windows Server 2003 Standard (5.2 64-bit Server)
    28 Jan 2010 13:20:54.449 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - IIS is supported on installed OS version
    28 Jan 2010 13:20:54.731 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Result of check to see if inetinfo.exe running: True
    28 Jan 2010 13:20:54.731 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Checks confirm that IIS is running.
    28 Jan 2010 13:20:54.731 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Checks confirm that IIS is enabled.
    28 Jan 2010 13:20:54.731 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Successfully detected IIS installation: IIS 6 (Auto-detected)
    28 Jan 2010 13:20:54.731 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Checks confirm that IIS is installed.
    28 Jan 2010 13:22:33.079 [ConfigurableThreadPool thread] ERROR RedGate.Profiler.Engine.Startup.Sessions.IISSession - Error while checking for the IIS service
    RedGate.Profiler.Engine.Startup.IIS.ServiceUtilitiesException: Couldn't start the 'ANTS Performance Profiler 6 Service' service (1053) ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 2240, offset:522
    --- End of inner exception stack trace ---
    at .?.(String )
    at
    aspence
    0

Add comment

Please sign in to leave a comment.