Weels Fargo resolution

No info at all via the quickencommunity ticket I'm following..but.. I got
through to someone knowledgeable at Wells Fargo and my problem is solved!!
The trouble was special characters in passwords. Oy!! Apparently, Wells
Fargo allowed damn near anything [and I've had no trouble with logging into
my account via their website] BUT: Quicken doesn't like "damn near
anything" and so things get messed up when it relays my password to Wells
Fargo. [the tech support person said this same thing happened when they
expanded passwords to 32 characters -- that works fine within WF and on
their website, but Quicken couldn't [can't?] handle passwords that long].
When I fixed my password not to have any special character not on the list
at WF it all worked.
It is a little hard for me to figure out what was going wrong. I'd assume
that if I gave Quicken the *wrong* password, I'd get some useful "your
password isn't correct" error or something like that. In this case all I
got was "we can't handle your request at this time, please try again later"
from WF. Anyhow, my nearly-four-week hassle is, for the moment, fixed.
/Bernie\
Reply to
Bernie Cosell
The only standard keyboard character restriction imposed by Quicken/Intuit on the password used to access an account at a financial instituion occurs when we use the Express Web Connect connection method and is , and &, however, the financial institution's profile may further restrict the pasword's character set and length. From your description, it sounds like the coordination of the financial institution's profile between Wells Fargo, Quicken and Intuit has broken down.
Reply to
Sherlock
[...] } > The trouble was special characters in passwords. Oy!! Apparently, Wells } > Fargo allowed damn near anything [and I've had no trouble with logging into } > my account via their website] BUT: Quicken doesn't like "damn near } > anything" and so things get messed up when it relays my password to Wells } > Fargo....
} The only standard keyboard character restriction imposed by } Quicken/Intuit on the password used to access an account at a financial } instituion occurs when we use the Express Web Connect connection method } and is , and &, however, the financial institution's profile may } further restrict the pasword's character set and length. From your } description, it sounds like the coordination of the financial } institution's profile between Wells Fargo, Quicken and Intuit has } broken down.
That could be -- I'm guessing that WF changed their password rules (as reflected on their "change password" page) but didn't do anything about existing/"grandfathered" passwords. So I could log into their website, but when quicken passed my password *that* did check the "new rules". It'd also explain why many people didn't see any problem: if they had a non-weird password they'd never have run afoul of the rules [my password manager generated long awful-to-type passwords! :o)]
Still doesn't explain the odd error message: if WF had just rejected my password the problem would have been fixed in minutes, but Quicken saying "it's not your fault" and WF saying "try again later" wasn't very helpful. In any event, I have another weapon for such problems in the future: if deactivate/reactivate doesn't help, trying updating your password..:o)
/b\
Reply to
Bernie Cosell

Site Timeline Threads

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.