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!
