Password problems between Quicken & Bank of America

After using Quicken (in various versions) to successfully connect with BoA since 2002, I have had an "improper password" error message (OL-334-A) several times over the past six weeks. I have reset the password with BoA after having access locked and had been using the same password for the last month. However, that password in Quicken is now giving me an error message while I can still connect to the BoA accounts via the web interface.

I have tried using the online center refresh method and have contacted both BoA and Quicken with the resultant tech support personnel pointing the finger at each other. Any help with others who have come accross this problem would be greatly appreciated.

Reply to
JimCrowell
Loading thread data ...

Adding the fact that I have also tried the deactivate/activate feature to no avail.

Thanks in advance.

Reply to
JimCrowell

wrote

What version are currently using?

Is it the same (334) error message you got before? If not, what is the message, and its number?

Do you use One Step Update with BofA? Have you tried recreating the pin vault? Print/Delete/Create.

Reply to
John Pollard

Q2006 Premier R4

Yup. Same each time.

Yes.

I don't use the PIN vault.

Reply to
JimCrowell

wrote

Once you get this message, it will not go away until you get things straightened out with your fi. It means you - or someone - made too many consecutive logon attempts with a wrong user-id/pin-password. I think this error will usually be preceeded by several OL-332 errors (assuming you were the party making the incorrect logon attempts), which just means you supplied the wrong user-id/pin-password. If you do that too many times in a row (probably 3 times), you get locked out and get the OL-334 error.

That's odd. I am unable to do a One Step Update without the use of the Pin Vault. (Q2005 or Q2006).

I had a couple of password problems with BofA a month or so ago, but they were caused by some testing I did which used an incorrect pin and got me locked out at BofA ... then I ran into BofA's newer pin/password requirements which obsoleted my old pin. Once I provided an acceptable new pin, and stopped testing with an invalid pin, I have had no problems.

Reply to
John Pollard

The correct password was used and all the errors (indeed, 3X) happened on one attempt to connect with BoA. It is indeed a weird happening.

The original problems, which necessitated the four password/PIN changes, were indeed linked to the BoA site changes. This much they admitted as being their responsibility. I haven't the foggiest as to why it has cropped up again now.

Working around with web connect until BoA or Quicken tech support can provide more information. Thanks for your (excellent, as usual) help on this matter.

Reply to
JimCrowell

wrote

Nuts, I just thought of something.

I did have another problem with BofA back in the middle of last month; I can't remember if there was a specific error number or what the error message was ... but I could not download to Quicken, though I could log on to the BofA web site with the same user-id/password.

It turns out the problem was that BofA will not allow you to specify in Quicken, that you can view your BofA account at Quicken.com. (I am reasonably certain this is a new "policy" on BofA's part.)

Click the "Change Online Services" button on the Overview tab of the account; uncheck "Check here to view your account on Quicken.com" and see if that helps.

Reply to
John Pollard

One other possible explanation for the password error comes to mind. My wife had been trying to manually enter her PIN when trying to log on to the BofA site. It rejected her PIN. The reason for this was that she had memorized her 4 digit PIN as letters since the numbers and letters coexist on the same

10-key pad at the bank. Of course, entering them on a computer keyboard, the letters and numbers are unique. Entering the numbers themselves worked.

Not likely your problem but just something to keep in mind.

- Dave

Reply to
David In NH

I reset the passcode again and, naturally, everything now works. I also did uncheck the box as I too was getting a "could not update" certain accounts that began around the same time (end of July) that the problems started.

Reply to
JimCrowell

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.