Navy Federal Credit Union NCFU 2 Step and downloads not working

Navy Federal Credit Union NCFU 2 Step and downloads not working

Found at:

formatting link
This discussion contains a couple of excellent examples of users who rush to assign blame when they have literally no clue what they're talking about.

Granted, one of the most common user errors is to confuse correlation with causation (as in the above discussion); but that does not excuse the error.

And one user in the discussion actually goes so far as to say, "Really tired of software updates that never seem to have conducted any regression testing." Since the error is not a Quicken error, and since the error has existed for

Despite several users in above discussion noting the CC-505 error, apparently not a single one actually looked that error up. If they had done so, they would have found this:

"You may receive the following message when you attempt to update your account transactions in Quicken:

"'CC-505 - Quicken is unable to update your account. This may be due to a temporary server issue or a communication error. Please try again.'

"Note: You may be able to log into the bank's website successfully and still receive this error in Quicken. This is because the error is caused by an issue on the bank's servers (TYPICALLY A BLOCK PLACED BY THE BANK [emphasis added]) that Quicken uses to download transactions."

There is not only not a shred of evidence that the error is caused by Quicken (much less, by the latest release of Quicken), but: the Quicken KB article noted above proves that the cause is NOT the latest (nor ANY) Quicken release).

I can also add that I have Q2020 R26.17 - which is MANY (about 30) releases earlier than the current Quicken release (R33.19); and I see the exact same CC-505 problem when downloading from NFCU.

One user (crjefferson) in the above discussion actually goes so far as to say, "Really tired of software updates that never seem to have conducted any regression testing." Since the error is not a Quicken error, and the error occurs (today) in a release that is some 30 releases old; the error has NOTHING to do with the "current release" (or ANY release), and complaining about a lack of "regression testing" is a totally phony attempt by the user to pretend to have superior knowledge, while demonstrating instead, snotty ignorance.

[And since NFCU is preventing access, no one should expect to see any authentication - multi-factor or otherwise.] [Last community discussion post: 05-09-21 @ 05:02 am]
Reply to
John Pollard
Loading thread data ...

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.