After generating traffic for your .NET app and waiting five minutes, data still does not appear in the New Relic UI.
Check with your system administrator before changing permissions.
Ensure the app pool identity has
readaccess to the New Relic registry key located at:HKLM\SOFTWARE\New Relic\.NET Agent\
Grant all users on the system access to this registry key, or allow only the app pool identity to access the key.
From the command line, perform an IISRESET.
If updating permissions does not resolve the problem, follow the .NET agent's troubleshooting procedures for missing data.
To prevent this problem from happening with future installs, uninstall WSM 18.104.22.168. If you do not want to make changes to your registry, uninstall WSM and .NET, then reinstall the latest versions.
A common reason why data does not appear is because the New Relic .NET agent cannot access its registry keys. You may see registry permission errors in your profiler logs at:
%ALLUSERSPROFILE%\New Relic\.NET Agent\Logs\
For example, you may see:
[Info] ... Logger initialized[Error] ... Unable to find New Relic Home directory in registry or environment.[Error] ... An exception was thrown while initializing the profiler.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.