5/10/2022 Chase - OL-393-A

Does anyone know what's going on with this error with Chase?  I've 2 logins, one works just fine, the other - for the last 24 hours or so, has this error.    Is there anything I can do on my end to fix it?  I've been using QW for many years with Chase.

Answers

  • Sherlock
    Sherlock SuperUser ✭✭✭✭✭
    If you haven't already, you may want to review: UPDATED 5/10/2022 Chase - OL-393-A
  • pbug56
    pbug56 Member ✭✭✭
    I did.  Doesn't really say anything.  After a few days you'd think they would have some idea.  And since you can't email them, outside of their hours there is no way to reach them, to add yourself to the list of people having the problem.

    I am hoping that someone can at least explain the problem in plain English.  Right now, all I get out of what Quicken says is that it's broken!  


  • pbug56
    pbug56 Member ✭✭✭
    Oh, and as far as I can tell, their offer to notify you consists of providing you some sort of mystery bookmark.
  • Sherlock
    Sherlock SuperUser ✭✭✭✭✭
    pbug56 said:
    I did.  Doesn't really say anything.  After a few days you'd think they would have some idea.  And since you can't email them, outside of their hours there is no way to reach them, to add yourself to the list of people having the problem.

    I am hoping that someone can at least explain the problem in plain English.  Right now, all I get out of what Quicken says is that it's broken!  


    You can read the plain English causes of the error message at: https://www.quicken.com/support/error-when-using-quicken-online-services-ol-293-or-ol-294

    Basically, Chase broke their Direct Connect service and Chase is working to fix it.  You may certainly call Chase, if you want to vent your frustration.
    pbug56 said:
    Oh, and as far as I can tell, their offer to notify you consists of providing you some sort of mystery bookmark.
    The bookmarking of the announcement in the community is no mystery.  When a Quicken moderator updates the announcement, you should receive a notification if you have checked the Notify me when people comment on my bookmarked discussions notification preference at: https://community.quicken.com/profile/preferences/
  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    The announcement also told how to workaround/fix the problem if in fact you aren't using Bill Pay through Chase.
    Signature:
    (I'm always using the latest Quicken Windows Premier subscription version)
    This is my website: http://www.quicknperlwiz.com/
  • pbug56
    pbug56 Member ✭✭✭
    Direct Connect Bill Pay is not turned on - I don't use Bill Pay.  Direct Connect, sure.
    When I went to report an error, all I saw was chat or a phone number, not usable at night.
    Thanks for pointing to the notification pref page - I had no idea it existed.  I've never seen the 'ribbon' before.
    Account settings did not change in the last day or two - they've worked for years.
    A second account with a separate login works normally.
    Some accounts at other institutions have a key symbol - this does not.
    I did Update Now a few times.
    I did reach out to the bank, but it usually takes several days before they respond.
    Whose server would be having the problem if it is a server problem?
    I also logged into my online account - that works normally.
    QW is up to date.

    So yes, I do find this baffling.  The instructions feel more like a pacifier than a way to fix anything.  And the error like one of the mystery errors that pop up from time to time with no viable explanation.  I've been a Quicken user for exactly 20 years - to the day.  I spent decades in IT as a developer, etc.  I'm a former beta tester for QW, as well.

  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    @pbug56 This is a Chase problem, but if you aren't using Bill Pay then turning it off will get rid of it reporting the error.  BTW in fact even though it reports an error the updates do happen.

    To change the setting right click on the checking account (the one that has Bill Pay ability) in the Account bar and select Edit/Delete account -> Online Services tab, and select the Deactivate on the Bank Bill Pay line.  Note that this is turn on automatically when you first setup for Direct Connect.
    Signature:
    (I'm always using the latest Quicken Windows Premier subscription version)
    This is my website: http://www.quicknperlwiz.com/
  • pbug56
    pbug56 Member ✭✭✭
    Understood.  I never used Quicken bill pay, but found one of the 2 options turned on.

    How long should it take to clear up?

    Thanks!
  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    pbug56 said:
    Understood.  I never used Quicken bill pay, but found one of the 2 options turned on.

    How long should it take to clear up?

    Thanks!
    There is no telling how long it will take, if you bookmark this thread, you should get notified when they announce that it is fixed:
    https://www.quicken.com/support/error-when-using-quicken-online-services-ol-293-or-ol-294
    Signature:
    (I'm always using the latest Quicken Windows Premier subscription version)
    This is my website: http://www.quicknperlwiz.com/
  • pbug56
    pbug56 Member ✭✭✭
    Let me rephrase.  After one turns off all bill pay options, how long should it take before that no longer generates the error?  "This is a Chase problem, but if you aren't using Bill Pay then turning it off will get rid of it reporting the error."
  • Damian
    Damian Member ✭✭✭✭
    @pbug56 - you mentioned in your OP that you had two logins.  Just a guess on my part but if you have multiple accounts at Chase, they all need to have billpay turned off.
    (Quicken Premier Subscription R40.21 on Windows 11 Pro)
  • pbug56
    pbug56 Member ✭✭✭
    The 2nd login works normally, no errors.  And it had both bill options turned off.
  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    Turning off bill pay in Quicken for Chase should immediately stop the error (as in on the very next One Step Update). 
    Signature:
    (I'm always using the latest Quicken Windows Premier subscription version)
    This is my website: http://www.quicknperlwiz.com/
  • pbug56
    pbug56 Member ✭✭✭
    I exited QW, restarted in case that would hep.  Ran Update again, transactions come through as expected, but error message did not go away.  I did REPORT in the hope that might help.