Washington Trust - OL-393-A

John54

Is this Quicken issue or the Washington Trust Bank (RI) banks?
Already tried support article.
Ends with: The Washington Trust Company: Invalid FID sent in request [OL-301-A]

Quicken Anja

Hello @John54,

Thank you for reaching out to the Community to tell us about your issue and stating that you have already tried the steps found in the support article regarding error OL-393, though I apologize that you issue persists.

However, as stated at the bottom of the article, if the issue persist you will need to contact the financial institution for further assistance:
"You will need to contact your financial institution for assistance. Quicken does not have access to the financial institution's servers to be able to correct the problem.

This may require you request to speak with an online services specialist that handles transaction download issues at the financial institution. If your financial institution states they can't assist, an escalation with them may be necessary."

Thank you!

Stormpix

I'm having the same issue with Royal Credit Union in Wisconsin. It started about 2 days ago, prior to which things had been working fine for months. I've contacted RCU and nothing has changed on their end, so I suspect it's a Quicken Issue.

SheilaM

I am seeing this with Redstone Federal Credit Union since Friday, so pretty sure this is a Quicken issue and not a financial institution issue.

John54

I plan to speak with Washington Trust Bank in the morning.
I will let you know how it goes

Zortrium

I started experiencing this issue with three different CUs at exactly the same time a few days ago (all different from those mentioned upthread). All have the same online banking interface so virtually guaranteed it's a Quicken backend issue rather than a FI-specific issue. Please get this fixed ASAP -- it is clearly a very widespread problem.

Zortrium

Also worth mentioning -- I'm not on Windows at all (so, again, points to a server backend problem).

rbcollins

This began happening to me on Friday after the most recent update auto-installed, on my account with Delta Community Credit Union.
The timing and the fact that it is happening with multiple financial institutions certainly looks like a problem with Quicken.

John54

This morning I'm getting OL-292-B error when trying to update Washington Trust bank.
Went through the procedure: https://www.quicken.com/support/error-when-using-online-services-ol-292 and still getting OL-292-B error. Trying the bank next.

John54

Just got off the line with my bank (Washington Trust) They do not see any problems on there end.
They show no login attempts, failed or otherwise since 9/16/22. I have made multiple attempts over
the weekend without success.
This appears to be a Quicken issue.

Please get someone on this to resolve.

Thank You
John54

dc0063

In reading the 393a error message for both Delta and Tower, which coincidently both occurred as of my Friday update and have continued, show a bad FID and the connection was rejected. Since the connection is rejected, there is no failed login or record at the FI.
So, since many CUs have suddenly failed for a bad FID, it points to a failed file update or server configuration.
As no one has indicated the connection method they are using, it's difficult to assess blame. However, with the Direct Connect change coming in a week and Intuit even more involved as a data conduit, it would seem Intuit the likely culprit.
Quicken, please stop sending us to the FI since they have no log entries. Instead look for issues that would cause multiple, aligned FI to fail at the same time. If Quicken, we understand just fix; if Intuit, the relationship must become closer and stronger for the sake of the community and product's future.

pistolpete

Well, I was having this same issue w/ Delta Community Credit Union this am and now it seems resolved?

dc0063

Confirm Delta and add Tower to the resolved.
Quicken, thank you

John54

Washington Trust is now working

Divine Intervention perhaps?

John54