Maddy on 13 Sep, 2021 09:22 AM
We are sorry to hear about the problem you have encountered.
As I mentioned in my earlier post (1) on this thread this is a generic Internal Server Error meaning that the bank might be making some changes at their end. Did you try asking the bank what sort of changes are they applying?
Also, could you let us know which version of Moneydance are you running?
To check, open Moneydance and select Help/Moneydance --> About Moneydance, where the version and build number will be displayed.
Did your try recreating or refreshing the connection by navigating Online Banking -> Set Up Online banking, then clicking the Reset Sync button?
Finally, you could try creating a new data set in Moneydance by going to File -> New, then try setting up your connection in that new data set and see if you can download your data then?
Jenny on 15 Sep, 2021 12:25 PM
We've made a change to the T. Rowe Price Retirement connection, which will hopefully resolve the problems you're seeing.
The new connection details are available for you to use in Moneydance now.
You should try to recreate the connection with your bank. You will need to disable your current connection and then recreate it using the New Connection button on the Online Banking Setup screen. To do so, you can follow these steps:
Select your bank account in Moneydance
Select Online > Setup Online Banking
Click the "Disable" button. If you don't see this button, just close the window.
Repeat the previous steps for any additional accounts at the same institution.
Select Online > Setup Online Banking (again)
Click the "New Connection" button and select your bank and hit OK
Continue with the setup process, entering your username/password
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 long list of available banks will force Moneydance to download the updated information, which should then allow you to connect.
Please let us know if you continue to encounter problems after recreating your connection and we'll troubleshoot further.