The first step would be to verify that you have full permissions to the message queue with the account you are executing the command as.

This can be done by going to Computer Management > Services and Applications > Message Queuing > Private Queues.

You should see 5 fnms... queues. You can verify if your account has permissions on these queues by right-clicking and selecting properties and then checking the security tab for what groups or users have permissions.

If your account does not have permissions to send messages to the queue then you will not be able to fail those tasks.

Outside of that you should check the compliance reader logs to verify why your tasks are getting hung or stalled.

Hi, you can find more logging information from the following BatchProcessor, BatchProcessScheduler, and BatchProcessTask logs as well found at:

%ProgramData%\Flexera Software\Compliance\Logging\BatchProcessScheduler

For single server implementation (Application/Batch/Inventory server) - The hostname should work by itself

For multi-server implementation (Separate Application, Batch, and Inventory Server) - The hostname should still be less than 15 characters but you also need the domain qualifier e.g. myhostname.mydomain.org

I hope that helps

To get rid of all existing of all pending tasks in the batch processing queue very quickly, you can delete them from the [BatchProcessExecution] table in the database.

As suggested by @dbeckner , I would recommend checking that the queues are configured correctly on your FNMS Batch Processing Server. To fix any issues, with the processing queues, you can re-run the FNMS PowerShell configuration scripts.

After submitting a new reconciliation job - for example by triggering the 'Inventory import and license reconcile' task from Windows Task Scheduler manually - you should see that:

• A new task is created in the processing queue, and 
• A new LOG file is created in the ''\ProgramData\Flexera Software\Compliance\Logging\ComplianceReader' folder.