APM .NET Profiler loaded but not sending data

Hello,

I installed the APM .NET Profiler in IIS 10 with .NET Framework 4.8.1.
I followed the instructions from
Profiler Auto instrumentation | APM .NET Agent Reference [1.x] | Elastic

The logs are outputting but when default it only outputs these few lines:

[2024-10-02T08:49:36.790475700-07:00] [WARN ] calltarget_rewriter_callback: skipping method as method replacement found but profiler has not been loaded into app domain. app_domain_id=2364754049408, token=100669846, caller_name=System.Data.SqlClient.SqlCommand.ExecuteReader()
[2024-10-02T08:49:36.892112500-07:00] [WARN ] calltarget_rewriter_callback: skipping method as method replacement found but profiler has not been loaded into app domain. app_domain_id=2364754049408, token=100669816, caller_name=System.Data.SqlClient.SqlCommand.ExecuteScalar()
[2024-10-02T08:49:37.317430200-07:00] [WARN ] calltarget_rewriter_callback: skipping method as method replacement found but profiler has not been loaded into app domain. app_domain_id=2364754049408, token=100669845, caller_name=System.Data.SqlClient.SqlCommand.ExecuteDbDataReader()

Based on the event log:
Theres one log:

.NET Runtime version 4.0.30319.0 - The profiler was loaded successfully. Profiler CLSID: '{FA65FE15-F085-4681-9B20-95E04F6C03CC}'. Process ID (decimal): 13072. Message ID: [0x2507].

wondering if something I am doing wrong? I checked the connectivity from apm server and the iis host and its fine.

Hi, @erikg. What type of ASP.NET app is this? Web Forms, MVC, Web Pages, Web API, WCF, etc.? Do you have multiple applications in the same app pool? Do you see a single log file, or are there profiler_managed logs? You could set the ELASTIC_APM_PROFILER_LOG environment variable to trace to gain more details about the profiler attachment.

We have had something similar reported but have not yet tied down a common scenario or root cause. I'll make another attempt to reproduce this and see if we can come up with anything on our end.

@erikg I've reproduced it, and it looks like a regression. Can you try 1.28.0 for now, which seems to be okay? I'm investigating the breaking change now.

1 Like

Hey @stevejgordon
I used 1.28.0 and it now works!

Thanks for confirming. We're working on fixing the regression in the next release.

1 Like