How to Fix Quicken Error CC-891 (Aggregator Connection Failed)
CC-891 is raised by the aggregator that powers Express Web Connect — the service could not complete its session with your bank on Quicken's behalf.
Why CC-891 Happens
- Aggregator service outage or maintenance
- Bank website redesign breaking the automated sign-in
- New consent screen or terms the bank requires
- Stale cached session on the aggregator side
- Multi-factor prompt that cannot be automated
Sign in to the bank website and clear all prompts
Accept any new terms, dismiss marketing interstitials, and complete any pending security setup. The aggregator's automated session stops at these screens.
Wait and retry before changing anything
CC-891 is frequently a temporary aggregator issue. Retry after a few hours — reconnecting during an outage can create duplicate registers for nothing.
Reset the account
Online Services → Reset Account forces a new aggregator session and clears the cached failure state.
Re-authorise the bank connection
Some banks now require periodic re-consent. During reset, watch for a bank-hosted authorisation window and complete it fully rather than closing it early.
Deactivate and reconnect as a last step
Back up, deactivate every account at the institution, restart Quicken, and re-add the bank linking to existing accounts.
Do Not Reconnect During an Outage
Repeated deactivate-and-reconnect cycles during an aggregator outage are how most duplicate-transaction problems start. Confirm the bank connection works in a browser first; if it does and Quicken still fails, wait one update cycle before rebuilding the connection.
Express Web Connect Down?
We can confirm whether the outage is aggregator-wide or specific to your file, and rebuild the connection safely once it clears.
Related Quicken Guides
QuickN Help Desk is a technical support service. We are not affiliated with or endorsed by Quicken Inc. All product names are trademarks of their respective owners.