Splunk AppDynamics

AppDynamics.Profiler failed to register.

CommunityUser
Splunk Employee
Splunk Employee

I am facing the following error while installing .Net agent on windows 2008 r2 server "C:\Program Files\AppDynamics\AppDynamics .NET Agent\AppDynamics.Profiler_x86.dll failed to register." What might be the probable cause and how i am supposed to overcome this issue.Kindly provide your assistance over the same.

Labels (1)
0 Karma

Raunak_Mohanty
Builder

Hi,

  4.4 Agent version installation has additional requirement as documented here

https://docs.appdynamics.com/display/PRO44/Install+the+.NET+Agent#Installthe.NETAgent-PreparetoInsta...

Please install either of the following components and then try installing Agent

Thanks,

Raunak

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Post uninstallation of agent on server, while browsing through the event viewer the following error message arises stating ".NET Runtime version 4.0.30319.34209 - Loading profiler failed.  COR_PROFILER is set to an invalid CLSID: 'AppDynamics.AgentProfiler'.  HRESULT: 0x800401f3.  Process ID (decimal): 3004.  Message ID: [0x2502]." how can i overcome this issue and why is this issue reoccuring in the event viewer.Kindly help for the same.

0 Karma

Raunak_Mohanty
Builder

Everytime a .Net Process comes to life it checks two Environment Variable.
1) COR_ENABLE_PROFILING : If the value of this environment variable is 1, it indicates that  profiling is enabled on the server
2) COR_PROFILER : If profiling is enabled then it checks this value of this env variable to see which profiler its need to load

  NET Runtime version 4.0.30319.0 - Loading profiler failed.  COR_PROFILER is set to an invalid CLSID: 'AppDynamics.AgentProfiler'.  HRESULT: 0x800401f3.  Process ID (decimal): 46608.  Message ID: [0x2502].
.NET Runtime version 2.0.50727.8009 - Failed to CoCreate profiler.


This error indicates that above-mentioned variables still exist but since you have uninstalled Agent, the 'AppDynamics.AgentProfiler'.dll does not exist.

Can you verify if those System level environment variables still exist? If yes can you go ahead and delete them and restart the .Net Application(s).

If this does not help a restart of the server might be necessary which will make sure they are removed from registry cache.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Those variables are present in the registry. Can i infer that those variables are to be deleted from the registry? will it have any impact on the application server or the application  hosted on it ?

0 Karma

Raunak_Mohanty
Builder

Hi,

  We do not create these variables at the Registry level. Please check System Environment variables and verify their presence. If they exist please delete them. Just restarting the server should fix these messages as well.

Thanks,

Raunak

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

System Environment variables stated by your end are not present on the server. In this case what more areas can i troubleshoot?

0 Karma

Raunak_Mohanty
Builder

It means that Windows has cached these variables. Restarting the server should help.

0 Karma
Get Updates on the Splunk Community!

Say goodbye to manually analyzing phishing and malware threats with Splunk Attack ...

In today’s evolving threat landscape, we understand you’re constantly bombarded with phishing and malware ...

AppDynamics is now part of Splunk Ideas

Hello Splunkers, We have exciting news for you! AppDynamics has been added to the Splunk Ideas Portal. Which ...

Advanced Splunk Data Management Strategies

Join us on Wednesday, May 14, 2025, at 11 AM PDT / 2 PM EDT for an exclusive Tech Talk that delves into ...