Update to MD 2011r2 (803)
Just updated to subject release from original MD 2011. Now get the following error when connecting to JP Morgan Retirement Plan Services:
"There was an error communicating with your financial
institution. The details of this error are below Bank Name: J.P.
Morgan Retirement Plan Services
The error code reported by the server was: 2020
Invalid date"
If I reset sync in online setup; I can download once before
getting the error again.
I have tried disabling the online settings and then setting up
again. That works for one download
and then the error occurs again. Was there a change to financial
connections for JP Morgan. All other financial
institutions are working fine.
2 Posted by ashokac22 on 13 Nov, 2011 01:13 PM
I see the exact same thing. As Joe pointed out, removing and adding the connection back makes it work for that one time and then it throws out the error.
Support Staff 3 Posted by Jessica Little on 13 Nov, 2011 07:07 PM
Hi,
If you would be willing, could you send me the contents of your error console? Ideally, if you could send logs from both the first successful connection and the second failed connection, that would be most helpful. Here's how to get the logs:
1) In Moneydance, click on the Help menu and select the Console Window option. This will open the console messages window.
2) While the Console Window is open, attempt to connect to your bank. Any error messages should be recorded to the Console.
3) Select all of the text in the Console and use the Copy to Clipboard button at the bottom to copy the text.
4) Paste the text from the message window into a text file (preferably saved with a .txt or .rtf extension) and email that file directly to me at jessica @ moneydance.com.
Do not attach the file to your response here, since this thread is public and the logs will contain your account information. To be safe you should redact any account info in the debug logs. Just replace it with something like ACCOUNT NUMBER HERE and it should be fine.
Jessica Little
Moneydance Support
Support Staff 4 Posted by Jessica Little on 14 Nov, 2011 07:11 PM
Hi all,
Thanks for the logs you sent Joe. I took a look at them and am not sure why the JP Morgan server is rejecting the date. I've asked a few of our other support staff to take a look to see if they have any ideas, and I'll let you know what they say.
I'd like to figure out if this is an issue with the Moneydance update or if it's a server problem. Could you please try downgrading to 2011r1 to see if that resolves the problem? If you don't have this issue in Moneydance 2011r1, then we know that the problem is with the r2 update. You can download r1 from our website at: http://moneydance.com/download/2011-791/
Jessica Little
Moneydance Support
5 Posted by Jimmy S on 14 Nov, 2011 07:28 PM
I hate to chime in with a idea that may be WAY off, but it occurs to me that JP Morgan is actually JP Morgan Chase. I mention this only because I am having issues downloading from Chase (I posted this in another thread) Could my issue with Chase be related to this issue with JP Morgan?
Support Staff 6 Posted by Jessica Little on 14 Nov, 2011 07:39 PM
Hi Jimmy,
I don't think that is the issue, since it's at least possible to connect to the JP Morgan server while the Chase server isn't even turned on. However, it may be the case that this weekend's server maintenance somehow affected the JP servers as well as the Chase servers. It might be worth calling up JP Morgan to report the issue and see if they know anything about it.
Jessica Little
Moneydance Support
7 Posted by Joe LG on 14 Nov, 2011 09:01 PM
Jessica,
I went back to 2011r1 and had no problems doing multiple downloads with JP Morgan.
Support Staff 8 Posted by Jessica Little on 15 Nov, 2011 03:28 PM
Hi Joe,
Ah...at least now we know where the problem is. Could you send me the logs from your connection in r1? Hopefully, I'll be able to spot the difference and fix whatever bug we introduced in r2.
Jessica Little
Moneydance Support
Support Staff 9 Posted by Jessica Little on 25 Jan, 2012 04:45 PM
Hi All,
I believe we may have fixed this issue in Moneydance, but I need folks to test it to be sure. If you're willing, could you please install build 806 of Moneydance 2011 and try your connection again? You can download the daily from our website at: http://moneydance.com/tmp/daily/installers/806/
Hopefully, this build will allow you to connect without the errors.
Jessica Little
Moneydance Support
Support Staff 10 Posted by Jessica Little on 25 Jan, 2012 08:24 PM
Hi All,
I forgot to mention that, in order to test this fix, you'll need to reset your connection to the bank. I'm sending a file called remove_one_service.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 Manage Extensions option.
2) From the list of available extensions, choose the python scripting interface extension, then click Install to download the extension and finish to complete the installation.
3) Close the Manage Extensions window.
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 will be asked to select which connection you want to clear. Choose your bank, and click OK. You'll get a confirmation message when the connection has been removed. 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.
Jessica Little
Moneydance Support