.Net Agent refuse to attach to IIS process

[Ziv Leibovich]

Hi,

I've installed a new 10.7 SP3 agent on a clean IIS environment.

The Performance Management is working OK but the .Net is not connecting to the IIS process.
I got in the eventlog a line:

.net Runtime version 4.0.30319.0 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: '{5F048FC6-251C-4684-8CCA-76047B02AC98}'. Process ID (decimal): 5448. Message ID: [0x2516].

I tried to configure the .Net version in the Introdcope Agent properties file, with all kinds of option V2,V4, v4.0.30319 but nothing changed.

anyone faced the same issue?
This is a clean system on azure with a single .Net application I want to monitor.

Thanks,

------------------------------
Ziv Leibovich
------------------------------

[Gnanawathy Hareendran]

Hi Ziv, 

Please refer the below KB for regular .Net Agent troubleshooting:
APM - Introscope .NET Agent Troubleshooting and Best Practices

If this a .NET Core environment, APM 10.7 /SP3 Agent is not supported.
 Azure based PaaS is not supported with APM 10.7 Sp3 agent either.

Thanks,
Yanna

[Ziv Leibovich]

Hi,

Thanks,

I'm currently working with APM.10.7 on the backend, can I use more updated agent to monitor .net application, or do I need to install APM 11.1 to do.it?

Ziv

[Haruhiko Davis]

That depends on how you setup your IIS server. Which option was chosen during setup?

------------------------------
Custom Solution Architect
Broadcom
------------------------------