nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Wells Fargo CC-501 error code

reigninslayer

Anyone else receiving the CC-501 error code when attempting to connect and download transactions from Wells Fargo? First time seeing this error on Windows and I usually have no issue connecting.

Find more posts tagged with

Known Issues

Windows

QWIN - Mobile/Web Sync

Known OLB Errors

Comments

Quicken Jared

reigninslayer said:

Anyone else receiving the CC-501 error code when attempting to connect and download transactions from Wells Fargo? First time seeing this error on Windows and I usually have no issue connecting.

Hello @reigninslayer,

I am sorry to hear about this issue with the CC-501 error message. Thank you for contacting the Quicken Community for discussion of this problem.

When did you notice this issue first? If it has emerged within the last day, it may resolve itself within 24 hours or so. If this is not the case, check back in with us and keep us updated, if you can.

Additionally, do you notice any other error messages in conjunction with the one mentioned in the title of the thread, such as ccscrape.170?

I look forward to your response, and hope to continue working with you on this issue.

Thanks,

Quicken Jared

rlof2453

I am having the same issue. It started February 23. Nothing that has been suggested helps. I know for sure that my login credentials to Wells Fargo are good. Is this not a systemic problem that Quicken is having? None of my other online accounts are having any issues updating in Quicken. I will be cancelling my subscription if this is not corrected soon.

Quicken Anja

Hello @reigninslayer & @rlof2453,

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

This is a known issue that has been escalated internally and is being worked on, though we do not have an ETA at this time. While the investigation remains ongoing, please refer to this Community Alert for any and all available information and updates.

We apologize for any inconvenience in the meantime! Thank you.