What are the challenges you face when working across database platforms? Take the survey

Info message in Windows eventlog with Memory Profiler 5

twditwdi Posts: 9
When profiling a .NET 4 Windows Service, the next message appear in the Windows Application event log when we start to profile:

Event Type: Information
Event Source: .NET Runtime
Event Category: None
Event ID: 1022
Date: 4-8-2010
Time: 8:59:22
.NET Runtime version 4.0.30319.1 - A profiler designed for an older version of the CLR was loaded because of the environment variable setting below. Older profilers will continue to work in many cases, but if you encounter problems, please consider upgrading the profiler or changing the setting of the environment variable. Please consult the documentation for information on how to use this environment variable, and the risks associated with it. Environment variable setting: ProfAPI_ProfilerCompatibilitySetting=EnableV2Profiler. Profiler CLSID: '{D60F7519-2600-4865-8AC1-C621C9CE41A2}'. Process ID (decimal): 4028. Message ID: [0x2518].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Could this cause problems or something we need to solve?


  • Options
    No, this won't cause any problems. AMP5 pre-dates the release of .NET 4 so it operates in a compatibility mode. .NET 4 just produces a warning message to let you know that this is happening. The main change in .NET 4 that affects the profilers functionality is that the layout of string objects has been changed, so version 5 of the profiler is unable to display their values.

    Version 6 of the profiler has been updated to fully support the new .NET 4 profiling interface.
    Andrew Hunter
    Software Developer
    Red Gate Software Ltd.
Sign In or Register to comment.