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

Question

Could really use some savvy technical advice here. There are a few issues which I believe may share a common thread, and which may be related to .NET (which I've installed and removed several times). I know this is a lot, but I really need to get this resolved.

Quickbooks File Doctor won't launch--starts to run and the exits; this is in the Event Log:

Application: QuickBooksToolsHub.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOExceptionApplication:

Also in the Event Log:

An unexpected error has occured in "QuickBooks Desktop Pro 2021":
Connection Error:Invalid user ID or password

But there was no failed login attempt to the QuickBooks company file.

These issues seem to happen on several company files, and the files are locally hosted, in the Public folder. I've checked permissions and used the ToolHub Network Check tool and they're OK.

When I try to run a stand-alone version of FileDoctor (not launched from the Hub) I get this message:

* QBDBMgrN not running on this computer.
* on this computer and may be blocking QuickBooks.
* Webroot SecureAnywhere Antivirus is active on this computer and may be blocking QuickBooks (and yes I did uninstall Webroot which didn't fix anything).

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.
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, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)

I'm hoping that these details will resonate with someone!

RCV · Answer

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:

Go to the File menu, then hover over Utilities and select Rebuild Data.
On the QuickBooks Information window, tap OK. Follow the onscreen steps to save a backup.
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.
When the tool finishes, press OK.
Go to the File menu. Then hover over Utilities and select Verify Data.
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:

Go to the File menu. Then hover over Utilities and select Verify Data.
Let the tool check your file for data issues.
From the Verify Results screen, select Expand All to see the errors.
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:

Select Network Issues
Choose Quickbase Database Server Manager. If QuickBooks isn’t installed on your server, you’ll be prompted to install it.
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.
The QuickBooks Database Server Manager will repair your firewall permissions automatically.
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.

Sign up

Login with SSO

Login to the community

Login with SSO