Vanguard Download HTTP Error:400
I used to download transactions from my Vanguard account directly into Moneydance. Recently I've gotten the error "A communication or parsing error occurred. This could be the result of a network problem, a proxy error, or misconfigured server. Error Description: java.io.IOException: HTTP Error: 400 Bad Request"
If I delete the online banking set up and recreate it, it seems
to take my password and offers up the correct account number to
match to my Moneydance account.
Any thoughts why I can't download any more? This started about
the time I changed my on-site password, but I am confident I'm
using the correct new password.
Running Moneydance 2010r3 (757) on Mac OS X 10.6.7
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Allison on Mar 27, 2011 @ 03:06 AM
I get the same error when trying to download from my local credit union. It used to work fine...no, all of a sudden it won't. I didn't change anything.
2 Posted by Allison on Mar 27, 2011 @ 03:13 AM
Time out...on second look, it's a different error message. I'll start a new thread.
3 Posted by Jessica Little on Mar 28, 2011 @ 09:26 PM
Hi David,
If you use your old password, are you able to log in?
Jessica Little
Moneydance Support
4 Posted by david on Mar 30, 2011 @ 10:34 PM
Hi Jessica,
No. If I use my old password I get an error that indicates I'm using the wrong user name or password.
5 Posted by Jessica Little on Mar 31, 2011 @ 02:33 PM
Hi David,
It's seems like Moneydance might be having trouble forgetting your old connection information. To fix this, you'll need to force clear all of your current connection information in Moneydance. I'm sending a file called remove_all_services.py that will help do that. Before proceeding, please back up your Moneydance file, just in case something goes wrong. So far, this hasn't caused any problems, but better safe than sorry!
To use the file, first save it to your computer and then follow these steps:
1) In Moneydance, click on the Extensions Menu and choose the Add... option
2) In the window that pops up, make sure the From Internet option is selected and then click next.
3) From the list of available extensions, choose the python scripting interface extension, then click Next to download the extension and finish to complete the installation.
4) Again, click the Extensions menu. This time, choose the Python Interface option.
5) In the python scripting window, click the read from file button and load the file from whereever you saved it. You won't get any confirmation of anything happening, but you also shouldn't get any error messages. Close the window when done.
6) Set up the connection to your bank like normal. Since all of your settings have been cleared, you should get the most recent connection information for your bank.
Hopefully, that will work. If it doesn't, let me know and we'll continue troubleshooting.
Jessica Little
Moneydance Support
6 Posted by david on Mar 31, 2011 @ 08:22 PM
Thanks. Just to be clear - this will remove the banking information for all my banks?
I just want to make sure I have all the right information on hand before I execute it.
Regards,
David
7 Posted by Jessica Little on Apr 02, 2011 @ 02:58 PM
Hi David,
Yes, it will remove all connection info. You'll need to recreate the connections for all of your banks after running this script.
Jessica Little
Moneydance Support
8 Posted by david on Apr 03, 2011 @ 11:59 PM
Hi Jessica-
This seems to have resolved the problem with Vanguard. Thanks for the help.
I hope this leads to identification of the bug in the program, as the utility you sent is a little extreme. Not surprisingly, in putting 16 other accounts back in for online banking, I fat fingered one and managed to lock myself out, necessitating password reset process, etc. Not the end of the world, but with the number of accounts involved, I was anticipating a glitch so it wasn't something I could do "in a free moment".
The bottom line is it was totally effective. The caveat to any of my peers facing the same issue, make sure you have all the passwords and configurations of those accounts you set up years ago and never had to touch since, and set aside time for reconfiguration of all your accounts.
Call it closed!
9 Posted by Jessica Little on Apr 04, 2011 @ 06:14 PM
Hi David,
Indeed, the need to use this file is due to a bug in Moneydance. However, I believe this bug has been fixed in Moneydance 2011, so hopefully in the future we won't need to resort to this blunt ax of a solution.
Anyway, I'm glad it worked for you. Please let me know if I can be of further assistance, and thanks for using Moneydance!
Jessica Little
Moneydance Support
Jessica Little closed this discussion on Apr 04, 2011 @ 06:14 PM.