I am not finding any documentation on 15 digit error codes as reported by the "Unrecoverable Error" message.
We have a recent upgrade to QBEnt 2022, but the Support folks also installed a different firewall and we've been having strange issues. Not to mention a huge turnover in our QB user staff; no one seems to know what they are doing anymore!
Any thoughts on this error code? 1407181142 28662
I not know what was being done prior to receiving this message.
Let's get rid of the error code, mwgross1.
Is the error only happen to one specific user? If so, the credential could be damaged. Let's check by re-creating this user.
If the same issue persists, you can run the QuickBooks File Doctor. It automatically opens the firewall ports to configure Windows Firewall. For the detailed instructions and steps, you may check this article: Configure firewall security settings for Desktop.
Also, make sure to download and install the latest release so the software will always have the latest features and fixes.
Due to the random nature of the errors, the error number you get may differ from what is shown. Here's an article for other troubleshooting solutions: General Troubleshooting Steps.
You may also contact again our QuickBooks Live Support Team so they can create a case to isolate the issue. Here's how:
Stay in touch with me if there's anything else you need about the error code you're receiving while using QuickBooks Desktop. I'll be right here to provide the information that you need.
The error is occurring with multiple users. They have had new accounts set up which work once, and the error returns.
Our firewall is not Microsoft, but another party. Hence QuickBooks File Doctor won't be of much use to open needed ports!
We have not installed the latest version. I suppose we should do that next! Here is our current info:
Here is the log file contents where the user gets into trouble. Maybe someone can tell me what it is telling me?
tasktracking.cpp (775) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 Cumulus:'ninosantarris' Form (Receive Payments (Editing Transaction...) ) Form
qbformnavbar.cpp (81) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 PayRcptCustomize::GetStringDataOnHeap content size=146ld
qbformnavbar.cpp (88) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 PayRcptCustomize::GetStringDataOnHeap LocalAlloc allocated 147ld bytes
debug.c (335) : MESSAGE: 1420: Thu Apr 28 14:46:56 LVL_ERROR--V32.0D R3 (M=1066, L=335, C=249, V=0 (0))
DLPEngine.cpp (365) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 DLPEngine::Inside DLPEngine::ISDLPApplicableForType type=1 isApplicable=0
DLPEngine.cpp (365) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 DLPEngine::Inside DLPEngine::ISDLPApplicableForType type=2 isApplicable=0
DLPEngine.cpp (365) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 DLPEngine::Inside DLPEngine::ISDLPApplicableForType type=3 isApplicable=0
NudgeMgr.cpp (857) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 FeatureDiscovery: EventName: AdditionalTracking Message: TrackingMessage= Triggered WorkflowCategory=ReportOpen;; CoreRealm=9130350968098056; AuthId=[removed]
NudgeConfig.cpp (269) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 FeatureDiscovery:NudgeConfig::GetNudgeConfigValue::Can't find nudge config value for key1: NudgeConfig, key2: ReportOpen, key3: MemorizedReportNudge, key4: Repeating
NudgeConfig.cpp (269) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 FeatureDiscovery:NudgeConfig::GetNudgeConfigValue::Can't find nudge config value for key1: NudgeConfig, key2: ReportOpen, key3: ManageCashflowInQBONudge, key4: Repeating
NudgeMgr.cpp (857) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 FeatureDiscovery: EventName: AdditionalTracking Message: TrackingMessage= WorkflowCategory=ReportOpen; NumberOfActiveNudges=2;; CoreRealm=9130350968098056; AuthId=[removed]
NudgeMgr.cpp (857) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 FeatureDiscovery: EventName: AdditionalTracking Message: TrackingMessage= NudgeName=MemorizedReportNudge; NudgeRuleResult=false;; CoreRealm=9130350968098056; AuthId=[removed]
NudgeMgr.cpp (815) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 FeatureDiscovery: Unable to find file specified in configuration : ManageCashflowInQBONudge
Approvals.cpp (174) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 Approvals::Exiting Approvals::IsApprovalApplicable isApplicable = 0
formwin.c (2809) : CHECKPOINT: 1420: Thu Apr 28 14:46:56 Creating form: formID=600, itID=2
senderrorapis.cpp (405) : MESSAGE: 1420: Thu Apr 28 14:46:56 LVL_ERROR--QuickBooks has experienced a problem and must be shut down, ErrorCode:3665512886.
We just upgraded from QB 2019 to QB 2022 (all Desktop) two weeks ago and are having the very same issue. The only fix at this time, which is absolutely unacceptable, is to uninstall on the desktop and reinstall. The user can then login however, if they log out of QB at all during the day or if they sit idle and get aborted out, they cannot log back in without doing an uninstall and an install. I am very frustrated with this issue and apologize for not having more positive feedback. We too have gone through every step out there with tool hub etc to get no positive results back.
New and more frightening information, we are in the middle of a payroll. I was reviewing payroll after updating the tax table, which recommends that I restart my QuickBooks, which resulted in having to uninstall and reinstall, went back into reviewing and no federal withholding, Social Security or Medicare taxes are being withheld. I updated payroll tax again, and again, it wants me to restart QuickBooks to apply the update correctly, however, if I log out of QB to restart it, I get the unrecoverable message again! And payroll isn't correct because it won't fully apply the tax update. HELP!!!!
This is not the kind of service we want you to experience while using QuickBooks. Don't worry I am here to help you get through this error you've encountered. While Community is a public space, and this requires pulling up your information which we were unable to do in Community for security purposes. I will route you to our customer support team. One of our agents will be able to pull up your account in a secure way and further investigate this matter. They can also provide additional troubleshooting steps to get this resolved.
Here's how to reach them:
You may refer to this article to help Unrecoverable error in QuickBooks Desktop. This article contains some list of unrecoverable error scenarios and how to fix them.
Additionally, I recommend checking our Help articles page that you can for future reference. From there, you can read some great articles and learn some best practices in managing your QuickBooks Desktop (QBDT).
Please let me know how the call goes. I want to ensure everything has been taking care of. Take care, and have a great day!
We have done every step in the above link and about 10 other possible links and are in critical mode now. I have requested a call, which will be the 4th one and I have to have this fixed and resolved today.
Problem was resolved, in spite of the lack of support from QuickBooks. I hope something here may help.
It turned out that:
1) We had been running QBEnterprise 2018, and have been under an annual contract since 2006, and
2) an employee who didn't know better took out a new contract for 2022 under a different name, and
3) Said employee quit, after transferring ownership of 2nd account to correct person, and
3) all the users were put into the INTUIT.COM side and all worked well for 24 hours, and
4) then the error message started to appear, and
5) the users in the 2nd account could only access the 1st original account at INTUIT.COM, and
6) Ownership of the 2nd account reverted to the former employee, and
7) former employee had to return and turn over account to new owner a second time, and
8) newer users had to be added to 2nd account again,
9) but this only worked for 24 hours.
10) 15 digit error messages started again,
11) until almost no one could open the company file.
12) at this point, no one had access to the new account, only the old one.
We did fix it by doing the following:
1) had former employee transfer ownership for the 3rd time, and
2) opened the company file with working credentials, and
3) ran verify and recover (2 errors detected), and
4) backed up company file, and
5) installed R4 minor update (we had been at R3), and
6) made sure all installations were upgraded to R4 (one already was; not good!)
7) Added users a 3rd time at INTUIT.COM
8) Brought our staff back into our company file one at a time.
The system has been stable for 2 weeks now. My suspicion is that INTUIT.COM was not handling 2 licenses and 2 customers with one user account needing access to both. I can see getting it wrong, but not changing it based on access. Anyway, I am glad it is working at this point!.