Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Netflow Traffic Analyzer (NTA) > ERROR SolarWinds Netflow FastBit Server Utils Periodical Performance Monitor Base - Access to the Registry Key '230' is Denied

ERROR SolarWinds Netflow FastBit Server Utils Periodical Performance Monitor Base - Access to the Registry Key '230' is Denied

Created by Con Finucane, last modified by MindTouch on Jun 23, 2016

Views: 22 Votes: 2 Revisions: 3


This article describes the issue when NTA service stops with the following prompt:

ERROR:<ERROR SolarWinds.Netflow.FastBit.Server.Utils.PeriodicalPerformanceMonitorBase - Access to the registry key '230' is denied. Running the permission checker no permissions applied>


All versions of NTA



This error occurs when running the permission checker and there are no permissions applied. 


To test the Orion permissions using the Orion Permission Checker:

  1. Go to C:\Program Files (x86)\SolarWinds\Orion\ (or whichever directory Orion was installed in).

  2. Run OrionPermissionChecker.exe.

  3. Click Check. 

  4. Click Repair


To manually repair permissions:

  1. Target Directories: (These should be same as AV exclusions)
    Volume:\Program Files (x86)\Common Files\SolarWinds\
    Volume:\Program Files (x86)\Microsoft SQL Server\
    Volume:\Program Files (x86)\SolarWinds\
    Volume:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
    Volume:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files 
    Volume:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files 
    Volume:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
  2. Right-click on each of the target directories and Select Properties.
  3. Click Security.
  4. Check the Group of the user names list. 
    Note: The Principal listed in the Orion Permission Checker should exist in this list, and must have full control. 
  5. If it does not exist:
    1. Click Edit.
    2. Click Add, and enter the Principal name.
    3. Click Check Names, and then click OK.
    4. Select Full control, and then click OK to complete.
  6. Repeat sub-steps A to D for all rows that do not exist in the Orion Permission Checker. 
  7. Repeat but for the following local accounts: Authenticated Users, IUSRS, Network Service
  8. Re-run the Orion Permission Checker to confirm all users have full control.
    Note:  Allow an hour before re-running the Orion Permission Checker. The Group Policy in a domain setting may affect permissions.


Last modified
20:31, 22 Jun 2016