Troubleshooting Batch Processing
The following notes may assist in troubleshooting the batch scheduler and batch processor on your batch server.
Examine log files
The batch scheduler and batch processor create log files under %ProgramData%\Flexera Software\Compliance\Logging\BatchProcessScheduler. Tasks go through the batch scheduler first, so you should first investigate BatchProcessScheduler.log. You can then use the ID given to each task to track processing results in BatchProcessor.log.
For a list of the status values that may be logged, and their meaning, see How Batch Scheduling and Processing Works.
Checking the state of batch processing
ShadowHost.exe BatchProcessTaskConsole.exe list-tasks
This
command is equivalent to the following database query (which you could also use within
Microsoft SQL Server Management
Studio):SELECT *FROM BatchProcessExecutionInfo bi
WHERE BatchProcessStatusID IN (1, 2, 3)
ORDER BY bi.StatusOrder, bi.DateOrder
list-tasks
command in debugging, see Killing or Failing Tasks.Checking the database record
You can use Microsoft SQL Server Management Studio to examine the contents of the
BatchProcessExecution
table (for details of the table columns, see FlexNet Manager Suite Schema Reference). There is also a convenient view on this table, called
BatchProcessExecutionInfo
. This can be used to monitor the health of
executing tasks, including those requested by Windows Scheduled Tasks.
Additional troubleshooting
The following topics may also assist with troubleshooting.
FlexNet Manager Suite (On-Premises)
2023 R2