Home → Online Banking →

Bank of America Direct Connect problem

• Edit

wa1oui

Jul 21, 2020 @ 06:51 PM

I have 3 web accounts with Bank of America that I direct connect to quite a few checking/savings accounts.

Two days ago I started getting a "2000" error (attached) that said there was a problem with my name or PW. I logged in to the associated web account and it logged in fine. I tried several times to initiate the download getting the same error. Then BoA locked my web account because of too many bad login attempts. I reset the web account, and then deleted online banking from one of my accounts that was not connecting. I attempted to reconnect it using my name and new PW. I got as far as having BoA give MD the list of accounts I have on that web account, meaning it had to have hopefully accepted my name/PW. I chose the account I wanted and it then bombed out again with the 2000 error.

I was able to speak to someone at BoA who actually knew about Direct Connect and he said that they could find no problem with my account. Direct Connect itself seems to be working as another web account has no problem direct connecting.

I tried deleting the account from Direct Connect and re-establishing it but that didn't help either.

I wanted to run the Remove All Services.py script as an attempt to clear a possibly corrupt file/db or whatever, but it wouldn't run, which will be the subject of another discussion.

Any ideas?

• BoA_Error.png 96.6 KB

1. Support Staff 1 Posted by Ethan on Jul 21, 2020 @ 08:36 PM

   

   Hello,

   Are you certain that you are using the correct user name and password? You seem to write that you are using the same information as you use to log into your account on the bank's website. However, application-based online banking often requires a different login/PIN than the ones that are used for ATM or web-based banking. Are you able to verify with this person who knows about direct connect that you are using the correct user name or password? Bank of America stopped enabling new accounts for direct connections a few years ago, and I'm afraid whether they have separate usernames and passwords (a fairly common practice) has slipped from my mind. That error message is what is being sent from your bank's servers, so there's not really much to reset in Moneydance for that kind of error.

   Ethan
   Infinite Kind Support

   • Edit

2. 2 Posted by wa1oui on Jul 21, 2020 @ 10:16 PM

   

   Hi Ethan,

   I’m absolutely certain name/pw are the same as I use 1Password password manager. Couldn’t remember 30 character pws without it!

   These Direct Connects have worked for years with the same user/pw and some still do on different web accounts, so I know that that system is functional: same name/pw for web and account.

   I wanted to reset MD’s set of online info completely as in the past I’ve had other problems with Direct Connect that it solved… hence my Python problems…

   David

   • Edit

3. 3 Posted by wa1oui on Jul 22, 2020 @ 12:41 AM

   

   The problem is definitely Moneydance. After reading something similar in another post somewhere on this board, I just set up a brand new MD with no accounts. I added one of my BoA accounts that kept failing, and this time using the same name/pw that fails on the other database it works here. And I know that it is not my typing as I use a password manager. I still would like to be able to clear my entire set of Direct Connect entries and start over, but that's the subject of my other thread. Any other ideas without my clearing the info?

   • Edit

4. 4 Posted by dwg on Jul 22, 2020 @ 01:25 AM

   

   I'm a fellow user.

   If a new data set works it does suggest that Moneydance has cached some information in the existing data set that needs to be reset, I recall seeing this on a few occasions, but it is not all that common.

   As far as the remove one service script I have seen at least 6 different versions of this, some at least seem to be Moneydance version specific, suspect some due to the API change in MD2015 and perhaps others due to Java/python version changes in later Moneydance releases.

   From what I can tell the attached one seems to work with Moneydance 2019.

   • remove_one_service_2019.py 999 Bytes
   • Edit

5. 5 Posted by wa1oui on Jul 22, 2020 @ 01:32 AM

   

   Thanks dwg. If you check my "companion post" to this one, python doesn't run on macOS Catalina. I gets an error I can't get past. The one you provided does as well.

   • Edit

6. 6 Posted by jeff_l on Jul 22, 2020 @ 05:58 AM

   

   The python script will not run under Catalina unless you change your Security & Privacy setting in the OS.

   You can do this by changing the settings, best explained in the attached screen grab.

   Whether you want to do this, or if it will fix your issue, I don’t know.

   • change_security.png 212 KB
   • Edit

7. 7 Posted by wa1oui on Jul 22, 2020 @ 01:34 PM

   

   Thanks Jeff. Maddy told me the same thing on a Python thread I started at the same time as this. That didi it! I'm familiar with that error, but normally either System Prefs pops up or I'm told to go there... this time I need help.

   I was able to delete the Bank of America connection. When I re-instated it and went through all my accounts, they all work perfectly. This obviously indicates that the MD database of direct connect got corrupted somehow. This discussion can be closed.

   • Edit

8. Support Staff 8 Posted by Ethan on Jul 22, 2020 @ 03:49 PM

   

   I'm glad to hear things have been sorted out! I'm honestly still not quite sure what would have returned that incorrect password message out of nowhere, but I guess somehow it got changed in Moneydance and then the program had trouble forgetting that change.

   Please let us know if we can be of further assistance,

   Ethan
   Infinite Kind Support

   • Edit

9. Ethan closed this discussion on Jul 22, 2020 @ 03:49 PM.