Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
posted
Hi, we're having a serious issue importing to QB Online that we've spent at least a week on, trying every possible solution, but I think the main issue is further up the pipe.
>> Main goal: We need to import our QB file from QB Enterprise to QB Online.
>> History: We told our accounting firm we were switching to QB Online, received the final .QBB from them (last used in QB Enterprise 22.0, so we're using the same everywhere) and are trying everything we can to get it to upload. We *always* have the same issue, which makes me think we're focusing on the wrong end of the puzzle.
>> Process Used: We start the process using the standard instructions per the link just below, then we log in (we've tried pre-logging in via "My Company" with no difference), we click through as expected (single QBO company, no prompt for inventory presumably because we don't use QB for that) and then we get the screen below, a few small windows briefly pop up reading various item sets from the file for about 30 seconds, and then the last one leaves and we sit at the window below for ~1.5 hours until we get the error in the title ("Error: Request Failed with Status Code 401"), of which there is a screenshot at the bottom of this post.
I'm always using the same method per the instructions here for QB Enterprise: Link. I've had it verified twice now with QB Online support and QB Desktop support via remote screen share that I'm not doing any of the steps wrong.
>> Alternative fixes methods we've tried (suggested by both Intuit Support and others):
1) We are the Primary Admin on the account now. (bookkeeping company moved our finance@ e-mail into that slot).
2) We have tried both running as Admin (right-click, Run As Administrator, to be clear) and not.
3) We have verified the file -> No issues found right from the start, so I don't think it's damaged.
4) We have confirmed we are under the targets limit. -> Way under, esp for QB Enterprise.
5) We have tried ensuring the file is in a folder <4 folders deep per Link, even though we don't get that error or any of the errors on that page (*only* the stated/pictured one at the bottom of this post).
6) We have tried it with QB Ent 22.0 fully patched (as of 7-13-22) and unpatched (came as R5_45 in the Trial installer) as our old accountant said they only got it to export *without* patching, though who knows what R-version they were on when they downloaded the trial.
7) I have tried all of these fixes using QB Ent 22 Trial in a completely freshly installed and patched Windows 10 virtual machine.
8) I have tried most of these fixes using the QB Browser-based Ent 22 Trial (QB Online -> Gear -> Import Desktop Data -> "Go To The Tool" link at the bottom, as I don't know why it's labeled "2017 or older" since it is just an instant deployment of the latest QB Desktop/Enterprise trials set to forcibly start the export process on file open.
Both the lack of any differences in any approach and seeing almost no network traffic (after a tiny initial burst once the export starts) have me believing that even if we may have solved one small issue incidentally (maybe with Run As Admin), the main issue here is the authentication. If I'm correct, the 401 error is not going to be a local installation or process issue but solely a network authentication problem between the program and the server, per almost every other post I've seen about it, either from developers or users.
>> Potential other wrinkles:
1) The bookkeeping company added us as the Primary Admin on the file by replacing their own user (different domain, different e-mail, as they were managing it until now). When signing into the new QB account owned by our organization, which has our self-purchased QB Online company, I don't see any link between our primary login/account and the permissions in that file (managed under Company->Users->Intuit Account User Management, which is almost certainly going to the web for the info shown there). I'm wondering if this is indicative of a conflict where the same e-mail address is both present in the QB Online account we own and manage and in this older... sub-account (organization? Unsure how to differentiate it) made for us by the old bookkeeping company. However it's all being stored on the back-end, it makes me wonder if it's actually two different accounts on the back-end and they're bumping heads. While the credentials are identical for both, there could be internal GUIDs or the like that are different and conflicting.
In support of this theory of some kind of conflict, when I check the F2 screen in the file I see (under "Intuit Account Information" -> "Company Intuit ID") the company ID of the old bookkeeping company, which I know is correct because the backup is from before they bumped us to Primary Admin on our own finance@ e-mail address at our domain. Our new Company ID, shown in QB Online, is completely different.
On the other hand, while I think the e-mail address being associated with two company IDs, however loosely, is possibly related to the issue, I *don't* think that the different company IDs themselves are the main issue, or possibly an issue at all (but please comment if you think so). My rationale is that tons of people rely on bookkeepers and accountants and import/export services, which almost certainly have accounts registered to other company IDs (their own or clients) to work with and export to QB Online all the time, meaning this would be a constant battle if an e-mail associated with one company ID were unable to interact with a different company ID.
Assuming I'm right and there's a conflict with the e-mail address being associated with two companies, I'm going to change the Primary Admin to a totally unrelated address and see if that changes anything while I wait for replies here.
>> One other potential question remains, however, that we may try next: How do we change the "Company Intuit ID" in a file so it's associated with (IDed by) our QB Online account? Is it not stamped on the file but instead just based on the current or last Primary Admin login to that file, and thus has nothing to do with the file itself?
>> Another idea: Is the export having an issue because we don't own a copy of Quickbooks Enterprise Desktop on our new/main account? This wouldn't seem to make sense, because if so then how would anyone use a trial copy (per #8 above, even Quickbooks' own tool uses the latest Enterprise Trial copy) as a temporary copy to export to Quickbooks online? This is probably not true or an issue.
Thank you for any help you can provide.
>> Final error we always get:
