I have two data files accessing the same accounts. The first I created in 2010, RJF2b. It has some issues, so I created a new file from scratch in 2023, RJF2023. One Step Update (OSU) uses the same logins to the 9 institutions to update the 21 accounts. I need to keep updating both files as I’m still debugging reports, memorized transactions, etc.
On May 6, as usual, I updated RJF2b. When I updated RJF2023, most institutions failed OSU with CC-901 errors. I repaired its connections. When I again ran OSU on RJF2b, it failed. Repairing one file corrupts the other file. As I tried to fix the failures, they changed to CC-601. Both files pass Validation and Super-validation. My Mobile and Web Apps are off.
Quicken support couldn’t fix both files either. (5/7/2025 Quicken case # 11756126)
Reading through the Community posts, I see many discussions on OSU failures, a few with those trying to have two data files sharing accounts. OSU is a major and continuing issue.
Fidelity uses Direct Connect and is ok. Institutions using Express Web Connect fail. They download data from the institution to Quicken’s servers. OSU downloads the data from these servers to Quicken desktop. Seven institutions use Express Web Connect+ authenticates with tokens. Barclays uses Express Web Connect authenticates that authenticates with my user’s ID and password. As data is read-only, I don’t see any technical issues using multiple files. Downloading from the institution as a CSV file isn’t a problem, nor is using Direct Connect. I suspect it’s caused by overzealous security.
Has anyone had this same issue? Have you found a solution?