cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

NET (Agent, Installation)

.NET Runtime version 4.0.30319.0 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: 'AppDynamics.AgentProfiler'. Process ID (decimal): 363548.

SOLVED
Neha.Dev
Producer

.NET Runtime version 4.0.30319.0 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: 'AppDynamics.AgentProfiler'. Process ID (decimal): 363548.

We have a scheduled task running a .bat file. The task successfully copies the file from source server to local folder.

 

Part two of the task invokes our Reflections FTP client software and sends single file via SFTP to the final destination which is failing. We are seeing the following error messages in our Application Event Logs and the task hangs in the running state.

.NET Runtime version 4.0.30319.0 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: 'AppDynamics.AgentProfiler'. Process ID (decimal): 363548. Message ID: [0x2516].

 

Please let me know, how to fix this issue

Tags (2)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
.NET Runtime version 4.0.30319.0 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: 'AppDynamics.AgentProfiler'. Process ID (decimal): 363548.
1 REPLY 1
Ryan.Paredez
Community Manager

Hi @Neha.Dev,

 

I found this info:

 

This event log message is written by the windows .NET Runtime, not by the .NET Agent. It will write for each of the new running processes either it is .NET Process or a Non-.NET Process. If Profiler is able to load into the process level then it will write a success message else it will write as shared message details.
As per the message, AppDynamics Profiler dll is not loaded into the Process ID -> [Your ID would be here]


Thanks,
Ryan, AppDynamics Community Manager



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.