Good morning, I may have solved this problem, fellow Quicken HTTP (null) error users. And the solution appears remarkably simple.
The problem doesn’t reside with any particular financial institution or Quicken generally, but rather with an individual Quicken account in the Quicken file that updates from a financial institution. After (far too much) trial and error, this is what appears to have permanently resolved the problem for me:
Open Quicken: Open and sign in to your Quicken file as you normally would.
Open Account Status: From the top tool-bar, select “Window.” From the drop-down that appears, choose “Account Status.”
- Isolate the Problem Account: From the Account Status Window, under the ‘Action’ column, isolate the problem account by choosing “Update” one at a time for each connected account listed. Test each account, even those from the same financial institution. While Quicken updates, observe the spinning circular arrow (next to the Account list), which indicates the one account you’re testing is being updated, until it stops spinning (i.e., stops updating).
Ignore Accounts You Determine Are Ok: If the circular arrow update indicator stops rotating with no HTTP (null) error message, that single account is ok. Move on to the next account and repeat steps 3 and 4. Keep repeating steps 3 and 4 for each of your connected accounts, until you receive an HTTP (null) error message.
Deactivate Identified Problem Accounts: When an individual account update results in an HTTP (null) error message, you have identified a problem account. Open the problem account (in my case it happened to be my BofA Savings account), choose “Settings” from the lower right menu, choose the “Troubleshooting” tab and select “Deactivate Downloads.”
Test Your Quicken File: Once the problem account’s automatic download is deactivated, test your Quicken file by clicking on the circular ‘update’ arrow in the upper left. This will automatically update all your accounts except the identified problem account you just deactivated.
Fix the Problem Account: If your step 6 Quicken file test updates without the nettlesome HTTP (null) error, then the identified account you just disabled for automatic download is the only problem account in your file. All you need do is return to the problem account, choose “Settings” again, select “Set up transaction download,” and, well, set it up with the relevant financial institution. Voila! Problem solved.
- Repeat for Other Problem Accounts: If after the Step 5 deactivation of the problem account, your Step 6 general Quicken file test still updates with an HTTP (null) error, do the following: First, fix the identified individual problem account as described in Step 7. Then continue from Step 4 with the next connected account until you identify another problem account. Once identified, continue from Step 6 until your Quicken file no longer generates the HTTP (null) error at all.
I have used this fix in the past. About 8 months ago this happened, and this fix solved it for a while. The error came back and I've tried it twice recently. Both times, it fixed it for the first "group" update, but afterwards I keep getting the error.
Thanks for the suggestion.
I began seeing this same issue with Quicken Mac 2017 (v4.7.3) about a week ago. I have several different banking accounts Golden 1 Credit Union, Citi Visa Card, JC Penny Credit, Macy's AmEx, Costco Citi Visa and they all individually show the NULL error - but continue to update. I tried the 'deactivate' fix but when I tried to re-activate with the Golden 1 Credit Union I couldn't log back in.
I called G1 Credit Union, Tech Support and was advised they are aware of this problem that many users are experiencing and do not yet have a fix, and their IT department is working on it. The account I deactivated seems to be connected again after preventing me from setting up automatic downloads.
Additionally, all transactions that download show up as 'Uncategorized' where previously repeating transactions carried over the Category.
Thanks for all the help.