You are attempting to login to a file already opened in Single User mode (Error -6073)

Legacy KB ID: 3949

Question

Why do I get the error: ‘You are attempting to login to a file already opened in SU mode’ when opening a file (Error -6073)?

Answer

One of the following steps will resolve the issue.  Start with the first and continue until the issue is resolved:

  1. Switch the file to multi-user mode;
  2. Delete the *.nd file;
  3. give QBDataServiceUserXX Full Control permissions to the folder containing the company file;
  4. Verify that the QuickBooks/Accounts Business network is properly setup.

 

The Issue

The error message suggests that the file is already opened in single user mode.  Other users will not be able to log onto the file until the file is switched to multi-user mode.

There are other factors that may produce this error message:

·         The QBDataServiceUserXX (where XX relates to the version number:  2014 = 23; 2013 = 22; 2008/09=17) does not have sufficient permissions to the folder containing the company file.

·         The *.nd file is damaged.

·         Multi-user hosting is not properly setup.

 

Solutions

Users should start with Solution 1.  If the problem is not resolved continue with subsequent solutions until the problem is resolved.

 

Solution 1:  Switch the file to multi-user mode

1.    Ask the user who has the company file open to switch to multi-user mode:

File > Switch to multi-user mode.

  1. If you get a message box titled:  Multi-User hosting setup required; click Yes to continue. 

Open your company file.

 

Solution 2: delete the *.nd file

  1. Close all Accounts Business applications. 
  2. If the company file resides on a File Server that does not have an Accounts Business application installed (Company File Server only), go the File Server and:
    1. Stop the QuickBooks Database Server Manager:

                                          i.    Right-click the QuickBooks Database Server Manager icon in the System Tray and select Open

                                         ii.    Click on Exit to close the Database Server Manager.

    1. in Windows Explorer go to the company file folder
    2. Find the file and delete it (if there is a file
      delete it too)
    3. Start the QuickBooks Database Server Manager and scan folders for QuickBooks datafiles
    4. Minimize the QuickBooks Database Server Manager
    5. Open the company file on one workstation and switch the file to multi-user mode.  Then open the same company file on a second workstation.
  1. If the company file resides on a PC that also has the Accounts Business application installed:
    1. in Windows Explorer go to the company file folder
    2. Find the file
      companyfile.qbw.nd
      and delete it (if there is a file
      delete it too)
    3. Open your company file and switch the file to multi-user mode.  Then open the same company file on a second workstation.

 

Solution 3:  give QBDataServiceUserXX Full Control permissions to the folder containing the company file.

  1. Go to the PC on which the company file resides;
  2. In Windows Explorer, browse to the folder containing the company file folder (do not use any mapped network drives)
  3. Right click on the company file folder > Properties > Security
  4. In the Group or user names box, highlight QBDataServiceUserXX. 
  5. In the lower box Permissions for QBDataServiceUserXX, confirm that Full Control is ticked.  If it is not, then:
    1. Windows XP & Vista:  tick the box for Full Control in the Allow column
    2. Windows 7&8:  click on the Edit box, confirm that QBDataServiceUserXX is highlighted, then under Permissions for QBDataServiceUserXX :  tick the box for Full Control in the Allow column.  Then click OK.

Click OK to close the Properties box

Open your company file and switch it to multi-user mode.

 

Solution 4:  Verify that the Accounts Business network is properly setup

Click the link below for kb404: Error (-6177, 0) or ( -6000, -83) for detailed guidelines.  Then open your company file.

https://kb.reckon.com.au/issue_view.asp?ID=404

 

How did we do?

Error (-6000,-816) Unable to open database

Related Articles

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)