---
title: No data and registry key permission issues
source: https://docs.newrelic.com/docs/apm/agents/net-agent/troubleshooting/no-data-registry-key-permission-issues
---

## Problem

After generating traffic for your .NET app and waiting five minutes, data still does not appear in the New Relic UI.

## Solution

> #### ⚠️ IMPORTANT
>
> Check with your system administrator before changing permissions.

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

    ```
    HKLM\SOFTWARE\New Relic\.NET Agent\
    ```
2.  Grant all users on the system access to this registry key, or allow only the app pool identity to access the key.

    **To grant the Everyone user access to the registry key:**

    1.  As Admin, open the Windows registry.
    2.  Select **Computer > HKEY_LOCAL_MACHINE > Software > New Relic**. Right-click **.NET Agent**, then select **Permissions**.
    3.  If you do not see an **Everyone** user in the **Group or user names** list, create the user: Select **Add**. Then, from **Select Users or Groups**: 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.

    **To 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
        ```
    2.  As admin, open the Windows registry.
    3.  Select **Computer > HKEY_LOCAL_MACHINE > Software > New Relic**. Right-click **.NET Agent**, then select **Permissions**.
    4.  From the **Permissions for .NET Agent** dialog, select **Add**. Then, from **Select Users or Groups**: 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.
3.  From the command line, perform an **IISRESET**.
4.  If updating permissions does not resolve the problem, follow the .NET agent's troubleshooting procedures for [missing data](https://docs.newrelic.com/docs/agents/net-agent/troubleshooting/no-data-appears-net).

> #### 💡 TIP
>
> To prevent this problem from happening with future installs, uninstall WSM 3.3.5.0. If you do not want to make changes to your registry, uninstall WSM and .NET, then reinstall the latest versions.

## Cause

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.
```