Showing results for 
Show  only  | Search instead for 
Did you mean: 


The Batch processor relies on Microsoft MSMQ to function.  When FNMS is first configured, the private queues are created in MSMQ and the service account is provided full permission to these queues.  Therefore, if the service account changes at some point after, access to these queues could be lost.  This would then result in the Batch Processor not processing any queued tasks.


In order to check and verify if you are having permission issues with the private queues in MSMQ, logon as the FNMS service account to the FNMS batch server and check under private queue:

Computer Management > Services and Applications > Message Queuing > Private Queues

You should see 4 - 5 queues, if any or all of them show up as a red x symbol with an error message, and then please proceed to the Solution section to resolve the issue.



If access has been lost due to a service account change, then you can logon as the old service account and provide permission to the new account by going to the view above and then right clicking each queue > Properties > Security tab to add the new account with full permission.

If the old account is no longer accessible, there are two possible remedies:

  • The powershell script attached will attempt to give full permission to the FNMS private queues to everyone in the Administrators group.  You can run the script as a local admin and ensure the service account is part of the group (or modify the script to give permission to another group that the service account belongs to).
  • Alternatively, you can turn off the Windows MSMQ feature, reboot the machine, and then re-run the config.ps1 script, which will re-enable feature and assign full permission to service account provided to the script.
Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Apr 13, 2022 09:33 AM
Updated by: