Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO
Chase Direct Connect error (QWIN) OL 294/ (QMac) HTTP-504
This discussion has been closed.
Answers
Not sure that was progress...
Question: Has anyone logged into Chase and checked their settings to allow Quicken and Chase to work together, for their Accounts? This setting is not Global in nature. Every User must do this.
Windows 10 Pro 32 & 64-Bit Build 21322.1000
also Windows 10 Pro 64-Bit Build 19042.804
Note: Product What's New in Quicken is grayed out.. Also Year is stuck on 2020 and Copyright Date is stuck 2018 in About Quicken.
View: https://community.quicken.com/discussion/7859218/work-with-copies-of-your-actual-quicken-data-files/p1?new=1
I just checked my "Desktop Software" option on Chase Website (not it is not "Desktop App" as you mentioned above) and I am already enabled. So that is not the cause of my Chase OL-295-A errors today.
Note to my earlier post on resetting one of my accounts: the error for that account changed to OL-297 when I tried to download again. Surely a temporary glitch, but it is unusual that it has stretched to the work week (Monday), at least for me.
Quicken for Windows subscription. Quicken user since 1990.
> Question: Has anyone bother to read this thread, before posting?
>
> Question: Has anyone logged into Chase and checked their settings to allow Quicken and Chase to work together, for their Accounts? This setting is not Global in nature. Every User must do this.
I sure did. Next suggestion?
Adding- deactivate/re-activate is not necessary; it works because Branding/Profile update is forced as part of the process. The link steps are usually simpler and quicker.
https://www.quicken.com/support/server-issue-troubleshooting
This time I selected one of the credit cards and refreshed and it worked for all four accounts.
Not sure why it would make a difference between banking accounts and credit card accounts but this fixed it for me.
So it wasn't your choice of accounts, Refresh would have worked regardless of the account selected at any point after the error state changed to OL-295.
adding- @Bob. Same response; the Refresh would not have worked until after Chase fixed the server. Refresh updates Quicken to match the requirements for connecting to Chase's updated server. The process happens periodically behind the scenes so the issue would have resolved magically soon enough; Refresh forces Quicken to do it now.
So I didn't have to do the refreshing to get it working for me.
BTW it is normal for it to go through getting the financial institution information for each financial institution (but usually it is almost to fast to even see). If have never really understood why they have to "force it" at times.
CP_ACCOUNT_NOT_FOUND
This after many years of downloading updates ok.