CC-601 Error - Fidelity Brokerage Accounts not updating.
Comments
-
The problem is not resolved.
0 -
CC 601 error issue has been happening since upgrading to Release R66.23. Has anyone checked to see if the previous release is having the issue?
I don't want to fall back on the release if the previous release has the same issue.
0 -
Where is the resolution status? what was issue? what was fixed? What steps are required if necessary to resolve? Quicken needs to provide the necessary detail to its community to understand how a problem, so consistent and critical with ts user base, has been corrected v.s everyone needs to call support. Are we talking about the same issue when we say it is resolved.
0 -
@shtevie That is a different issue then the one being discussed here. I know — it's very hard to keep track given the parade of bugs.
The CC-601 issues with Fidelity are definitely still there. What is so strange is that my original file still gets transactions from Fidelity with no issues — it's only my new data file that @Quicken Kristina had me create with a fresh copy with new connections that encounters this problem.
2 -
I just called support and the issue being discussed here, i.e. CC-601, is not resolved yet and they have no ETA.
0 -
@jeffrub27 Did they offer any more substance than what @Quicken Kristina said? "Not fixed, no ETA" is just not acceptable — especially after going on this long.
I wish we weren't all part of a captive audience with legacy data. Given how unstable Quicken has become and how often these issues come up with just this kind of response and delay, they deserve an exodus of customers.
0 -
-
@bdantes agree 100%. unfortunately this is what happens when a company has a captive audience. They sure do not seem to care about us much probably cuz we do not have much choice I guess.
The support guy was nice but poretty much said they have no idea what is going on, no ETA and no work around.
I'm on a chat with Fidelity to see if there is a way we can download QIF files so maybe we could get some data manually in the meantime.
1 -
Fidelity does not support QIF anymore, only CSV.
Has anyone had experience with Quicken Perl Wiz for converting CSV to QIF? (See below)
I may try it, but cannot tell if it is a repurable publisher or not. It is discussed on the Quicken website.
Perhaps we can download CSV files from Fidelity, and use this app to convert to QIF and then load into Quicken.
0 -
It looks like my post regarding Quicken being unreliable and the lack of proper testing before releasing changes to production has been deleted. Instead of deleting posts, how about fixing the problem. You should have your IT team working around the clock to resolve an issue of this magnitude. I am seriously considering dropping Quicken as it is of no use to me unless this issue is fixed. Where does Fidelity stand on this? I would think they would want their customers to be happy and not considering moving to another institution.
1 -
With all of these issues, having the ability to download .QIF files from the Fidelity web site so we can simply import our data into Quicken is definitely a necessary option that was available for years. It's still an option on other financial sites like banks and credit card companies. I'm not sure why this option was removed (either by Fidelity or Quicken) but we need to somehow convince both companies to re-instate it. Converting .CSV to .QIF would be cumbersome and not seamless.
0 -
Still waiting for a fix
0 -
@Quicken Kristina reports that trouble ticket 12255818 (similar to this issue) has been resolved. I just want you to know that it is not, in fact, resolved for me. No change. OSU login proceeds, seemingly without incident, but no transactions download.
0 -
Just tried to upload my Fidelity accounts into a new, clean Quicken file. After being asked for cash balances, the accounts were added but no transactions except opening balance. Then ran OSU one more time and got CC-601 error. Glad I didn't use my true Quicken data file !!!! This issue is NOT fixed
[Removed-Disruptive][Edited-Readability]
0 -
@Ain't Misbehavin Again, I think you may be referring to a different issue just as @shtevie was. The issue that is the subject of this thread is this — and @Quicken Kristina has definitely not marked it as resolved.
0 -
@spence288 Call Quicken phone support [Removed-Disruptive]
1 -
Thanks @bdantes, will contact phone support and ask for a supervisor and I encourage others to do the same. I am not looking for a refund, just dont feel I should be paying full price for a broken product.
Also these comments are NOT DISTRUPTIVE and sad to see the comment treated in such a defensive way. Frankly, this is how you escalate a critical issue inside a company where management is too far away from the product and have not prioritized support and SUSTAINING engineering. Just look at Windows!1 -
I am having same problem, CC-601, for all my Fidelity Accounts. Please add me to the list
0 -
Yes, I completely agree that the Quicken community moderators removing my comment about my history with support for getting extensions/refunds for issues as "Disruptive" is truly bad. Simply wow - seems like an effort to alienate customers even more.
In all fairness, I am impressed that Quicken maintains this bulletin board at all and generally allows critical comments as long as they are civil. That said, I think that last editorial action was extreme. I hope it was AI over-reacting — but if it was an actual human moderator, shame on them. We may be compelled to take honest feedback to a Quicken subreddit or similar if they edit like that.
0 -
I just spoke with Ian in Fidelity Electronic Channel Support - and he indicated that they are fully aware of the problem, that they have changed nothing on their end, at that your internal teams have told them what you have communicated: Quicken is working on it with no ETA. To be 100% clear — Fidelity feels the problem is entirely on Quicken's side (or possibly Intuit's). So this really emphasizes that there shouldn't be this kind of delay in diagnosing, sharing better detail, and fixing the issue.
0 -
Pretty sure this is a Fidelity choice. On Wells Fargo Advisors, I can export transactions in Quicken (.qfx) format. The downloading capabilities at Schwab do not include .qfx.
0 -
I don't think there is anything we can do except wait for a fix. We're stuck and have to put up with the poor communications and lack of empathy from the company that has a monopoly on this type of software.
I have gone the csv route for my "simpler" Fidelity accounts so I do not get too far behind and that works, but is very time consuming. All of my the Fidelity accounts are basically brokerage or investment accounts, but I have a few that are basically bank accounts, i.e. no equities, and I am loading transactions that way using the File > File Import > Banking Transactions > From CSV file. I have not tried the File Import > Investment Transactions yet because that will be more complicated with extra columns and such. I will likely hold out for the fix longer before trying that.
Fortunately my CC accounts are all working fine.
Fingers crossed ….
0 -
One of the weird things about this Fidelity outage is how it impacts only some users. My wife's file has this problem, but mine doesn't.
0 -
@GermanBlueRam Agreed — my original data file is working fine with Fidelity. It's only my new data file that @Quicken Kristina had me create from a fresh copy (for an unrelated issue) where I had to establish brand new connections that is having this problem.
0 -
Hi everyone,
Thank you for your patience. We understand how important it is for you to have a reliable connection, and resolving this issue is a top priority for our team.
The alert regarding “Fidelity Investments – Missing Transactions / Incorrect Balance / Missing Securities / Etc.” has been marked as resolved. If you are still experiencing difficulties, please contact Quicken Support, as they can provide guidance for handling issues related to Fidelity accounts.
The other alert, related to CC-601 / FDP-101, is still open. Our team is actively working on a fix, and we will notify you as soon as the issue is resolved so you can connect your accounts successfully. You can also bookmark the alert to stay updated on any progress or changes.
We sincerely appreciate your patience and understanding while we work toward a resolution.
Quicken Laura
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
Thank you for the message. I understand that engineering may be providing you with no further detail than what you have just written. But please pass on the message that updates lacking detail and with no firm ETA just compound the frustration — especially when the problems keep recurring and have gone on this long. The connections with Fidelity have been problematic since last July. EWC+ finally stabilized and reached parity with the original Direct Connect a couple of months ago, only to have this latest debacle that's now gone on over a week. Your users deserve better than this — at the barest minimum a detailed explanation of what is going on. From my and many others' perspectives, it appears that QA is entirely lacking.
0 -
If this is true: "To be 100% clear — Fidelity feels the problem is entirely on Quicken's side (or possibly Intuit's)"(From @Quicken Kristina) how could one explain that I can download Fidelity Elan VISA transactions fine from the Elan Financial site, but when I try to download them from Fidelity Investments I get the dreaded CC-601 error?
0 -
Elan may not be using EWC+ is one possibility, and the other is that Quicken or Intuit is interpreting Elan’s data differently than Fidelity’s. But all I can say is that Fidelity asserts they’ve changed nothing and that Quicken told them it was in Quicken’s side. Given that I and other users have one Quicken file without the problem and another with - using the same Fidelity feed — strongly points at a Quicken bug.
But all of this hand wringing and supposition would be unnecessary if Quicken would provide substantive triage feedback.0
Categories
- All Categories
- 52 Product Ideas
- 34 Announcements
- 247 Alerts, Online Banking & Known Product Issues
- 20 Product Alerts
- 514 Welcome to the Community!
- 680 Before you Buy
- 1.5K Product Ideas
- 55.6K Quicken Classic for Windows
- 16.8K Quicken Classic for Mac
- 1K Quicken Mobile
- 832 Quicken on the Web
- 126 Quicken LifeHub