Let us help you tackle any Software issues and optimize your accounting workflow. 

Sage 50 crashes when saving transactions

Sage 50 Waiting to Open Queue.dta Error: Effective Solutions

The Sage 50 Waiting to Open Queue.dta Error can stop the accounting software from opening a company, leave it stuck on the startup screen, or display a message saying that the queue file is currently in use. You may see an alert such as “Queue.dta is in use. Please wait until this file is available,” even when nobody appears to be working in the company.

This problem is commonly associated with the Sage Data Service being unable to access company data, a queue file that remains locked, or a connection issue in a network or Remote Data Access environment. The correct fix depends on whether you use a locally stored company, a shared network company, or Sage Remote Data Access (previously called Sage Drive).

It is important to identify your setup before deleting Queue.dta or resetting Sage services. The troubleshooting process for a standard network company is different from the process for Remote Data Access. This guide explains the likely causes, how to refresh the queue file safely, and what to check if Sage 50 continues waiting to open the company.

What Is the Sage 50 Queue.dta Error?

Queue.dta is a file used by Sage 50 Accounts to manage access and activity involving company data. When Sage cannot access this file correctly, it may wait for the file to become available instead of opening the company.

The error can appear in several forms:

  • Waiting to open Queue.dta.
  • Queue.dta is in use. Please wait until this file is available.
  • A Sage ID user is currently processing at another site.
  • Sage 50 hangs or closes on the startup screen.
  • The company opens at the main location but not at a remote location.

The error is particularly relevant to Sage 50 Accounts (UK). Sage 50 U.S. Edition uses a different company-data and database architecture, so the UK Queue.dta instructions should not automatically be applied to a U.S. installation.

A. Common causes of the Queue.dta error:

Possible causeWhat happens
Queue.dta remains lockedSage cannot obtain access to the queue file
Sage Data Service cannot access company dataThe service cannot read or manage the required company files
Another Sage process is still runningA previous session or background process may retain access
Incorrect folder permissionsThe service account cannot access the company-data folder
Company data is in a restricted folderWindows folder restrictions can prevent the service from accessing the data
Sage versions are inconsistentDifferent software builds can create problems in a shared or remote setup
Remote Data Access connection problemThe main and remote sites may not be communicating correctly
Unstable internet connectionRemote company access may be interrupted or delayed

B. Difference between a network Queue.dta error and a Remote Data Access error

It is useful to establish which setup you are using before attempting a fix.

Standard network company: The company data is stored on a server or host computer and accessed by other computers over the local network. The Sage Data Service, file permissions, and company-data location are important checks.

Remote Data Access (RDA): The company is accessed across different locations through Sage’s remote access service. The main site, remote computers, Sage services, software versions, and connection status all need to be considered.

Sage Drive is the older name associated with this remote-access functionality. If you see older instructions referring to Sage Drive, check whether they apply to your installed version before following them.

How to Fix Sage 50 Waiting to Open Queue.dta Error?

Before starting, ask all users to close Sage 50 and exit the affected company. If possible, create a backup of the company data and preserve the original files. Do not delete Queue.dta while other users or Sage services may still be accessing the company.

1. Close Sage 50 and remove the locked Queue.dta file

For a standard Sage 50 Accounts company that does not use Remote Data Access, Sage’s troubleshooting guidance recommends deleting the Queue.dta file when it is responsible for the file-in-use message. First, make sure the file is no longer being used.

  1. Ask all users to close Sage 50.
  2. Close Sage 50 on the computer hosting the company data.
  3. Open Task Manager by pressing Ctrl + Shift + Esc.
  4. Check that no active Sage session is still using the company.
  5. Open File Explorer and browse to the folder containing the affected company data.
  6. Locate Queue.dta.
  7. Delete the file if it is present and no Sage process is using it.
  8. Reopen Sage 50 and test the company.

If Windows reports that the file is still in use, do not force-delete it. Check for remaining Sage sessions or restart the computer hosting the data after confirming that all users have exited.

Important: Delete only the identified Queue.dta file in the correct company-data location. Do not delete other .dta files or company database files. If you use Remote Data Access, follow the RDA-specific process later in this guide instead of treating the issue as an ordinary network file lock.

2. Restart the Sage Data Service

The Sage Data Service needs appropriate access to the company files. If the service is stopped or unable to access the data, Sage may remain stuck while waiting for Queue.dta.

  1. Close Sage 50 on all computers.
  2. Press Windows + R.
  3. Type services.msc and press Enter.
  4. Find the Sage Data Service associated with your installed Sage Accounts version.
  5. Check its status.
  6. If it is stopped, right-click it and select Start.
  7. If it is running but unresponsive, use Restart if available.
  8. Wait for the service to finish starting.
  9. Reopen Sage 50 and test the company.

For Sage Accounts version 31 and above, Sage provides a Data Service Manager that makes the service-management process easier. Use the tool appropriate to your release rather than relying on service names from older versions. If the service fails to start, record the Windows error message. Repeatedly restarting it will not resolve an underlying permissions or installation problem.

3. Check whether the company data is stored in a restricted folder

Sage’s troubleshooting guidance identifies certain folder locations that can prevent the Sage Data Service from accessing company data. These include locations such as the Windows directory, Program Files, and the root of the C: drive. For a network installation, perform this check on the computer that stores the company data.

  1. Press Windows + E to open File Explorer.
  2. Browse to C:\ProgramData\Sage\Accounts\xxxx, replacing xxxx with the relevant software-version folder.
  3. Locate the COMPANY file.
  4. Open it with Notepad.
  5. Review the company-data paths listed in the file.
  6. Check whether any path begins with one of these locations:
    • C:\
    • C:\Windows
    • C:\Program Files
    • C:\Program Files (x86)
    • C:\Dev
  7. If a company-data path uses one of these restricted locations, follow Sage’s instructions to move the data to an appropriate folder under C:\ProgramData.

Do not move company data while users are working in Sage 50. Close the software first, preserve a backup, and make sure the company configuration points to the correct location after the move.

4. Verify Windows permissions on the company-data folder

If Queue.dta has been refreshed and the Sage Data Service is running, incorrect Windows permissions may still prevent the service from accessing the company files.

Sage’s guidance for affected Sage Accounts installations describes checking permissions on the relevant COMPANY.xxx folder. This process involves reviewing the folder’s advanced security settings and ensuring that the required system and authenticated-user permissions are present. Because changing advanced Windows permissions can affect data security and access, involve your IT administrator if you are not familiar with Windows permissions. Before making changes:

  1. Confirm the exact company-data folder.
  2. Record the folder’s existing security settings.
  3. Make a separate backup of the company data.
  4. Review the permissions against Sage’s instructions for your version.
  5. Apply only the required permissions to the correct company folder.
  6. Test Sage 50 after the changes.

Do not grant Full Control to everyone or apply broad permissions across an entire drive. The required access should be limited to the appropriate accounts and folders.

5. Update all computers to the same Sage Accounts build

In a network or Remote Data Access setup, inconsistent software builds can contribute to access problems.

  1. Check the installed Sage Accounts version on the main computer.
  2. Check the version and build on each affected workstation.
  3. Open Sage and select Help, then Check for updates, if the software opens.
  4. Install the appropriate available update.
  5. Make sure the main and remote computers are running compatible, matching builds.
  6. Restart the computers if the update requires it.
  7. Test the company connection again.

Do not install an update intended for a different Sage release. Confirm the version and edition before downloading or installing software.

6. Reset Sage services and refresh Queue.dta for Remote Data Access

If you use Remote Data Access and the message identifies a particular computer or site, start troubleshooting on the computer named in the message. Sage’s RDA guidance recommends checking software compatibility, resetting Sage services on the computer holding the data, and refreshing Queue.dta on that computer.

  1. Confirm which computer is the main site and which computers are affected.
  2. Make sure you can access the main site and the affected remote sites.
  3. Confirm that all computers are running the appropriate matching Sage Accounts build.
  4. Close Sage 50 on the affected computers.
  5. On the computer holding the company data, reset the Sage services using the procedure for your version.
  6. Refresh the Queue.dta file on the computer storing the data, following Sage’s RDA instructions.
  7. If the issue continues, repeat the service-reset process on the affected remote computers as directed by Sage.
  8. Reopen Sage 50 and test the remote connection.

For older Sage Drive instructions, Sage also recommends restarting the computers holding the data at the relevant sites when possible. Do not mix older process names or service-reset instructions with newer releases without checking the version-specific guidance.

7. Disconnect and reconnect Remote Data Access if the problem persists

If the queue error continues after checking software versions, restarting Sage services, and refreshing the queue file, the remote connection may need to be reset. Sage’s Remote Data Access troubleshooting process includes disconnecting from RDA and downloading the data again. If that does not resolve the issue, a full RDA reset and reconnection may be required. Before proceeding:

  • Confirm that the main-site company data is available and backed up.
  • Make sure you know which copy contains the latest accounting information.
  • Coordinate the process with all users.
  • Follow the supported RDA procedure for your Sage version.

Disconnect the affected site from Remote Data Access and follow Sage’s instructions to download the company data again. If the issue continues, use the supported reset and reconnection procedure. Do not remove the company from Remote Data Access or re-upload it as an initial troubleshooting step. Re-uploading data can affect the remote setup and should be considered only after the simpler checks have failed.

How to Fix Sage 50 Queue.dta Errors on a Network?

When multiple computers access the same company, the issue may be related to the host computer rather than the workstation displaying the error.

Use these checks to narrow down the problem:

  • Test the company on the host computer: If it opens successfully on the host but not on a workstation, investigate network access, permissions, and software versions.
  • Check other users’ sessions: Confirm that everyone has closed Sage 50 before refreshing the queue file or restarting services.
  • Verify the shared data location: Make sure all workstations are opening the same company stored on the host.
  • Check the Sage Data Service: Confirm that the service is running on the computer holding the company data.
  • Review security settings: Check whether firewall rules or Windows permissions are preventing access.
  • Coordinate service restarts: Restart services only after users have exited the company to avoid interrupting active accounting work.

If the company fails to open on the host computer as well, focus on the Sage Data Service, company-data folder permissions, and the queue file itself before investigating individual workstations.

How to Prevent Sage 50 Queue.dta Errors?

Although a Queue.dta problem can occur unexpectedly, good maintenance practices can reduce repeated access and file-lock issues.

  1. Keep the Sage Data Service running: The Sage Data Service needs to operate correctly to access shared company information. Monitor the service if Sage regularly hangs during startup or displays file-in-use messages. If the service stops repeatedly, investigate the underlying Windows service or permissions problem instead of simply restarting it each time.
  2. Make regular company-data backups: Create regular backups and store additional copies separately from the active company-data folder. Always create a fresh backup before changing permissions, moving company data, refreshing queue files, or resetting Remote Data Access.
  3. Avoid interrupting active Sage sessions: Ask users to close Sage 50 properly before restarting the server or performing maintenance. Avoid shutting down the host while other users are working in the company.
  4. Keep network computers updated: Use compatible Sage Accounts versions and builds across the main computer and workstations. This is particularly important when using Remote Data Access.
  5. Store company data in an appropriate folder: Avoid placing company data in restricted Windows locations. Follow Sage’s recommended folder-location guidance so the Data Service can access the files correctly.
  6. Maintain a stable remote connection: For Remote Data Access, maintain a reliable internet connection at the main and remote sites. Check the service status and connection requirements if remote users regularly experience delays or access errors.

Conclusion

The Sage 50 Waiting to Open Queue.dta Error usually indicates that Sage Accounts cannot access its queue file or the underlying company data. A locked file, stopped Sage Data Service, incorrect folder permissions, restricted data location, or Remote Data Access problem can prevent the company from opening.

Start by identifying whether you use a standard network company or Remote Data Access. For a standard company, close all Sage sessions, refresh the correct Queue.dta file, and check the Data Service. For RDA, verify the software builds, reset the relevant Sage services, and follow the supported queue-refresh or reconnection procedure.

Always protect your company data before changing files, permissions, or remote-access settings. Following the correct procedure for your Sage Accounts version can resolve the queue problem while reducing the risk of disrupting other users or damaging important accounting records.

FAQs of Sage 50 Waiting to Open Queue.dta Error:

What does the Sage 50 Waiting to Open Queue.dta error mean?

It means Sage 50 Accounts is unable to access the Queue.dta file as expected. The file may be locked, another process may be using it, or the Sage Data Service may not have the necessary access to the company data.

How do I fix the Queue.dta is in use error?

For a standard network company, close Sage 50 on all computers, confirm that no active sessions are using the company, and delete the identified Queue.dta file from the company-data folder. Restart the Sage Data Service if necessary and reopen the company. For Remote Data Access, use the separate RDA troubleshooting procedure.

Is it safe to delete the Queue.dta file?

Deleting Queue.dta is a documented troubleshooting step for this Sage Accounts error when the file is no longer being used. Close all Sage sessions first and confirm the correct company-data location. Do not delete other .dta files or company database files.

Why does Sage 50 get stuck on Waiting to Open Queue.dta?

The Sage Data Service may be unable to access the company data, the queue file may remain locked, or Windows permissions may prevent access. Network connectivity and Remote Data Access problems can also cause the message.

How do I fix the Queue.dta error when using Remote Data Access?

Check that all relevant computers use compatible Sage Accounts builds. Identify the computer named in the error, reset the Sage services on the computer holding the data, and refresh Queue.dta according to Sage’s RDA instructions. If the issue continues, follow the supported disconnect, redownload, or RDA reset procedure.

Why does Queue.dta work on one computer but not another?

The affected computer may be using a different company-data path, an incompatible software build, or incorrect network permissions. Compare its Sage configuration and access to the host with a computer that opens the company successfully.

What should I do if deleting Queue.dta does not resolve the error?

Check whether the Sage Data Service can access the company-data folder. Review the folder location and Windows permissions, and confirm that no Sage processes are holding the company open. If you use Remote Data Access, troubleshoot the remote connection separately. Contact Sage Support if the problem continues.

Related Articles