Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Access Rights Manager (ARM) formerly 8MAN > ARM - Knowledgebase Articles > FS Logga file access report does not generate data

FS Logga file access report does not generate data

Updated Jan 9, 2019


This article provides details about the issue in which a user runs a file access report on the FS Logga server, but the generated report does not include any results from the query. 



On the file server on which FS Logga is installed and licensed, the report is queried to provide results of file access over a specified period of time on a share server. No data is returned, although the files queried have been accessed during the defined period.


  • Access Rights Manager


  • Filter Driver is not running
  • Root of the share is configured in reporting
  • Collector service is not installed with Admin privileges


Make sure you are not scanning or generating reports on the Root share, instead generate reports for the folder monitored under root.

  1. Confirm the collector is installed(using Run as administrator if have UAC/Impersonation polices in place) on the file server and running.


  2. Verify whether FS Logga is switched on and if access to the resource on the server is monitored.


    1. If FS Logga is installed and configured correctly, check if the minitrc driver is running on the file server by executing the following command on the file server(only applies to Windows FS):
      sc query minitrc


    2. If FS Logga is not installed, start the service by executing the following command on the file server:
      sc start minitrc
  3. Confirm if an instance is assigned to minitrc by querying the filter driver Management Console on the command line:
  4. To see the name of the instance, run the command:
    fltmc instances


  5. If the number of instances is 0, restart the ARM service on the file server.
    • If all tests fail, update the Microsoft Visual C++ 2015 Redistributable (x64) pack.


      • You can confirm the current version of Visual C++ on the Microsoft website.

        Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

      • If the latest version of Visual C++ is already installed, repair the installation.
    1. Run the setup as an administrator on the file server on which FS Logga is installed.
    2. Select Repair.


    3. If generated reports still do not include any results, open the SQL database and check _8ManDB
    4. Verify the table tracer.events_NameofFileservers exists
    5. Once you have repaired Visual C++, restart the ARM service on the server.
  6. Once file access has taken place on the resource, they are generated in the report.
  7. Confirm there is an entry on your file server under _8ManDB such as: Tracer.events_yourserverName




Last modified