Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Relic Solution: .NET Core Agent Installation Troubleshooting in Windows


#1

This post assumes that you are sure the .NET Core agent is not creating logs for your application and that you have a Windows OS. If you’re not sure about this, start with the general .NET agent troubleshooting guide.

  • If you are using the .NET Core agent in Linux, see this post instead.

:grey_exclamation: You’re going to need admin privileges on your host to work through this post.

1. Start/Restart your application and check for logs.

2. Check if the .NET Core agent profiler is loaded into the application’s process

  1. Launch Microsoft Process Explorer as an Administrator on your host machine. (Right-click --> “Run as administrator”)
  2. In Process Explorer’s menu bar, select “View” --> “Lower Pane View” --> “DLLs”
  3. Select your application’s process in the upper pane of Process Explorer
  4. Look in the list of DLLs in the lower pane for an assembly called NewRelic.Profiler.dll
  • If you don’t see that DLL in the process, continue
  • If you DO see that DLL in the process, skip down to # 4 (permissions)

3. Check for the required environment variables:

  1. In Process Explorer, right-click your application’s process in the upper pane and select “Properties”.
  2. On the screen that pops up, select the “Environment” tab.
  3. Make sure that all of the required environment variables are present in that window and that their values are correct.
  • If you don’t see all four required environment variables in that list, set your environment variables, restart your app and go back to #1.

  • If you DO see the required environment variables, make sure that they all have the correct values.
    (see link above).

  • If you made any changes to your environment variables, restart your app and go back to #1

4. Check permissions.

  • Make sure that the user your application process is running under has read/write/execute permissions to the directory where the .NET Core agent will write its logs ( CORECLR_NEWRELIC_HOME ), and all of its sub-directories.

  • If you made any changes, restart your app and go back to #1

6. ¯\_(ツ)_/¯

  • If you’ve come this far and still don’t have any logs for your application you either have a compatibility issue or something out-of-the-ordinary is going on.

  • Contact support or ask in these forums with your specific questions.

If you have logs now


Relic Solution: The .NET Agent is Not Reporting: A Troubleshooting Guide
Net core agent doesn't work with IIS and AspNetCoreModule
How to setup New Relic for ASP.NET Core 2.1 website application hosted in Windows & IIS
Can not setup agent with .net core app
APM support for asp.net core app running on http.sys in a Windows Service
2018 Review of Community Awesomeness
#3
  1. The current release of .Net Agent includes both Framework and Core
  2. This information from my support ticket from Oct 10 2019:

Could we please unset the CORECLR_PROFILER_PATH variable? It’s not required on Windows. The only variables that are required for .NET Core on Windows are:
CORECLR_ENABLE_PROFILING=1
CORECLR_PROFILER={36032161-FFC0-4B61-B559-F6C5D41BAE5A}
CORECLR_NEWRELIC_HOME=C:\ProgramData\New Relic\.NET Agent\
NEWRELIC_INSTALL_PATH=C:\Program Files\New Relic\.NET Agent\
Please note that CORECLR_NEWRELIC_HOME is set to ProgramData while NEWRELIC_INSTALL_PATH is set to Program Files.


#4

Thanks for reminding me about this! I made some edits to reflect the changes with the most recent installer.


#5

I’d suggest one more change to this page:

Make sure that the user your application process is running under has read/write/execute permissions to directory where the .NET Core agent was extracted on your system will write its logs ( CORECLR_NEWRELIC_HOME ), and all of its sub-directories.


#6

Thanks @rpresser - I just made that change :smiley: