Community discussion: CitiBank Returns CC-501/101 Error Resolved, now creates CC-503 error

- J
- John Pollard
  
  Contact options for registered users
posted
2 years ago

Sun, Sep 5, 2021 2:45 AM

CitiBank Returns CC-501/101 Error Resolved, now creates CC-503 error

Found at:

formatting link

The original poster has committed a cardinal error: he has not provided sufficient information. Every new discussion should contain:

- Quicken OS; Edition; Release (found at Help > About Quicken)

When downloading is involved, the original post should also contain:

- The Quicken account "Type" (found on the General tab in the Edit Account Details dialog for the Quicken account)

- The QUICKEN name of the financial institution (found on the General tab in the Edit Account Details dialog for the Quicken account)

- The Quicken "Connection Method" for the download to the account (found on the Online Services tab in the Edit Account Details dialog for the Quicken account)

In this specific case, assuming that the Community discussion Subject contains the correct QUICKEN financial institution name (the Subject should not be the location where readers are expected to find the correct financial institution name), it's important to note that the financial institution name CitiBank does NOT allow "Direct Connect" downloads: the only options are Web Connect (which cannot be used in a One Step Update), and Express Web Connect (which CAN be used in a One Step Update. So based on that assumption that the correct financial institution name is CitiBank, and that the original poster is using One Step Update to download: the "Connection Method" must be "Express Web Connect".

Express Web Connect (often referred to as EWC) is the most unreliable Connection Method available to Quicken users. When Express Web Connect is being used and is experiencing problems, "Web Connect" is an excellent alternative (when the financial institution also offers Web Connect). NO ONE should complain that the CANNOT download transactions using Express Web Connect, when they have Web Connect available and have not attempted to use it.

Anyone experiencing ANY Quicken error should read the Quicken FAQ for that error (when available) VERY CAREFULLY. At

formatting link

key the error number (the numeric portion of the CC-nnn error - in this case, 503).

There is a very important caveat in the CC-503 FAQ to which the op was referred, namely: "Please note, Quicken has a 16-character limit for bank passwords. If your bank password is longer than 16 characters, it will need to be shortened."

It's not clear that the original poster in the above Community discussion noticed that. If the op did notice it, he was remiss in not including that he noticed it, and how he addressed that issue, in his comments. Instead, the op posts information that provides limited insights to those wanting to help - focusing instead on the assumption that it must be a Quicken problem.

It appears to me that the original poster is intent on believing that his problem is caused entirely by Quicken. While that is possible, banking on that assumption is not the best approach to solving this, or any, Quicken problem.

Loading thread data ...

- J
- John Pollard
  
  Contact options for registered users
Vote on answer
posted
2 years ago

Wed, Sep 8, 2021 5:55 PM

Some additional information:

I think the 16 character password limit referred to in my previous post (from the CC-503 FAQ) only applies to the Express Web Connect Connection Method (which the original poster in the discussion is using).

But there is another limitation on passwords for Express Web Connect downloads, namely: "[It] ... could be that the bank account login password uses special characters that interfere with Quicken's ability to download transactions. These special characters can be (but are not limited to) the ampersand (&), left carat (<), right carat (>), backslash (\), and forward slash (/)." Passwords using those characters must be changed. [This limitation definitely only applies to Express Web Connect.]

Both those password limitations provide ample reason not to accept at face value the claim that, since the user can manually logon employing the same credentials used in Quicken, the user's Quicken credentials must be legitimate.

The original poster has also subsequently claimed that he can not modify his financial institution password in Quicken because there is no entry for the financial institution in the Password Vault. The process has changed (EWC accounts were intentionally removed from the Password Vault), but financial institution passwords can definitely still be changed in Quicken ... you just have to change them at the financial institution first. As per another FAQ: "If you have recently changed your password for your bank's website, you will be prompted to change it in Quicken after you attempt to update your accounts with the old, stored password."

Also, while awaiting resolution to the problem, those Citibank users can manually logon to their Citibank accounts and use Web Connect to download to Quicken.