Communicating with my bank
Ever since I upgraded to snow leopard I can no longer communicate with my bank. I keep getting a java error.
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 Brian Adler on 25 Sep, 2009 02:54 PM
Wayne,
Are you using our most recent Moneydance build available here:
http://moneydance.com/preview
Can you paste the specific java error you are receiving? Also, to which bank are you trying to connect?
Sincerely,
Brian Adler
Moneydance Support
2 Posted by Jeremy Martin on 25 Sep, 2009 11:07 PM
I keep getting the same problem. Trying to connect to Bank of America.
It keeps saying the connection is closed
There was an error communicating with your financial institution. The details of this error are below.
There was an error communicating with the server. This could be the result of a network problem, or the server may be offline or not responding. Please try the operation again later.
Error Description: java.net.SocketException: Connection reset
3 Posted by Jeremy Martin on 25 Sep, 2009 11:07 PM
Forgot to mention I did download build 642
4 Posted by Dave K on 27 Sep, 2009 11:08 AM
I am having the same issue on Snow Leopard. I'm running build 643. But when I try to download from TD Bank I get:
There was an error communicating with your financial institution. The details of this error are below.
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:404 Not Found
5 Posted by Dave K on 27 Sep, 2009 11:09 AM
Chase account downloads give me this message:
There was an error communicating with your financial institution. The details of this error are below.
The error code reported by the server was: 2000
We are unable to connect to the website at this time. Please try your request again later.
6 Posted by Brian Adler on 27 Sep, 2009 08:15 PM
Jeremy,
I use BofA with the latest build of Moneydance and Snow Leopard. Are you sure that your account is already enabled for direct connect?
Dave,
The issue with TD Bank cannot be resolved until TD Bank and TD Banknorth are merged into a single connection. It is my understanding that that is going to occur very soon. Has Chase worked for you in the past? Are you sure you have been enabled by them for direct connect? I believe that Chase issue distinct login information once an account has been enabled.
7 Posted by Brian Adler on 27 Sep, 2009 08:18 PM
If any of you are continuing to have an issue with your connection, please install this debugging tool and we will determine the cause. Be sure to redact any personally identifying information,
To install our debugging extension:
1) Download this file:
http://moneydance.com/preview/miscdebug.mxt 2) Select the Extensions->Add Extension menu and select the "From a File" option
3) Select the miscdebug.mxt file downloaded in step 1, and continue to install the extension
4) Select the Extensions->Moneydance Debugging Helper menu. This displays a window that will capture any error messages and OFX messages.
5) Attempt to download transactions until the error occurs
6) Select all of the text in the error message window and use command-C (ctrl-C on win/linux) to copy the text
7) Paste the text from the error message window into a response to this message.
8 Posted by Jeremy Martin on 27 Sep, 2009 08:33 PM
He Brian,
I think the issue was on BofA's side. It worked this morning.. Thanks for looking into it though.
9 Posted by Wayne Albritton on 27 Sep, 2009 08:49 PM
Brian,
That solved the problem. Thank you very much.
Wayne Albritton
10 Posted by Dave K on 28 Sep, 2009 02:20 PM
Brian:
Is the TD bank issue a new one? I originally came to TD as a Commerce Bank customer. The download worked without nay problems for me pre-Snow Leopard. But now it seems to be broken completely.
The Chase problem must have been temporary. I can now download without trouble.
11 Posted by Brian Adler on 30 Sep, 2009 01:14 PM
Dave,
TD Bank is currently upgrading their system. You will be unable to connect to them through Moneydance (or any other personal finance software) until after September 29th (and perhaps a little longer). We have already updated our database with the new "TD Bank Online Banking" connection. Note that this is different from the current TD Bank connection we have in our database that has a dash in it. Once their upgrade is complete, you will need you disable your old connection to TD Bank and create a new connection to TD Bank Online Banking.
You can find more information about their upgrade at their website. I'm sorry for the temporary down time. Hopefully the upgrade will go smoothly and you'll be able to connect again soon.
Sincerely,
Brian
Moneydance Support
12 Posted by Dave K on 30 Sep, 2009 01:20 PM
Brian,
Thanks for the reply. I understand, it's completely out of your hands.
13 Posted by johnmitola on 15 Oct, 2009 11:27 PM
Please help!!!! I am having the same problem with BofA but I can't open the debugging tool. Is it because I have not loaded the new version of leopard? I haven't changed anything on my Moneydance or Mac but all of a sudden I can't connect to my BofA accounts. Getting the same java error as described above.
14 Posted by johnmitola on 15 Oct, 2009 11:30 PM
Please help!!!! I am having the same problem with BofA but I can't open the debugging tool. Is it because I have not loaded the new version of leopard? I haven't changed anything on my Moneydance or Mac but all of a sudden I can't connect to my BofA accounts. Getting the same java error as described above.