QuickBooks Error -6000 -77

Simple tips to Fix QuickBooks Error 6000-77 When Opening a Company File

Will you be getting this QuickBooks Error 600-77 that commonly occurs when your company file is stored in an improper folder? The first thing you ought to do is restart QuickBooks with an increase of permission. In most cases, the error is resolved following the restart and there is no actual further action needed.


Possible quick ideas to fix this:

  • Close your QB and then right-click the QuickBooks Desktop icon on your desktop and choose Run as Administrator to re-open it.
  • Copy the company files Manually when they saved on an external drive.

Reasons for QuickBooks Error 6000-77 Error

This is a string error of QuickBooks Error codes 6000. A number of the possible causes for qb error 6000 77 might be:

  • Inappropriate folder permission for the folder that keeps the organization file inside.
  • The company file should be on a network or local drive this is certainly situated on an external storage device.
  • The business file will be opened by QuickBooks by referencing a mapped drive
  • QuickBooks running in multi-user mode when communicating the problem.

Note: In most of the cases, the error is solved after restarting the system.

Related Article:
How exactly to fix QuickBooks Error 6000-77?

Some Other Helpful Tips to Solve this error:

  • Reboot the QuickBooks software with an increase of permissions. In a lot of situations, the error is taken away following the software is restarted and no further tasks are required.
  • Run a QuickBooks file doctor. With the capability to repair damaged or corrupted QB files. However, sometimes this utility fails in QuickBooks file recovery and therefore fixing the 6000 77 error message. This might be for the weak and basic underlying technology.
  • Move the organization file to a nearby or network drive if it had been previously stored on an external storage device. Then, try opening the QBW file in QuickBooks if ever the error has gone or it still exists.
  • If QuickBooks Company file references the mapped drive, change ‘settings’ and select ‘right server’. To achieve this, click on ‘Open or Restore’ when you look at the File menu. Following this, select ‘Open a company file’ and then click on ‘Network Place’. Also, click on the ‘entire network’ and choose the server where the company file was stored. Finally, to check on if the solution works, restart the QuickBooks software.

Solution 1: It is possible to fix this utilizing the UNC path as opposed to the mapped drive

  • Right-click the QuickBooks icon on your desktop, press and support the Ctrl key on your keyboard, and choose Run as Administrator. Hold down the Ctrl key unless you have the no enterprise Open window.
  • Note: Holding down the Ctrl key prevents QuickBooks Desktop from auto-opening a business file.
  • From the File menu, select Open or Restore Company > Open a business file > Next.
  • When you look at the left pane, click Network, and navigate to the location of one's company file.
  • Note: If you can’t discover the folder where in actuality the company file is saved, you may want to set folder permissions.
  • Choose the company file and click Open.

Solution 2: Configure your firewall and security software

Solution 3: Re-create the damaged folder by this step

  • Create a new folder in drive C of one's computer.
  • Open that folder where the company old file is saved.
  • Discover the .qbw file. Like- company_file.qbw.
  • Copy the .qbw file.
  • Then open this new folder and paste the file.
  • Set window on Access permission to share with you company files.
  • After that open QB Desktop and open the file from a unique place.

Solution 4: Copy the QuickBooks file on Desktop

Copy files towards the desktop and later open it for the test if you are facing any issue aided by the located area of the company file. Here, there's two desirable things. The first one is your file will open in an innovative new location and thus there clearly was an issue because of the previous location, perhaps it’s damaged or too deep that this file path exceeds system boundaries. If you are not able to open the file from a unique location, it indicates that the file itself is damaged.

  • Go to the folder that holds your business file.
  • Now, find the file with .QBW extension and right-click regarding the file, and select the copy to copy the file.
  • Later, head to desktop, press the best button regarding the mouse and click regarding the paste to paste the file.
  • Open QuickBooks while holding down the control key, to make sure you are redirected to a No company’s open window.
  • Now, open the current company or select Restore.
  • Go to the desktop and look for the business file which you copied and open.

You may also read:

Solution 5: Run QuickBooks File Doctor

Solution 6: Rename .ND and .TLG files:

Rewrite the extension of .ND and .TLG. These extensions help to configuration files that allow QuickBooks Desktop to get into company files in your network or perhaps in multi-user mode. Harmful .ND or .TLG files could cause errors when opening the QuickBooks desktop. Renaming these files will not result in data loss because when you open the business file or scan the company files utilizing the QuickBooks database server manager, these are typically automatically reproduced.

  • Go in Computer and select the folder and open for which your business file is.
  • Default Location: C: \ Users \ Public \ Public Documents \ Intuition \ QuickBooks \ Company Files
  • Search for files with the same file name as your company file, however with the extension.ND and .TLG.
  • eg: company_file.qbw.ND, company_file.qbw.TLG
  • Right-click select .nd / .tlg file and rename. To link the phrase “.old” within the last of this file extension and press enter.
  • Example: company_file.qbw.nd.OLD, company_file.qbw.tlg.old

I hope this post will allow you to resolve QuickBooks Desktop error 6000 77. If you still need help using this error or other QB issue, then give us a call at our toll-free QuickBooks Error support number

Go Back


Blog Search


There are currently no blog comments.