Log API - MSMQ Queue Access Denied
If you encounter an "MSMQ Queue access denied" error when working with the Nodinite Log API, this guide will help you quickly restore access and ensure secure, reliable message processing.
✅ Step-by-step solution to restore MSMQ queue permissions
✅ Ensures secure and reliable message processing
✅ Prevents downtime and access issues for integration experts
This issue often occurs if the .NET Service removes the "Everyone" group from the permissions on a private queue. As a result, you may be unable to change permissions for a queue (for example, im.services.logapiservice/logapiserviceoneway.svc). When you click Apply or OK, you receive an access denied message.
Follow these steps to resolve the problem and restore proper access:
- Stop the MSMQ Service.
- Open the folder:
C:\WINDOWS\system32\msmq\storage\lqs - Find the file that describes your problem queue (e.g.,
incommingQueue). - Using Notepad, open the LQS file for another private queue that has correct security permissions. If you don't have another private queue, create one.
- Locate the line in the file that begins with
Security=.... - Copy the entire Security=... line (be careful with word wrap; this line is usually very long).
- Open the LQS file for your problem queue in your text editor.
- Overwrite the Security=... line in this file with the one you copied.
- Save the modified LQS file.
- Start the MSMQ service.
Your problem queue should now have the same permissions as the working queue, restoring access and resolving the error.
Next Step
- Learn more about Log API troubleshooting
- Explore MSMQ integration best practices