Error (-6000,-816): "Unable to open database. The file is being used by another user"

Legacy KB ID: 3751

Question

Why do I get the error (-6000,-816): "Unable to open database. The file is being used by another user" when trying to open my company file?  I have checked and there are no other users accessing the file. 

Answer


This error is being experienced by users with Symantec’s Endpoint Protection security system with Auto Protect enabled.  This system is blocking key Reckon Accounts application files that prevent Reckon Accounts opening files. 

 

 

Solution

Users need to consult their Symantec User Guide for instructions on making processes exception to blocking rules. 

Click here for Symantec’s Knowledge Base article on this problem and follow their instructions:

https://www.symantec.com/business/support/index?page=content&id=TECH102742&locale=en_US

 

The Reckon Accounts processes that must be made exceptions are:

·       FileManagement.exe located in C:\Program Files\Intuit\Reckon Accounts 20xx-xx

·       QBCFMonitorService.exe located in C:\Program Files\Common Files\Intuit\Reckon Accounts

·       QBDBMgr.exe located in C:\Program Files\Intuit\Reckon Accounts 20xx

·       QBDBMgrN.exe located in C:\Program Files\Intuit\Reckon Accounts 20xx

·       QBGDSPlugin.exe located in C:\Program Files\Intuit\Reckon Accounts 20xx

·       QBW32.exe located in C:\Program Files\Intuit\Reckon Accounts 20xx

·       QBUpdate.exe located in C:\Program Files\Common Files\Intuit\Reckon Accounts\QBUpdate

·       Port 10184 For Reckon Accounts 2021; 10183 for 2020, ..... 10179 for 2016. 

* Where xx represents your Year Version.

You will not have all these processes, but you must make whichever ones you have an exception.

 

You can get Reckon Accounts to work immediately by switching off Auto Protect, but doing so may leave your PC vulnerable. 

 

Additional Information

For more information on this issue see this site:  https://social.technet.microsoft.com/Forums/en-US/winservergen/thread/0105b25b-a3c6-475c-8afa-73175f27f48f

 

How did we do?

Related Articles

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)