Error -6000, -301

I'll share some guidelines you can follow if you encounter an error when QuickBooks tries to access the company file.

The following may be the causes of the error:

1. One or more of the QuickBooks Desktop Support Files are damaged. These files are:

• The Transaction Log (TLG) file
• The Network Descriptor (ND) file
• The Data Source Name (DSN) file

2. The company file is damaged

3. Encryption software is installed

Here are some solutions you can follow.

Rename the QuickBooks support files:

1. Open the folder that contains your company file.
2. Look for files with the same name as your QuickBooks file but with extensions .tlg, .nd, or .dsn.
3. Right-click each file and select Rename. Add the word.OLD to each of them.

Run the QuickBooks File Doctor:

You can refer to this article: Fix company file and network issues with QuickBooks File Doctor.

For detailed information, visit this article: Error -6000, -301: An error occurred when QuickBooks tried to access the company file.

I will also leave these articles for future purposes:

• Fix error -6000 when opening a company file.
• Verify and Rebuild Data in QuickBooks Desktop.

For additional QuickBooks-related concerns, don't hesitate to post them here in the Community. We're always available and willing to lend a hand to your queries. Have a great day ahead.

@dtr_0523 

Your installer file of QBD 2023 is corrupted and the error message is bogus. Reinstalling your QB program won't fix anything. Support has apparently decided not to publicly acknowledge the issue since last year. Unfortunately the Support team you spoke to by calling that phone number was not a real Intuit Support

Can you find the following files in the same folder?

90s.trf

QuickBooksDownloader.exe.config

QuickBooksDownloader.exe.manifest

Just upgraded to 2023 from 2022 and getting the same error -6000, -301. Called the telephone number on the screen and was told $2,000 to $3,000 up front to fix...never had problems with this before and cannot get it figured out.  Has to be in the new version..?  Funny thing is it is only showing the error on the server, all the work stations are fine.