Chase Bank- error
All of a sudden I have started to receive the attached error when I try to download txns from my Chase Credit Card. ANy insight as to why this may be happening?
Thanks
-
Capture.JPG 25.6 KB
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 David Hanley on 08 Feb, 2016 04:42 PM
Hi Scott,
Can you please verify the exact build version of Moneydance you are running? To do this run Moneydance and from the menu bar select Help->Console Window... Then copy and paste the output of the console window to this discussion.
Can you try re-creating your connection with your financial institution and see if that fixes the issue that you're seeing? You will need to disable your current connection to your bank and then recreate it using the New Connection button on the Online Banking Setup screen. To do so, you can follow these steps:
Make sure you pick new connection, even though your bank is still one of the connection choices after you disable it. Choosing your bank from the list of available banks will force Moneydance to download the updated information, which should then allow you to connect.
Please let me know if you continue to have connection problems after recreating your connection.
David Hanley
Infinite Kind Support
2 Posted by sobo1 on 08 Feb, 2016 04:48 PM
David-
Thanks for the quick note back- that solved it! Not sure what the issues
but resetting the connection fixed it.
Thanks!
3 Posted by David Hanley on 08 Feb, 2016 04:57 PM
Hi Scott,
Glad to hear that worked! Resetting the connection allows Moneydance to download updated connection certificates from Chase. This has been coming up a fair bit lately as they've been trying to nail down security tighter.
Please feel free to contact us for any future support!
David Hanley
Infinite Kind Support
David Hanley closed this discussion on 08 Feb, 2016 04:57 PM.