Skip to main content

Attaché: Error: 'The <NAME> company is currently being accessed by someone else' when running an archive

Updated over 3 months ago

Error: 'The <NAME> company is currently being accessed by someone else. Attaché Archive can't start until the user exits' running an archive, but no one else is logged in.

Attaché Archive cannot create a backup file if anyone else is logged into the company. Make sure all users are logged out and then run Archive. If you are not sure how to check if all users are logged out refer to this article: Confirm users currently logged into Attaché.

If you are certain no other users are logged into the company and the error message (or a similar one) is still displayed, try the following suggestions below. You may need your system administrator to assist.


​Archive another company

Try archiving another company to confirm that it works. Then retry archiving the problem company. If Archive still doesn't run, see the solutions below.


Users blocked from accessing the company

You may have been blocked from accessing this company. To unblock access, see Error: 'Access to this company has been blocked by the user named {Username}'.


Check again that all users are logged out

If users still show as logged in, then restart the Attache Database Server service. See: How do I restart/check the Attaché services are running (API & Database).


Check for external programs accessing the Attaché database

Run the following checks to look for other programs connected to the Attaché database:

  • An MS-Query or Excel query with ODBC connection to the Attaché database is open.

  • An ODBC connection has been terminated. (In an RDS environment, this can be checked on the server, but in a client-server environment, the session will have to be checked on a per workstation basis.

  • A Third-party application services are stopping the archive process (e.g. Web Ninja, VSS, ClearView, Powerlink).


A user terminated their Attaché connection incorrectly

The user was logged out or terminated their connection incorrectly, resulting in the session remaining open. On the Attaché server, check Computer Management, Shared Folders, Open Files for files left open in Attaché.


Attaché has an incorrect drive mapping

Attaché has been installed to a UNC path or shows a UNC path in the Program Directory field in Tools, Company, System, System Status. In this area, the Program Drive field value currently displays as the @ symbol. To resolve this, see: Setting up a mapped network drive for Attaché Workstation.

Once you have set up a mapped drive, change the properties for the Attaché desktop icon to point at the correct mapped drive. See: How to update the Attaché desktop icon to point to a mapped drive.

Did this answer your question?