How to Fix Sage 50 Queue.dta is in use

Business entrepreneurs use Sage 50 accounting software for handling their finances and accounts with ease which helps them grow their business. Sage 50 encounters a few errors while opening the software one of them is “Queue.dta is in use” and the second is “An error has occurred in the script on this page”. In this article will discuss about the “Sage 50 Queue.dta is in Use” error.

The exact error is shown…

Queue.dta is in use, Please wait until this file is available

Causes for Queue.dta is in Use while Opening Sage 50

The cause for Sage 50 Accounts Queue.dta is in use is because the Sage Data Service has restricted access to the data file or the data is entered into third-party sites.

The Following Sites are:

• C:/
• C:/ Windows
• C:/ Program Files
• C:/ Program Files (x86)
• C:/ Dev

Read More: Fix Sage Data Service Unavailable

Steps to Fix Sage 50 Queue.dta is in Use

To resolve the “Queue.dta is in use” error in Sage 50 Accounts, delete the Queue.dta file. Use the Sage Data Service Manager for easier processing.

Solution 1: The Data Should Not be Placed in a Blocked Folder

• Internet Explorer should be selected twice and then go to look through: \ProgramData \Sage\Accounts\20xx. 20xx is the second version for 2017 or 2018
• Choose Notepad by clicking on the company file twice
• The user has to confirm if the Company Data Path starts with:
• C:/
• C:/ Windows
• C:/ Program Files
• C:/ Program Files (x86)
• Transfer the data to a folder that is outside the locations given above for example C:/ProgramData
• After Transferring the Data if the user still receives the message “Waiting to open Queuedta” they must reboot the data services: To Reboot the given data perform the given steps:
• Open Run Command by Clicking on Windows+R Keys
• Type Services.msc
• Select Sage 50 Accounts Reboot

Solution 2: The user has to Check the Authorizations on the Machine.xxx folder

For Windows 8 and 10 Users:

• Click on Windows+E Keys then choose C:/ProgramData/Sage/Accounts/20xx. 20xx is the Software Version for example 2017 or 2018
• The user must open the notepad by clicking on the company file twice, write down each directory path, and then close the file.
• If the First directory path is C:/ProgramData/Sage/Accounts/2017/COMPANY.002, right-click to find the COMPANY.002
• Choose Properties then Select Security Tab, from Advance Settings deactivate inheritances and eliminate all inherited authorizations for the project Choose a principle then Select the Object Types
• Mark the Checkbox in the computer then Mark Services Accounts
• Provide an Object name for the system
• Mark the Complete Control and Go to Basic Authorizations.

Read More: Fix Sage 50 Accounts Hangs

Solution 3: Access Your Sage Accounts Company File on Windows 7

Windows 7, follow these steps:

• Press the Windows key + E to open File Explorer
• Browse to the directory C:\ProgramData\Sage\Accounts\xxxx, where xxxx represents your software version (e.g. 2015 or 2016)
• Double-click the company file to open it in Notepad
• Note down the directory path and exit Notepad
• Right-click on the folder that corresponds to the directory path (e.g. C:\ProgramData\Sage\Accounts\2015\COMPANY.001)
• Select Properties, then click on the Security tab
• Click Advanced, then Change Permissions, and then Add
• Click on Object Types and select the Computers and Service Accounts or Services checkboxes
• If these checkboxes are not visible, proceed to the next step
• In the “Enter the object name to select” field, type in “system”, click Check Names, select SYSTEM, and then click OK
• In the Allow column, select the Full Control checkbox, and then click OK, Apply, OK, and OK again
• Repeat steps 4 to 7, replacing “system” with “Authenticated Users”
• Repeat steps 4 to 8 for each directory path that you noted down in step 2.

Conclusion – Fixing “Queue.dta is in Use” in Sage 50 Cloud

The “Queue.dta is in use” error in Sage 50 Cloud usually appears when the system believes the file is locked by another user or process. This can happen if Sage closes unexpectedly, if multiple users try to access payroll at once, or if the file is stuck in read-only mode. To fix it, end background processes, delete the Queue.dta file (with caution), and ensure no other user is accessing the payroll system. For safer troubleshooting and remote help, contact the Bigxperts Sage 50 support team.

Frequently Asked Questions