Citibank - Citi Cards OL-209-B Errors

cjim

A few days ago I started having Citibank download errors. I have 3 Citibank Gold credit cards. Downloads have been working great for many many months. Then 1 of the 3 cards started getting OL 209-B errors on download. Today it continued so I tried some troubleshooting. Reset did not solve the problem. Deactivate/Activate did not resolve the problem. I even removed and re-added the third party application authorization for Quicken in my online Citibank account and I was able to re-connect the 2 cards that were working before but not the card that is having issues. So still no resolution. All 3 of my Citibank cards are the same type. Only difference are the numbers. Why 2 work just fine and 1 does not is very strange. Quicken please help resolve this. I am running Windows R43.14.

Quicken Anja

Hello @cjim,

Thank you for reaching out to the Community and telling us about your issue, though I apologize that you are experiencing this.

If you haven't already, please take a moment to review and follow the error-specific troubleshooting instructions found in this support article regarding error OL-209.

I hope this helps!

cjim

Thank you for the quick response @Quicken Anja. I should have mentioned in my original post that I had already tried those steps in the support article you pointed me to. I have plenty of free space on my disk and I have minimal temporary files in my temp files folders. Any other suggestions? Citibank has been of no help and is pointing me back to Quicken for resolution.

Quicken Anja

Thank you for following up.

With this specific error, if the troubleshooting instructions fail to resolve the issue, we do advise reaching out to the financial institution for further assistance. If they state they cannot assist, then an escalation with the financial institution would be required. As stated at the bottom of the article:

• If the steps above do not resolve the issue, you will need to contact your financial institution.  Quicken does not have access to the financial institution's servers to correct the problem. This may require you ask 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 the financial institution may be necessary.
  
  

If you wish to, you are welcome to also contact our Quicken Support team first. They can pull and review your log files for you and will be able to provide you with the information that your financial institution will need. However, please be aware that after contacting our support team, you will likely be referred back to contact the financial institution.

Thank you!

cjim

@Quicken Anja - just wanted to provide an update on this issue. Over the past many days I have, off and on, been in contact with Chase support. While they have been very nice and have spent time with me trying to help the bottom line is that they have not been able to help. They say there is no problem on their side and continuously pointed me back to Quicken. They also referred me to some of the same posts from this Community Forum that I had already read. In the end I did get it to work on my own. The solution was to abandon "Direct Connect" and reconfigure using "Express Web Connect". It is my understanding the Express Web Connect is not as secure as Direct Connect so this is not my desired solution to the problem but at least I am functioning again. In the mean time I hope Quicken investigates this issue further as I cannot be the only one experiencing this. I am also not convinced that this is Chase only issue.

cjim

@Quicken Anja - Can you please comment on the issue I described above. I am now also experiencing the same issue with Wells Fargo. Direct Connect will not work for me anymore with Citibank and Wells Fargo. I am having to switch to Express Web Connect in order to download transactions.