TFCU error OL-393-A since 9/13/2022

DoroV
DoroV Member ✭✭
Getting error OL-393-A on TFCU one-step-update and individual account update, quicken version R43.6, build 27.1.43.26 since approx. 9/13/2022. When will this be resolved? Thx

Answers

  • Hello @DoroV

    Thank you for contacting the Quicken Community, though I do apologize that you are receiving this error with your Tinker Federal Credit Union account(s). 

    I have located a support article that discusses some troubleshooting steps to take when presented with an OL-393-A error. You may follow this link to access that FAQ. Please keep in mind that it is recommended to save a backup before proceeding (just in case). 

    I hope this helps!

    -Quicken Jasmine

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

  • DoroV
    DoroV Member ✭✭
    Thanks for your reply. its Tower Federal Credit Union and I had performed those steps already and in additon contacted my bank. They said is nothing on their end. Is the problem seems to be on Quicken's end, whether that is my install or the Quicken servers. Can you look into this option? thx
  • DoroV
    DoroV Member ✭✭
    PS. I tried the deactivation and reactivation and got the message "sorry its not your fault, quicken cannot connect to your bank". Please advise.
  • Hello @DoroV

    Thank you for providing more information and for attempting those troubleshooting steps. 

    We recommend that you contact Quicken Support directly for further assistance as they can walk you through troubleshooting steps in real-time and escalate the situation if needed. 

    The Quicken Support phone number can be found through this link here. Phone support is available from 5:00am PT to 5:00pm PT, Monday through Friday.

    Thank you. 

    -Quicken Jasmine

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

  • DoroV
    DoroV Member ✭✭
    Hi Jasmine, thanks so much for your help. All worked again today before I even contacted Quicken Support. Seems that the problem was in fact with Quicken and must have been resolved on that end. thanks again for you assistance and advice.
This discussion has been closed.