Citi Bank Message Error

allgoodnamestaken

For the past two months I get the following error message:

"Citi Cards

Citi Cards is reporting connection issues.

The associated accounts can't update right now,

We are investigating the issue."

Except Citi is downloading all transactions accurately. More of an annoyance than a concern, unless it indicates some pending issue. Is anyone else seeing this message?

Quicken Alyssa

Hello @allgoodnamestaken,

Thank you for sharing your experience.

This is a known issue and is under investigation. We currently do not have an ETA for resolution. Some users have reported that the steps below have resolved this error for them:

1. Run One Step Update (OSU) first to see if the issue resolves.
2. If the issue persists, close Quicken
3. Using Windows File Manager to rename the runtime.dat file located at: 
   C:\ProgramData\Quicken\Inet\FILENAME\ where FILENAME is the name of your current Quicken data file, e.g. My Quicken Data 2024 as seen in the image below. There usually is an \Inet\… subfolder for each Quicken data file in existence.
   • (For example, add a 1 at the beginning of the file name so it reads 1runtime.dat.)
4. Start Quicken and run One Step Update again to check if the problem is resolved.
5. Close and restart Quicken to ensure changes take effect.

📌 Note: The ProgramData folder is hidden by default. If you need help accessing it, Microsoft's support site has instructions on how to unhide folders.

Since this is considered a known issue, particularly with Citi, and has been escalated internally, you can assist in the investigation by providing the following info listed below.

• Logs (Help > Report a Problem)
• Screenshots (excluding personal data)
• A sanitized copy of your Quicken data file (with personal details removed)

If you do send logs, let me know so I can add you to the ticket.

Thank you!
(CTP-14158)

BK

@allgoodnamestaken

In a post, specifically this comment, I found an unconventional method or workaround which might help you. I have had this issue since early June, and with the workaround I have been error free for a month now! Good luck and please let us know.