Unknown error after upgrade to V23, desktop, Enterprise

Thank you for turning to the Community about your concern, topherfarrell.

I can see how this error you're experiencing kept you from opening your QuickBooks Desktop (QBDT) Enterprise 2023 smoothly. I'm here to help ensure you can access the desktop program in a breeze.

Before we start, allow me to share the reasons what causes the error:

• The file is saved in a protected location such as the root of C:// Drive or Program Files of a Windows Vista, 7 or 8.
• The file is located in a restricted location.
• Folder permissions are not set up properly.
• The folder where the company file is saved is damaged.

We've compiled a list of troubleshooting solutions to resolve the error. Let's make sure to perform each one according to their order for best results. 

To begin, download and install QuickBooks Tools Hub. From there, you'll have to launch the QuickBooks File Doctor. This utility is used to resolve company file-related errors. Follow these steps to run it:

1. Make sure to close your QuickBooks.
2. Download the latest version of the QuickBooks Tool Hub (1.6.0.3) and save it where you can easily find it. 
3. Open the QuickBooksToolHub.exe link.
4. Choose Yes to allow this app to make changes and click on Next to install it.
5. Press the Yes button and accept the license agreement
6. Follow the on-screen instructions to complete the installation process.
7. Once finished, tap the Finish button.

Next, lodge the QuickBooks File Doctor. Here's how: 

1. In the QuickBooks Tools Hub window, go to the Company File Issues menu on the left panel and click the Run QuickBooks File Doctor button (can take up to one minute to open it).
2. In QuickBooks File Doctor, choose your company file from the drop-down menu.
3. If you’re unable to see it, select Browse and Search to find your file.
4. Press the Check your file option and then Continue.
5. Enter your QuickBooks admin password and then click Next.

After performing these solutions, open your QuickBooks. If the error persists, perform Solutions 2 up to 5 in this guide: Message: You do not have sufficient permissions to the specified folder.

I've included an article that discusses in detail the various access limits in single or multi-user mode: Features available and tasks. 

In addition, these resources will guide you on how to handle company file and network issues:

• Fix company file and network issues with QuickBooks File Doctor
• Resolve network issues with QuickBooks File Doctor test results

Don't hesitate to leave a comment below if you have additional questions about the multi-user mode. I'll be around to assist you further. 

None of the suggested fixes worked. Also, none of the suggested errors were the cause. I found workaround that seems to be functioning for now. A little more info on my setup in case anyone else encounters this-

• My company file is hosted on a server running Windows Server 2022
• I have approximately 20 users
• My version of QuickBooks is Enterprise: Manufacturing & Wholesale V23, update 33.

Upon upgrading from V21 to V23, half of my users received the error that I originally reported in this post. The fix that I discovered was, after the installation of V23 I opened QuickBooks, on the first screen that asks how I want to set up, I simply closed the window, chose "open or restore company file > open a company file" from there I should be able to just choose my company file and hit "open" BUT that is where the error would pop up and not allow me to move forward. What I did was right-click in the "Network Locations" then select "Add a new network location" then follow the steps in the "Add network location wizard", choose the "custom network location" then I manually added the address to my enclosing file that contains my company file. Even though the address is identical to the option that appears automatically in the window, for whatever reason, this bypasses the error and allowed me to complete the install. I replicated these steps on 10 workstations that initially gave the error, but with these steps it worked.