nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CC-800 Errors on Accounts with 0 transactions

flashfearless

I have continued to get CC-800 errors when I have multiple accounts with a bank and one or more of the accounts have no transactions to download. The error claims the account may be deleted, but of course it isn't. Fixing / Re-Adding and all the other recommended fixes have not corrected it.

I have also tried Validating and "Super Validating" the data file (it found some weird $0 transactions on 0/0/0000), but there was no impact to the error.

And no, there was no restoration from a backup as implied in the error. I just want this error to go away, as there is no error. Just no data.

Find more posts tagged with

download transactions

One Step Update

Comments

Quicken Anja

Hello @flashfearless,

Suppose you have followed the troubleshooting instructions in this error-specific support article regarding error CC-800. In that case, as stated at the bottom of the article, you will need to contact Quicken Support directly for further assistance and possible escalation if they see fit.

We apologize for any inconvenience! Thank you.

flashfearless

The crazy thing is that when there are transactions, it will download them, and then report the error as if something was wrong.

flashfearless

I was finally able to get the CC-800 errors to disappear once I did the following 1) Validate and Repair File, Super Validate 2) Delete all old accounts which were previously marked closed and hidden from my data file (now I will have a lot of transfers with [To Deleted Account] in them) and 3) Deactivate and Re-Add the problem accounts' online connections.

I had previously tried the Deactivation and Activate steps, but it was prior to doing the Validate and Repair and the deleting of all old accounts.

Quicken Anja

@flashfearless Thanks for the update! Glad to hear the issue has been resolved, and we appreciate you sharing it here as it may help someone else experiencing the same problem. 🙂