Question

Unrecoverable errors.

Forum|Forum|4 years ago
June 11, 2022
2 replies
53 views

I have tried all the online suggestions. I have even done a troubleshooting session with QB over the phone using screenshare. Unfortunately, these unrecoverable errors continue to be a constant random occurrence.

Using QB Pro 2021.

Windows Error reporting shows numerous types of these errors "An unexpected error has occurred in "QuickBooks Desktop Pro 2021":
FeatureDiscovery:NudgeConfig::GetNudgeConfigValue::Can't find nudge config value for key1: NudgeConfig, key2: PayrollCentreOpen, key3: WorkForceAutoEnableFTU, key4: ShowHighlighter"

Other errors are showing twice each of the following.

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

"An unexpected error has occured in "QuickBooks Desktop Pro 2021":
Connection String:CON=QBConnectionPool-Probe-QB_data_engine_31; ;DBF=C:\Users\Removed\OneDrive\blank\Remved Drywall DBA.QBW;ENG=QB_data_engine_31;DBN=ea6a07f4b4a44cde836afb78e81356d9"

"An unexpected error has occured in "QuickBooks Desktop Pro 2021":
DBConnPool::HandleConnectionError errorCode:-6069, dbCode:-103 from file:'src\connpool.cpp' at line 1043 from function:'DBMgr::DBConnPool::init'"

Also of note QB Tool Hub File Doctor never loads up after any amount of time waiting. The errors started appearing about 4/5 weeks ago after a QB update and restart.

Luckily the program saves data before crash, which can happen during any operation, or even sitting idle.

Hopefully someone in this community can help me get QB running smoothly again.

QuickBooks Desktop Payroll

katherinejoyceO

Level 9

Thanks for sharing your concern today, @Wallboard.

There are various causes of Unrecoverable Errors and the codes that may come with it in QuickBooks.

Before performing necessary troubleshooting, let's make sure to:

Then, let's identify how many users are affected as our initial steps. Here's how:

From the Company menu, select Set Up Users and Passwords > Set Up Users.
Enterprise users: Go to the Company menu, then select Users > Set Up Users and Roles.
Select Add User..., then type the user name and password. Select Next.
Note: Do not use the damaged user name.
Customize the user as necessary, then select Finish.
Go to the File menu, then select Close Company/Logoff.
Log in to the company file using the new log in the credential.

If the Admin user is damaged, run the QuickBooks File Doctor from the QuickBooks Tool Hub. This will help fix common errors.

If the issue persists, I'd recommend following Solution 2 in this help article: Unrecoverable Error: General Troubleshooting Steps.

Feel free to keep in touch if you need additional help. We're always around here to assist.

W

WallboardAuthor

Thanks for trying to assist. I'm still struggling with this issue now it just gets more crazy.

I have tried adding a user. No joy. Same error.
Have tried every suggestion from this site many times over. No joy.
Reset my Windows installation. Installed current signed drivers. Downloaded and installed QB 2021 Pro fresh. Loaded my company and logged out.
Next day the error returned a few minutes after opening.
2nd and 3rd days started getting BAD_Pool_Caller before or shortly after logging in to Windows. In Safe Mode I disabled all QB and Intuit Start Up Items. Suddenly no more Blue screen of death.
After several hours of using my PC without issues I decide to try QB again. Instant Blue Screen.
My last resort, unless someone can help, is to wipe my drive and start completely fresh. I really don't want to go that route.

P

PUCC_Treas

2nd reply of the day. As noted earlier I did a full uninstall, cleanup, reinstall.

At first things appeared to be okay.

I then applied all pending updates.

Now, with generic setup and sample file only, crashes are back.

Per instruction in last comment by support, I opened the tool hub and did a quick fix my program. After restarting, the same problem continues to occur.

Edit: Back to tool hub, next option is Quickbooks program diagnostic tool, which is described as: will run through a variety of repair processes for all the Microsoft components ... I went ahead and ran that, rebooted, and as soon as I open the sample file, return to the utilities page to look at repair options it crashes again.

Based on where I can always trigger, I would suspect that your IE replacement code/browser is not playing nice with new versions of Windows 11, because it is always in the website browser page where you can download the tool hub, but before I actually have any interactions with the site. And since that IE replacement browser code is probably always present in QB in some form, it might explain the intermittent nature of when this occurs. If that change was implemented in the May timeframe as IE was approaching end of support then that would explain why the generic 2021 install without updates didn't seem to be problematic. Is there a way to switch back to IE mode via a software switch/ini file/configuration setting to see if the issue stabilizes? Just wearing my IT hat here, as my day job is software support. I could be out in left field. But I suspect if I load QB 2021 on a generic windows 10 or maybe even an off the shelf Win 11 pc, then I'd probably be okay but the dev builds of Windows 11 do sometimes have cutting edge restrictions that haven't been put into the real world yet. That means whatever the OP and I are experiencing (and apparently another group of users per the comments), may become a very, very widespread issue if Microsoft does a patch cycle that pushes a change on their side triggering this. It would be useful for all of us to narrow down the focus to what is actually happening and not keep trying to put bandaid fixes on it.

Regards.

@PUCC_Treas wrote:

Based on where I can always trigger, I would suspect that your IE replacement code/browser is not playing nice with new versions of Windows 11, because it is always in the website browser page where you can download the tool hub, but before I actually have any interactions with the site. And since that IE replacement browser code is probably always present in QB in some form, it might explain the intermittent nature of when this occurs. If that change was implemented in the May timeframe as IE was approaching end of support then that would explain why the generic 2021 install without updates didn't seem to be problematic.

In regards to the above comment I made in last post I am attaching a lot file that would seem to agree with the observation. A couple of errors are being logged including this:

10:10:54:791 Error 1 QBRecommendations RecommendationsProvider : Error during loading of Recommendations System.Exception: LibraryContext is not initialized
at Intuit.QuickBooks.RecommendationsLib.LibraryContext.get_CurrentContext()
at Intuit.QuickBooks.RecommendationsLib.RecommendationsProvider.GetAccessPointConfiguration()
at Intuit.QuickBooks.RecommendationsLib.RecommendationsProvider.LoadRecommendations()

And this:

10:11:1:779 Information 1 QBBrowser
AppshellV2 {"AuthRealmRequired":"","WindowTitle":"QuickBooks","Width":"1200","Height":"900","MinHeight":"600","MinWidth":"600","IsWindowResizable":"True","HapId":"HAP_NO_HAP_ID","TitleChangeSupported":"1","EnableFileDownload":"True","PluginId":"CEFBrowserPlugin","Url":"http://http-download.intuit.com/http.intuit/QBDT_HELP/QBDTUrlRedirect.html?QBURL_ID=article000111&QB_VERSION=31","AuthFailureFallbackUrl":"","WindowType":"MODAL","Auth":"none","PreRoaUrl":"","BringMDIWindowToTop":"False","CalloutControlId":"14352","IsAuthFailureRedirectionRequired":"","ShowStatusBar":"1","SSLCertSupported":"1","ShowAddressBar":"0","ShowNavigationBar":"1","ShowProgressBar":"1","DownloadAnimationSupported":"1","UniqueUrlSupported":"0","EnableBrowserExperience":"True","BootstrapJS":"XXXXX","PostData":"XXXXX","RFAPreRoaUrl":"","RFAUrl":"","RFAPointOfNeed":"","RFABusinessRoles":"","RFAOfferingRoles":"","RFAShowEducationPopUp":"","RFAShowRFA":"","HideModalTitleBar":"false","AuthMMACARoleCheckRequired":"","AuthUrlRealmMarkerEnabled":"","Hydrator":"","ODHydrationURL":"","ShowCustomBrowser":"false","CustomBrowserName":null,"WorkflowRequirelocalFileAccess":"false","BrowserInstanceId":"biid-appshell-2-ac4ede92-feea-4592-a738-4d6d2b3f01d4","JsObjects":{"jsId-24-b97a355a-822f-4c21-852d-fb404a3d860a":"AuthenticateFromQBDT","jsId-25-2c208854-7190-4070-86ef-f15bbbd1c0b9":"PaymentsCompanyInfo","jsId-26-3d4d48e5-e6b5-4172-837e-6ad7e545ea80":"ActiveXCCTransaction","jsId-27-4040d14b-f1bf-4555-8df2-eecda34b9be1":"ActiveXAppParametersBizObject","jsId-28-83192655-1081-45ba-aaca-3eca3848c250":"ActiveXTDTBizObject","jsId-29-f9401e35-4ae3-47b2-ad1c-d2ed92c07b7d":"ActiveXNAuthBizObject","jsId-30-2f8c1bf8-57c3-4adf-9a88-466953916fef":"ActiveXWindowExternal","jsId-31-65c08238-55ca-4d39-9d09-97d2093b2cde":"ActiveXQBSDKBizObject","jsId-32-3ca2bd71-4e86-42e8-b1bd-b53bd62a0575":"ActiveXPrefsBizObject","jsId-33-c282c289-2eb8-4d28-bb56-0f7bca7ff36e":"NAuthBizObject","jsId-34-c28c6abd-431e-40f5-b5f4-3431dd1c3fbc":"PrefsBizObject","jsId-35-1cc04989-a967-496d-811c-113e2980634d":"TDTBizObject"},"CallbackId":"callbackid-2-d6ecc4f8-e728-4805-8878-9cac25c8341b"}
10:11:3:19 Error 1 FeaturesInterop AppshellV2: Exception in QBBrowserInterop::LaunchBrowserAsModalSystem.ArgumentOutOfRangeException: TimeSpan period must be less than or equal to Int32.MaxValue.
Parameter name: value

M

manderberg

We're seeing this issue as well. It started occurring late May early June.

We've done all the steps suggested.

It happens to all users.

We're on the Accounting Desktop 2021 R10 - the most current release

Permissions are correct on server

UAC is disabled

- the first time a user tries to open a company file it takes 10 minutes to open!

-use task manager to close QB, relaunch and we get QB has stopped working

-third time we launch a company file it opens right away.

I've spent 2 hours on the phone with QB support with 3 different technicians.

And no effective solutions have been offered.

C

CFODR

Manderberg,

We just updated to 2022, having the same 10 minute to open a file issue for a number of our company files. Upgrading, which was forced as Intuit dropped logging into Intuit website with IE forced our hand on upgrading, which has been nothing but pure nightmare for us for the past 5 days. Worst product ever.

Fiat Lux - ASIA

Level 14

@CFODR wrote:
We just updated to 2022,

@CFODR

Did you upgrade from QBD 2019?

Sign up

Login with SSO

Let's get you signed in

Login with SSO

Scanning file for viruses.

This file cannot be downloaded