Why does the Log Archive Service take so long to stop? (NETIQKB72199)

  • 7772199
  • 08-Apr-2010
  • 04-May-2010


Security Manager 6.x


The purpose of this article is to provide information on what is happening when a stop request is received from the Service Control Manager.


When the Log Archive Service receives a stop request from either the System or the Service Control Manager, there are a number of processes that must complete their work before the service can be stopped. Below is a list of items that must be stopped before the Log Archive service can be stopped.

  • Log Archive Indexers
  • Partition Verification and Compression.
  • Cube Export Uploads to the SQL Reporting Server.

Each one of these process could take up to several minutes to complete their tasks. It's possible for these processes to take longer to stop if there is a resource limitation on the physical server.


  • User sends a stop request using the Services snap-in.

  • Windows send a stop request for physical server shutdown.

Additional Information

Formerly known as NETIQKB72199

Killing the Log Archive Server process in the Task Manager can lead to corrupted indexes, partitions that can't be closed, and incomplete rows in the data tables in the SMCubeDepot on the SQL Reporting Server (SSIS job failures).