BMO Private Bank OL 297A since January

Bullwinkle80
Bullwinkle80 Quicken Windows Subscription Member ✭✭

Hello! I haven't been able to download any transactions since January 15th for my BMO Private Bank account. Using Quicken Classic latest version. I tried all the online help on that error including the tip Quicken gave me with resetting IE. I tried a new dummy account to connect and get the same error. Any ideas? Thanks

Comments

  • Quicken Anja
    Quicken Anja Moderator mod

    Hello @Bullwinkle80,

    We appreciate you taking the time to bring this issue to our attention!

    To confirm is the instance shown below the one you are using to connect?

    Also, are the troubleshooting steps outlined in this support article the ones you have tried so far? Please confirm.

    Thank you!

    -Quicken Anja
    Make sure to sign up for the email digest to see a round up of your top posts.

  • Bullwinkle80
    Bullwinkle80 Quicken Windows Subscription Member ✭✭

    Hi! Yes, that is the bank I am trying to connect. And yes, I tried the support article on the error with no success.

    Thanks!

  • Quicken Anja
    Quicken Anja Moderator mod

    Thank you for getting back to me and for confirming! Since the troubleshooting steps in the support article did not resolve the issue, the next step will be to contact your financial institution directly.

    As mentioned at the bottom of the article I previously linked, Quicken does not have access to the financial institution's servers to correct this issue, so their support team will need to investigate further. I recommend asking to speak with an online services specialist who handles transaction download issues. If they are unable to assist, you may need to request an escalation within their support team.

    Thank you!

    -Quicken Anja
    Make sure to sign up for the email digest to see a round up of your top posts.

  • Bullwinkle80
    Bullwinkle80 Quicken Windows Subscription Member ✭✭

    Thank you! I did contact them about this connecting problem last month and they claim it was entirely a Quicken problem. I'll escalate the issue up the chain of command there.

    Thanks