Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Has anyone seen this error before?
Error 22 - RealmInput: TokenHeaders for the user found to be NULL
Rebuild will not correct it.
Thanks for posting here in the Community, @YourITLLC.
At this time, we have an ongoing issue where users are getting a RealmInput error when verifying the file. Rest assured that our product engineers are diligently working for a fix.
To ensure you'll get an update about the resolution status, I recommend contacting our Phone Support Team. This way, they can add your company to the list of affected users and provide this investigation number for easy tracking: INV-46657.
To reach them, please follow the steps below:
For now, you can visit our blog site so you'll be able to get the latest news about QuickBooks and what our Product Care Team is working on.
Thank you for your patience while we work for a fix. Please post a reply below if you have other concerns with QuickBooks Desktop. I'll be more than happy to assist you again. Have a great day and take care always.
Is this still an ongoing problem? I received several errors today when I was working on Bank Feed transactions. Most of them were fixed by running verify and rebuild a couple of times.
This problem has not fixed itself and I found this information about the bug, but it was posted in September and I wanted to know if this is still an ongoing issue, and if not, how do I fix it on my QBDT?
Thank you
EJ
Hi there, GolfNut72.
Thank you for posting here in QuickBooks Community. I appreciate you for providing details that most bank feed transactions issues were fixed by running verify and rebuild.
The error about RealmInput has been closed and tag as resolved. Since you still encounter the same problem, you'll need to make sure the RealmID is showing in the F2 (Product Info) window.
If you have logged in through the My Company window and no RealmID is showing, I'd suggest checking the My Company settings to make sure the Company Name is filled in and that the email address format looks OK. Also, verify no special characters are used in the names of bank accounts.
Once corrected, log out of My Company and log back in. Then, you can try running another Verify or Rebuild to see if the results still show the same. If the issue continues to occur, I'd recommend contacting our QuickBooks Desktop Support Team. They have the tools to pull up your account to investigate the cause of the problem when working on bank feed transactions. Please follow the steps shared above on how to reach them.
Please refer to this article to see different information on how you can fix several OL and OLSU Bank Feeds errors and what causing the errors to appears: Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop.
Please know that we're open 24/7 here and I'm always ready to help. Have a great day.
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.
For more information visit our Security Center or to report suspicious websites you can contact us here