You may have encountered an issue where in the process of gathering troubleshooting logs for GFI EventsManager, you notice that the DebugLogs directory increases its disk space usage significantly. This article provides information on how to resolve this issue.
This is a known issue that is related to the following SQL collector error:
Failed to initialize object as reader. This issue occurs when auditing is enabled for SQL Servers 2012 or later. In order to free up some disk space, some SQL Collector logs can be deleted. To prevent this from occurring in the future, please follow the steps below:
- A workaround solution to this problem is to modify the Trace Definitions that the SQL server has, and use those with EventsManager in order to switch to the correct assemblies.
- The default paths for the SQL Server trace definitions are:
- SQL Server 2012 - C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Profiler\TraceDefinitions\
- SQL Server 2014 - C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Profiler\TraceDefinitions\
- SQL Server 2016 - C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Profiler\TraceDefinitions\
- SQL Server 2017 - C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Profiler\TraceDefinitions\
- The assembly needs to be copied over to the EventsManager server, in the following location:
- "C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Profiler\TraceDefinitions\"
- If the steps above do not solve the issue, you can try installing the SQL Server management studio version that matches the SQL Server event source version on GFI EventsManager so that it overrides the incorrect assemblies.
This will prevent the DebugLogs directory from creating unnecessary logs in the future.