on 26 Nov, 2019 02:30 PM
Thanks for the reply.. I was able to follow the steps you mention
below. It took a while to figure it out with a little help, but even
after successfully getting the secure message and confirming my identity
I continue to experience the same error message from within MD
indicating that the bank does not allow the login. Apparently MD had
previously emulated Quicken's protocol, but perhaps the bank now has a
way to specifically identify Quicken vs MD as the software attempting to
connect. They, the bank, claim only to support Quicken users. Is it
possible some developer on your end could confirm the emulation
requirements with Chase? I previously had been able to connect when I
was a Quicken user, and yes I had the bank disconnect that setting
before trying to reconnect through MD. Appreciate any words of wisdom
on this. I have spoken to bank 4 times on this issue with them claiming
basically that MD is not supported (despite any success previous? to
other MD users?)
Maddy on 26 Nov, 2019 02:39 PM
Firstly, according to your description, it appears third party access has been enabled on the Chase site. Therefore, I wonder if you've definitely checked for a message within the Secure Message Inbox on the Chase site.
This is a crucial step. Then you should be able to confirm the connection from within the message before you can connect from Moneydance.
Secondly, can you try completely resetting your connection to your bank and see if that fixes the problem you're seeing?
To do this, you'll need to force clear the current connection information for your bank in Moneydance. I'm sending a file called 'remove_one_service_2017.py' that will help do that.
Before proceeding, take a manual backup via File --> Export Backup.
To use the .py file, first save it to your computer and then follow these steps:
In Moneydance, select Window --> Python Scripting (Choose 'MoneyBot' if you're using the 2019 version).
In the window that opens, select 'Open Script' then navigate to the .py file wherever you saved it on your system.
Select 'Run' to execute the file.
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.
Set up the connection to your bank like normal choosing the "New Connection" button. Since all of your settings have been cleared, you should get the most recent connection information for your bank.
Finally, if the previous steps do not lead to a solution, could you send us the contents of your error console? 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 extension) and attach that file to your response here.
The debugging logs that this produces will contain your account information. I've made sure that this conversation is private, so the info won't be broadcast to the world, but just 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.
Maddy on 27 Nov, 2019 02:17 PM
Sorry to hear that the problem persists, Craig!
Please can you let us know what’s happening when you click the secure message to confirm your identity? You should see a message that states your identify has been confirmed. You should not be taken back to the home page portal without any messages.
Some customers have reported the link on the Chase site isn’t working, as expected and no confirmation is being shown.
Also, which web browser are you using, and do you have any other web browsers on your system that you can try with?