• EnglishEspañol日本語한국어Português
  • Log inStart now

No data appears (.NET)


After generating traffic for your app and waiting five minutes, none of your .NET agent data appears in the New Relic UI.


The absence of data may occur for several reasons.

Basic solutions

To troubleshoot the most common reasons for missing data, try these solutions as applicable.

Basic solutions


Check app and framework for compatibility with agent

.NET Framework compatibility and requirements


.NET Core compatibility and requirements

Learn about common install issues

See Troubleshooting for .NET Core and Linux or Troubleshooting for Windows

Configure for short-lived .NET process

If you have a short-lived (below 60 seconds) process, it may not report data. For more information, see Monitor short-lived processes.

.NET Core: Check Kestrel requirements.

Make sure you are using a Kestrel app/web server supported by New Relic. Otherwise, you may need to ensure your .NET agent has .NET Framework support enabled.

.NET Core: Check environment variables.

Make sure you have configured all the required environment variables, then restart the agent.

.NET Framework: Restart IIS.

If your app is not receiving traffic, no data will be reported to New Relic. To restart IIS:

  1. From a command line, run IISRESET.
  2. Verify that traffic is being sent to your application.

Run New Relic Diagnostics.

To try to automatically identify the issue, use New Relic Diagnostics.

Check for profiler conflicts.

If you are using Microsoft's System Center Operations Manager (SCOM), follow the troubleshooting procedures to resolve .NET and SCOM conflicts.

Review log files.

If log files exist, open them and review for errors.

Advanced solutions

To remedy more complex issues when no data appears, try these solutions as applicable:

Advanced solutions


.NET Framework: Check Registry permissions.

Check for a registry key permissions error.

.NET Framework: Run Windows Event Viewer.

If applicable:

  1. Run the Windows Event Viewer, and look for application events from the New Relic .NET Profiler.

  2. Search for messages whose source is the New Relic .NET Profiler or New Relic .NET agent.

  3. If there are no New Relic event messages, look for messages from the .NET Runtime.

    For more information, see No data or event log: CoCreate errors.

Get debug logs.

If your logs did not show errors, increase the logging level temporarily to collect debug logs.

Check proxy settings.

Ensure your proxy settings are correct and that your settings include a host attribute.

.NET 8: Make sure runtime diagnostics are enabled

Starting in .NET 8, setting the environment variable DOTNET_EnableDiagnostics=0 (or COMPlus_EnableDiagnostics=0) will disable CLR profiling, making it impossible for the agent to work. This setting is commonly recommended in read-only filesystem deployment scenarios, but only to disable the diagnostic port. See Microsoft's documentation on how to disable specific sub-components of the diagnostic system while leaving profiling enabled.

Get additional help.

If data still does not appear, get support at support.newrelic.com.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.