SCOM ACS Collector Troubleshooting Tips

Posted by : at

Category : troubleshooting   guides   operationsManager

A customer of mine was having problems with Audit Collection Services in SCOM 2019 UR3. I figured this information may prove helpful someday to someone. Enjoy!

SQL Queries

Here are some ACS SQL Queries you can utilize:

Verify ACS collector performance

  1. Open Performance Monitor, right click on Start Menu and select run.
    In run box type the following:
  2. Once Opened go to Monitoring Tools Folder, then right click on Performance Monitor and go to Properties:
    Performance Monitor Properties

  3. Select the Data tab:
    Performance Monitor Properties - General

  4. Clear the currently selected counters by removing each counter listed with the Remove Button, then select Add:
    Performance Monitor Properties - Data Sets

  5. Locate the ACS Collector in available counters, select it, and click on the Add button:
    ACS Collector Performance Counter
    This is how it should look when it is added:
    ACS Collector Performance Counter - Added

  6. Click OK to confirm the property settings.

  7. Click on the following button to change the view type, change to Report:
    Change to Report View

  8. View your performance data for ACS:
    ACS Performance Data

Gather Partition Table History

You can run the following tsql query against the OperationsManagerAC

-- Status:
-- 0: active, set by collector
-- 1: inactive, mark for closing during collector startup & indexing, set manually
-- 2: archived, ready for deletion, set from outside the collector
-- 100 - 108: closed, indexing in progress
-- 109: indexing complete
select * from dtpartition order by partitionstarttime

Enable ACS Collector Logging


TraceFlags consists of three groups that are OR’d (added) together. They are Verbosity Level, Component, and Log Output Method. Verbosity Level refers to the number and type of events that are logged to the trace log when trace logging is enabled, while Component can only be used if the Verbosity Level is set to Level Debug and is used to enable/disable logging for various internal components. Log Output Method is used to specify the location that tracing information is written to.

Verbosity Level settings

Value Description
0x00000000 No logging.
0x00000001 Level Error. Logs only errors.
0x00000002 Level Warning. Logs errors and warnings.
0x00000003 Level Informational. Logs errors, warnings, and information.
0x00000004 Level Debug. Logs everything and is very verbose.

Component settings

Value Description
0x00000010 General
0x00000020 Networking
0x00000080 Event tracking

Log Output Method settings

Value Description
0x00020000 Log to debug out
0x00040000 Log to the console, if available (only when running the collector from the command line)
0x00080000 Log to file in `%SystemRoot%\Temp` directory

%SystemRoot% = C:\Windows\

Trace log files are located in the %SystemRoot%\Temp directory. For the Collector, the log files are written to %SystemRoot%\Temp\AdtServer.log and %SystemRoot%\Temp\AdtSrvDll.log. When a log file fills to capacity, the system overwrites the oldest entries with the most recent entries. Log files have a default size of 1 MB and begin to overwrite the oldest entries once they are full.

  1. To enable logging, open RegEdit navigate to the following location:
  2. Create the TraceFlags DWORD (32-bit) Value and set it to Hexadecimal 80003 unless otherwise advised. Trace logging begins immediately; no restart of the Collector is needed. Additionally, Change permission must be granted to %SystemRoot%\Temp for the NetworkService account.


    For example, to log errors, warnings, and information messages to a file change the traceflags registry value to 0x00080003. This is a combination of 0x00080000 [file] and 0x00000003 [errors +warnings+informational].

  3. To disable logging, delete the TraceFlags value or set it to 0.

Change the scheduled time the SQL Scripts run that are in the ACS Installation Folder

In order for you to change the time the jobs will run the partitioning, grooming and reindexing. You need to edit the dtConfig table and change the “table switch offset in seconds since midnight UTC” value to another time in UTC (Google UTC Converter):

Get current configuration:

select * from dtConfig

Get current SQL UTC time:


Get 10 minutes ahead of current UTC time:


Get seconds from midnight for dtConfig “table switch offset in seconds since midnight UTC” ahead in seconds, in this example we add 10 minutes to the current UTC time:

Declare @d DateTime
Select (DatePart(HOUR, @d) * 3600) + (DatePart(MINUTE, @d) * 60) + DatePart(SECOND, @d)

Update configuration to midnight UTC, which is 7:00 PM (EST):

UPDATE [dbo].[dtConfig]
   SET [Value] = 0 -- Default: 25200 (2:00 AM (EST))
   WHERE [Id] = 4

Be mindful that the scripts are usually run overnight when there is not alot of activity in the ACS Database. So take precautions if changing this when alot of logons/logoffs are happening in your environment.

Set filter for ACS Data

  1. On the ACS server, Go to the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AdtServer\Parameters
  2. Right click the key Parameters, select Permissions
  3. Select the row “Network service”
  4. Click edit
  5. Set “Apply to” as “This key and subkeys”
  6. Select Full control in the column Allow, click OK
  7. Run CMD as an Administrator
  8. Run the below command:
    cd C:\Windows\System32\Security\AdtServer
  9. Run the below command to check current query we use. There should no filter clause to exclude the collected event.
    adtadmin –getquery
  10. Run the following command to add filter for the collected events.
    adtadmin /setquery /query:"SELECT * FROM AdtsEvent WHERE NOT (EventID=528 or EventID=540 or EventID=680)”


    Change the event IDs to the events you don’t want collected. See the below example for a basic filter. Since every environment has its own concerns, please double check which events can be ignored to reduce data collection amount.

    adtadmin /setquery /query:"SELECT * FROM AdtsEvent WHERE NOT (((EventId=528 AND String01='5') OR (EventId=576 AND (String01='SeChangeNotifyPrivilege' OR HeaderDomain='NT Authority')) OR (EventId=538 OR EventId=566 OR EventId=672 OR EventId=680)))"

Install ACS from Command Line

In order to install the ACS Collector from the command line you are required to provide an XML, this an example of the XML that is required:

<?xml version="1.0" encoding="utf-8" ?>



    <!-- Interval (in seconds) between heartbeats. -->

    <!-- Number of failed heart beats before collector
             disconnects the forwarder. -->

    <!-- Time (in seconds) to wait before disconnecting forwarders
             which have not yet sent the initial data packet on a
             new connection. -->

    <!-- The TCP port on which the collector should listen
             for forwarder connections. -->

    <!-- Maximum length of database queue. This value will be
             rounded up to a power of two if necessary. -->

    <!-- Lower bound (in seconds) of randomly chosen backoff
             time sent to agent if the collector is overloaded. -->

    <!-- Upper bound (in seconds) of randomly chosen backoff
             time sent to agent if the collector is overloaded. -->

    <!-- (percentage of max queue length) -->

    <!-- (percentage of max queue length) -->

    <!-- Asset value new agents get assigned.
             -1 means they get the value of their group instead. -->

    <!-- Group ID of the group new agents get assigned to. -->

    <!-- Number of simultaneous database connections to use
             for event insertion. -->

    <!-- Number of simultaneous database connections to use
             for string insertion. -->

    <!-- Minimum asset value required in order to report 
             application log events regarding an agent. -->

    <!-- Minimum asset value required in order to store events
             from an agent. -->

    <!-- (seconds) -->

    <!-- (seconds) -->

    <!-- If running in grooming mode, the collector only kicks
             off a grooming cycle if the database queue has at most
             MaxPurgingQueue entries. -->

    <!-- 0 = Event timestamps will be reported in UTC.
         1 = Event timestamps will be reported in local time. -->

    <!-- Size (in bytes) of memory to use for caching principal data. -->

    <!-- Size (in bytes) of memory to use for caching string data. -->

    <!-- Time, in seconds, to backoff unwanted agents -->

    <!-- Maximum time (in minutes) a connection can exist before it
             gets disconnected for rekeying purposes. -->

    <!-- -->

    <!-- Time, in seconds, before a new connection gets
             disconnected if the client doesn't send any data -->

    <!-- Time, in seconds, before a connection attempt times out -->

    <!-- Interval (in seconds) between recalculation of queue
             statistics. -->

    <!-- Name of ODBC data source -->

    <!-- 0 = SQL Server runs on a different machine
         1 = SQL Server runs on collector machine -->

    <!-- Name of machine running SQL Server -->

    <!-- Name of SQL Server instance to use. Usually blank. -->

    <!-- Name of collector database -->

    <!-- 0 = Specified data and log directories will be used.
         1 = SQL Server's data and log directories will be used. -->

    <!-- Path (on DB server) where data file should be created
             Necessary only if UseDefaultPaths is set to 0 -->

    <!-- Initial data file size in MB -->

    <!-- Maximum data file size in MB, 0 means unlimited -->

    <!-- File growth amount in MB -->

    <!-- Path (on DB server) where log file should be created.
             Necessary only if UseDefaultPaths is set to 0 -->

    <!-- Initial log file size in MB -->

    <!-- Maximum log file size in MB, 0 means unlimited -->

    <!-- File growth amount in MB -->

    <!-- (hours) time to keep events -->

    <!-- Number of partitions to use -->

    <!-- Time when partition switching should occur.
             Expressed in seconds since midnight in UTC -->

    <!-- Type of authentication collector should use
             when connecting to the database:
             0 = Use SQL authentication (not recommended)
             1 = Use Windows authentication (recommended) -->

   <!-- only necessary when using SQL authentication -->

    <!-- only necessary when using SQL authentication -->



Page Views

Share on:
About Blake Drumm
Blake Drumm

I like to collaborate and work on projects. My skills with Powershell allow me to quickly develop automated solutions to suite my customers, and my own needs.

Email : [email protected]

Website :

About Blake Drumm

This is the personal technical blog for Blake Drumm. Currently primarily focused towards Microsoft System Center Enterprise Management Products. I am an Microsoft Support Engineer on the System Center North America Support Team. I am new to blogging. July 6th, 2021 marks my first day as a Microsoft FTE converting from a contractor. I had been working as a contractor since January 2020. Continue to check back for new posts or tips. I like to continually update this page as time permits.

Follow @blakedrumm
Useful Links