cc-501 error -- I called Quicken support and ...

I had been getting a cc-501 error trying to download my Citibank accounts for the past week.

Finally, I called Quicken support.
They said that they have made some changes in August to their servers and it impacted many bank downloads.
I don't know why August changes didn't cause a problem for me until October. Maybe they have been trying to fix the August errors and have now created more problems.

At any rate, they asked for my Connlog and OFX log files and will pass that to their tech team.
They said it would take a week to expect results.

Here is another annoyance:
I went to their support page and followed the path that said they would call me about my problem within 20 minutes.

Instead of calling, they sent me an email with an incident number and asked me to call them. They did not even include their phone number in the email. I had to go back to the web site to get the phone number.


Here is an update.
The Quicken Web Connect to Citibank is working today.
Q support said it would take 7 - 10 days to resolve the issue.
They actually fixed it over night. One day. Bad feedback from them. But, excellent service.
Was this answer helpful? Yes No
1 additional answer

No answers have been posted

More Actions

People come to Quicken Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:

  1. Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
  2. Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
  3. Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
  4. Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
  5. Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.

Select a file to attach:

Do you still have a question?

Ask your question to the community. Most questions get a response in about a day.

Post your question to the community
or contact us