Quickbooks 2021 problems -- .Net, File Doctor and more

I can see how hard you tried here. No worries, Dmillerss; I'll make amends and ensure you never have to deal with this again.

We appreciate you providing complete details about what is happening so that we can better isolate the problem. We can use the Rebuild Data tool to automatically fix minor company file data issues. Here's how: 

1. Go to the File menu, then hover over Utilities and select Rebuild Data.
2. On the QuickBooks Information window, tap OK. Follow the onscreen steps to save a backup.
3. Let the tool repair your file. It may take some time. QuickBooks may seem stuck, but as long as you can move your mouse, the tool is working.
4. When the tool finishes, press OK.
5. Go to the File menu. Then hover over Utilities and select Verify Data.
6. Let the tool check your file for data issues.

If QuickBooks finds no errors, click OK. You may continue to use your company file. There is no data loss on your end. If QuickBooks discovers a problem with your company file, click Rebuild Now.

We can also manually fix your errors, you can find the errors you can fix from the Verify Results window. Before you get started, make sure to back up your company file. To manually fix data errors:

1. Go to the File menu. Then hover over Utilities and select Verify Data.
2. Let the tool check your file for data issues.
3. From the Verify Results screen, select Expand All to see the errors.
4. For the steps to fix the error, see See Online Article. If the error doesn’t have an article, contact support for help repairing your company file.

After that, launch the QuickBooks Database Server Manager from the QuickBooks Tools Hub on your server. Check the folder containing your company's files is set up to share files over your network. Your QuickBooks company file(s) are stored on your server computer. Your workstations are the other machines on your network. Here's how it's done:

1. Select Network Issues
2. Choose Quickbase Database Server Manager. If QuickBooks isn’t installed on your server, you’ll be prompted to install it.
3. Inside the QuickBooks Database Server Manager, Select Start Scan if your company file folder(s) are displayed. If they aren’t, Browse to the location of your company file and then select Start Scan.
4. The QuickBooks Database Server Manager will repair your firewall permissions automatically.
5. When the scan finishes, press Close.

When you're done, find and open the folder you scanned. Make sure there's an ND file in the folder. It looks like this: [your company file]qbw.nd. If you don’t see the ND file, scan the folder again.

You can refer to these helpful articles in case you have any other concerns about QuickBooks Desktop.

I'd like to know how you get on after trying the steps, as I want to ensure this is resolved for you. Please reply to this post and I'll get back to you. Take care always.

Thank you for the detailed information .... you seem to think the company files need verification/repair, which I've done .... but I'm still concerned about the .NET Framework errors that show up in the event log. The errors associated with File Doctor occur prior to a company file even being opened.  I tried removing .NET and letting Quickbooks install .NET when it was launched but that didn't help.  Is there a specific version of .NET or QB 2021 that we know is compatible, and how can I verify that?

But the DB Manager is installed.  Then File Doctor throws this message:

************ Exception Text **************
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.

Hello there, @Dmillerss.

We can download the QuickBooks Tool Hub to resolve the issue. It'll help diagnose and fix a common problem in QuickBooks.

Here's how:

1. Close QuickBooks.
2. Download the most recent version (1.5.0.0) of the QuickBooks Tool Hub. Save the file somewhere you can easily find it (like your Downloads folder or your Windows desktop). Note: If you've installed Tool Hub before, you can find out which version you have. Select the Home tab. The version will be on the bottom.
3. Open the file you downloaded (QuickBooksToolHub.exe).
4. Follow the on-screen steps to install and agree to the terms and conditions.
5. Once done, double-click the icon on your Windows desktop to open the tool hub.

Then, use the QuickBooks Install Diagnostic Tool to diagnose any installation issues. Here's how:

1. Open the QuickBooks Tool Hub.
2. In the tool hub, select Installation Issues.
3. Select QuickBooks Install Diagnostic Tool. Let the tool run. It can take up to 20 minutes.
4. When the tool finishes, restart your computer.

For more solutions that you can try, you can proceed to Solution 2 found in this article: Fix Microsoft .NET Framework Error When You Install QuickBooks Desktop. Additionally, you may sometimes experience network issues when using QuickBooks. Learn from this article how you can recover damaged company files and solve network issues: Resolve Network Issues With QuickBooks File Doctor Test Results.

Let me know if you have other questions. I'm always here to help.

I've run the QBooks Diagnostic Tool and just about everything else I can think of.  Trouble is File Doctor doesn't work ... if I launch it from the Hub it never opens up; just waits a bit and then closes the Hub.  If I run in stand-alone, it says the company file cannot be repaired with the message below.  I've removed and re-added the .NET Framework several times ... does QBooks need both installed (3.8 and 4.5)?  

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, Async

I know this hasn't been an easy process for your, Dmillerss. Allow me to chime in and assist you in getting things sorted out for you.

Since you're still encountering these specific errors after doing all possible troubleshooting steps above, I'd suggest contacting an IT professional to help us identify the root cause of the issue. Also, it may be a problem with your operating system, and they'll consider checking your desktop to investigate further. 

Additionally, you'll want to visit this article for more detailed information on how to fix .NET Framework errors: Manually fix Microsoft .NET Framework errors.

Moreover, I'm adding these references that will guide you with self-help articles and reinstalling QuickBooks to fix company issues and start with a clean slate if necessary:

• Reinstall QuickBooks Desktop.
• Help articles for QuickBooks Desktop.

We'd love to hear more from you if you require additional assistance troubleshooting your desktop file. Please don't hesitate to reply in the comments below. Keep safe!

Thanks but .... I am an IT Professional.  30 years of experience, from the IBM PC to Enterprise networks.  I was hoping the Event Log errors I shared would trigger a response from perhaps the coders or tech savvy support folks at Intuit .... 

Still dealing with problems here ... but one thing puzzles me:  the error in the Event Log (see screen cap attached) says Invalid User ID or Password--but the trouble is we don't get to the point where we can enter the credentials.  So where does that message come from?  Does this cast any light on this issue?

thx in advance for any assistance ... 

Thank you for getting back to the thread and providing an update to us, @Dmillerss. I'll conform with others and share my thought regarding this matter.

Before that, know that this is not the experience we want you to have while using the service, and I appreciate all the effort you've performed so far to resolve the issue.

You'll want to check if your QuickBooks Desktop is on the latest release and verify its activation by pressing F2. If not, you can activate it through a window pop-up with the message Set up your Intuit account. QuickBooks Desktop's activation screen allows you to use an existing Intuit account or create a new one.

For detailed information, refer to this article: Register QuickBooks Desktop using your Intuit account.

Then, you can check if it resolves the problem. However, if the issue persists, it is best to connect with our QuickBooks Desktop Support, as it may be a technical issue that requires assistance from our Customer Care Team. Contact them for further guidance. They also have tools like screen sharing and guide you through the process.

Here's how you can reach them:

1. Open QuickBooks.
2. Go to the Help menu at the top.
3. Select QuickBooks Desktop Help.
4. Type Contact Us in the search box. Then, click on Contact Us at the bottom.
5. Select the way you wish to connect with support.

Please refer to this article for additional details: Contact QuickBooks Desktop Support.

You can always refer to our Help Articles for further assistance whenever you need it. There are a variety of QuickBooks-related topics and instructions here.

Please don't hesitate to reach out if you need assistance with QuickBooks-related concerns. Have a nice day!

Jesus, this entire thread is nothing but AI bot responses from "Intuit". It can't even be GPT - I'm pretty sure GPT would do a better job. Not a single response has provided any method to fix File Doctor crashing on attempted start-up. Not even methods that don't work - they're just programmed to open with something like "You sure are working hard to fix this!" then just regurgitate tangentially-related support articles, ad nauseum. Awful.

You noticed!  I got nowhere with this ... I'm done with QBooks.