No data and registry key permission issues

Problem

After waiting five minutes, none of your .NET agent data appears in the New Relic UI. A common reason for this is that the agent is unable to access its registry keys.

A common symptom of registry permission issues is errors in your profiler logs (at %ALLUSERSPROFILE%\New Relic\.NET Agent\Logs\). These errors look like:

[Info] ... Logger initialized
[Error] ... Unable to find New Relic Home directory in registry or environment.
[Error] ... An exception was thrown while initializing the profiler

You should try the Solution even if you don't see these profiler log errors.

Solution

Ensure the app pool identity has read access to the New Relic registry key located at:

HKLM\SOFTWARE\New Relic\.NET Agent\

You can grant all users on the system access to this registry key, or allow only the app pool identity to access the key:

Check with your system administrator before changing permissions.

Grant the Everyone user access to the registry key.
  1. As admin, open the Windows registry.
  2. From the left folder tree, select Computer > HKEY_LOCAL_MACHINE > Software > New Relic. Right-click on the .NET Agent and select Permissions.
  3. If you don't see an Everyone user in the Group or user names list, create the user: Select Add. Then, from Select Users or Groups dialog: In the Enter the object name to select field, type Everyone. Select OK.
  4. In the Group or user names list, select Everyone. Then in the Permissions for table, select the Allow checkbox for Read permissions.

  5. From the command line, perform an IISRESET.

To prevent this issue from happening with future installs, uninstall WSM 3.3.5.0 and install WSM 3.3.6.0. If you'd rather not make changes to your registry, uninstall WSM and .NET, then reinstall the latest versions.

Grant individual app pool identities access to the registry key.
  1. Determine your app pool identity, which uses this standard format:

    IIS AppPool\APP_POOL_NAME

    To determine your app pool name, open Internet Information Services (IIS) Manager from the Start menu. Then find your app pool:

    apppool.png

    In this example, the app pool name is Meadows, so the app pool identity is IIS AppPool\Meadows.

  2. As admin, open the Windows registry.

  3. From the left folder tree, select Computer > HKEY_LOCAL_MACHINE > Software > New Relic. Right-click on the .NET Agent and select Permissions.

  4. From the Permissions for .NET Agent dialog, select Add. Then, from the Select Users or Groups dialog: In the Enter the object name to select field, type your app pool identity (for example, IIS AppPool\APP_POOL_NAME). Select Ok.

  5. In the Group or user names list, select your new app pool identity. Then, in the Permissions for table, select the Allow checkbox for Read permissions.

    Screenshot: Granting read permissions for Meadows
    crop-net-registry-key-read-permission.png
  • From the command line, perform an IISRESET.

To prevent this issue from happening with future installs, uninstall WSM 3.3.5.0 and install WSM 3.3.6.0. If you'd rather not make changes to your registry, uninstall WSM and .NET, then reinstall the latest versions.

If updating permissions does not resolve your issue, see No data appears.

For more help

Additional documentation resources include:

  • No data appears (other troubleshooting steps when no data appears in your UI after generating traffic to your app).
  • Profiler conflicts (check that your system does not have multiple profilers in place)

Join the discussion about .NET monitoring in the New Relic Online Technical Community! The Technical Community is a public platform to discuss and troubleshoot your New Relic toolset.

If you need additional help, get support at support.newrelic.com.