ATFCU: Odd Error Message

Boatnmaniac

Last night during OSU I got an error code for ATFCU (Austin Telco Federal Credit Union). I think it was CC-800 but can't remember for sure. I tried Update Now and it returned the same error code so I then did Reset Account. Reset Account failed and deactivated the EWC connection.

I then did Add Account and that set up the download connection for my 3 accounts but I got the following error message even though transactions and account information were updated correctly. There was no error code.

This morning during OSU I got this same error message (no error code) even though the accounts updated correctly.

I searched Community but did not find any posts similar to this.

Is anyone else seeing this?

Quicken Anja

Hello @Boatnmaniac,

Thanks for posting about this issue!

Our teams are actively investigating this issue further as we are seeing this error occur across multiple different financial institutions and they would like you to try the steps provided below:

1. Run One Step Update (OSU) first to see if the issue resolves.
2. If the issue persists, rename the runtime.dat file located at: C:\ProgramData\Quicken\Inet\FILENAME\
   • (For example, add a 1 at the beginning of the file name so it reads 1runtime.dat.)
     
3. Run One Step Update again to check if the problem is resolved.
4. Close and reboot 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.

To assist in our investigation, please provide the following and let us know once you have done so:

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

Thank you!
(CBT-607)

UKR

@Quicken Anja ,

Shouldn't there be an additional step or two in these instructions? (See text in italics)

1. Run One Step Update (OSU) first to see if the issue resolves.
2. If the issue persists, close Quicken and rename the runtime.dat file located at: C:\ProgramData\Quicken\Inet\FILENAME\
   …
3. Start Quicken
4. Run One Step Update again to check if the problem is resolved.
5. …

Boatnmaniac

Thanks, @Quicken Anja. I was wondering at first if it might be a runtime.dat file issue but my recollection is that runtime.dat file issues will prevent the account(s) from updating and/or the last download date and/or the connection method will not be visible beneath the Account Name in the Account Register. In my case, the accounts updated and the last download date and the connection method are visible beneath the Account Name in the Account Register.

I did run OSU in a test file with these ATFCU accounts already set up in there and also added those same accounts to another test file. This error message did not come up. So, it does lend some credence to this being a runtime.dat file issue in the primary data file.

I will test for the runtime.dat file issue in the primary data file in a little bit and post the results back here.

Boatnmaniac

@Quicken Anja - I just finished renaming the runtime.dat file. I cringe whenever I need to do this with my primary data file because it does something that is not mentioned in your instructions and I forgot to mention that to you: It almost always requires all EWC/EWC+ accounts (not DC accounts) with all FIs to be Reset/Reauthorized. And even then the Reset/Reauthorization process does not always reconnect those accounts, again, requiring that the affected accounts be completely deactivated/reactivated.

The problem ATFCU accounts could not be reconnected with EWC via Reset Account and needed to be totally deactivated/reactivated. Reset Account was all that was needed for all of the other EWC/EWC+ accounts.

So, I learned something new: Another way to identify a possible runtime.dat file issue.

It seems to me that runtime.dat file issues started becoming a significant issue about 2 years ago even though it's been an on-again-off-again issue for many years prior to that as is evidenced by the relatively large number of posts about it in Community. I sure hope Quicken's engineers can figure out how to resolve this issue soon once and for all.

Boatnmaniac

https://community.quicken.com/discussion/comment/20481128#Comment_20481128

I used to do this as you suggested…close Quicken before renaming the runtime.dat file. But this time I thought I would try doing it without first closing Quicken. It seems to have worked fine so maybe closing Quicken first is not needed (or not needed anymore)?

Quicken Anja

@Boatnmaniac Thank you for following up and providing a very detailed update!

If you don't mind, please submit a problem report with log files and a sanitized file attached via Help > Report a Problem so we can attach it to the open ticket (regardless of whether or not those steps resolved the issue). I think that the information you shared would be useful to include in the ticket.

Thank you!

Boatnmaniac

https://community.quicken.com/discussion/comment/20481145#Comment_20481145

Sorry for the delay in replying. I got caught up on some other things and am just now seeing your request. I just now submitted the report, sanitized file and reports.

On a positive note for me: I had initially thought the problem occurred in my primary data file which was concerning. But it must have been a senior moment for me because I later realized it was in a test file that the issue occurred. And in that test file the fix is still effective this morning.

BK

I just finished renaming the runtime.dat file. I cringe whenever I need to do this with my primary data file because it does something that is not mentioned in your instructions and I forgot to mention that to you: It almost always requires all EWC/EWC+ accounts (not DC accounts) with all FIs to be Reset/Reauthorized. And even then the Reset/Reauthorization process does not always reconnect those accounts, again, requiring that the affected accounts be completely deactivated/reactivated.

@Boatnmaniac , Fortunately for me, deleting the runtime.dat file has always worked flawless where no account had to ever be reset/reauthorized, so this is the first time I learn about this probability (thank you). I thought such measure would yield a consistent result so maybe this is a rhetorical question but I wonder what it is that gives us such different experiences?

Boatnmaniac

https://community.quicken.com/discussion/comment/20481284#Comment_20481284

I found out about all of this a couple of years ago and that was captured in a Mar-Apr 2023 thread: Time date stamp [of last account update]. This thread also identifies some other ways to determine when a runtime.dat file corruption issue might be at play.

There was also another thread at that time where it was also determined that persistent CC-800 error codes that cannot be resolved via more standard troubleshooting methods are perhaps also caused by runtime.dat file issues and that replacing the runtime.dat file issues can often resolve them once and for all.

I think I must have commented in at least 15-20 threads over the last 2 yrs suggesting that the Op was having a runtime.dat file issue and the Op then reported that replacing the runtime.dat file resolved the issue for them.

What I don't understand is that runtime.dat file issues, based upon the prevalence of posts in Community, seems to me to be rather cyclical. Am I correct about this? And if so, what causes it to be cyclical?

BK

Re: cyclical?

You just might be onto something since I have seem multiple similar posts to your OP in the recent weeks. Such as this one that made me laugh. Perhaps Quicken/Intuit is doing something on purpose or not.

Speaking of the CC-800 errors: (sorry off topic) I used to be able to refer to a backup file without any issues, and then since about a couple of years ago I cringe every time I do, cuz I get the CC-800 error with a few accounts. Next time I have to resort to a backup, I will incorporate deleting the runtime.dat file as part of the process before opening it to see if it helps.