Problem with Quicken Connection Channel

Twice now, the second time today after update to Version R29.12, Build 27.1.29.12 (Windows), my Quicken Connection Channel has been set to QCS. With QCS, every single time that I run One Step Update, I have to re-authenticate my Capital One accounts. Every single time. I am also getting an unexplained error on my Vanguard account, which I think is related. When I change my Quicken Connection Channel back to FDS, everything just works. What is going on here? Why does Quicken want to use QCS, and how do I get it to work for me?

I originally reported this problem here: https://community.quicken.com/discussion/7879300/repeatedly-have-to-link-capital-one-accounts-to-quicken#latest

I have submitted this under help->report a problem but was advised by Quicken support to post here as well.

Comments

  • BK
    BK Member ✭✭✭✭
    edited September 2020
    CapOne uses EWC+ and therefore Quicken does not store the password in the vault.  I don't know the role of the connection channel with EWC+.  Just to compare notes, My connection channel is FDS, and this is my Quicken setup for CapOne


    and this is what CapOne's website shows under [My Name] > Security

    - Q Win Deluxe user since 2010, US Subs R32.12
    - I don't use Sync, Cloud, Mobile, Web, Bill Pay/Mgr, Tax
    - Techie, Win10 Pro x64 21H1
  • markus1957
    markus1957 SuperUser, Windows Beta Beta
    As for Vanguard, it uses direct connect so the issue is not related to QCS. QCS is being rolled out to everyone over time and will be the only EWC method in the not too distant future.  Switching back and forth will only cause you more issues.

    Generally, the Vanguard issue resolves with a second try.  FWIW, it worked fine today on the first try.

    https://community.quicken.com/discussion/comment/20120450#Comment_20120450
  • Kent Fiala
    Kent Fiala Member ✭✭
    Yes I agree that my Vanguard errors seem to be unrelated. It's strange that it just reported that an error occurred without giving any diagnostic code as usual.
This discussion has been closed.