I have several financial institutions, some with multiple accounts (checking, savings, CD;s, etc.) . Many institutions use Direct connect while a few others use Express Web connect (EWC).
EVERY institution using EWC is failing. EVERY institution using Direct Connect downloads and updates successfully.
With help from Quicken we have determined my data files are not damaged or corrupt and have ruled out all other client side possibilities. Quicken now points to my financial institutions to resolve the problem and it is up to me to work with my institutions to resolve it. Quicken will not assist according to the techs I have dealt with.
I have reached out to my primary credit union who uses EWC. They report they have other customers complaining of the same issue and have diagnosed their end and have escalated the matter to Quicken several times. They are certain the failure point is at Quicken. Following is the last response I received from my CU:
"I apologize that you are having to manually enter in the transactions. I know that quicken is saying that it is on our side, but we have looked into this issue multiple times and the error message that is being received, we researched it and it is an error on their end. We have contacted them multiple times about this issue and looking to get it resolved. We have been told that they are looking in to it."
My question and point is, WHY IS QUICKEN NOT RESOLVING THIS ISSUE? The error codes you provide indicate it is a server side error! You even "apologize" saying it is not my fault this is failing.
I had this problem in Quicken 2015 beginning the fall of 2016 and spent countless hours attempting to resolve it. I finally upgraded to Q 2017 hoping it would not have the problem but it does!
Help us Quicken, we need your help NOW. If not I will move on after successfully using your products for 25 years.
So, in that case, the bank/etc would of course claim that 'everything's fine on their side' when in reality it's their failure to provide timely notice that's the real problem ... and you just need to wait it out until THAT fix bubbles up to the top ... after those banks/etc that DID provide timely notice.
In case of CC-501, 502, 506 errors deactivate all accounts with this bank using the same bank logon ID, including any old, long closed, hidden and forgotten accounts that might still be activated. If you miss one, the Quicken server involved in handling Express Web Connect - connected accounts will not start with a clean slate and you will continue to have this problem.
To deactivate an Account
Go to Tools > Account List.
Click Edit for account you need to change.
If account has been activated for Online Bill Payment, deactivate this service first.
Click Deactivate button in Online Setup box.
Repeat for any other accounts that need to be deactivated.
Restart Quicken to make sure that the changes are fully applied.
To (re-)activate accounts for downloading
Create a backup of
your Quicken data file. This is a restore point, should something go horribly
wrong during the next steps.
Go to Tools / Add Account to reactivate the accounts. As you go thru the setup process, Quicken will identify all accounts it can download.
Select an account type, e.g. Checking
Enter the name of your bank and click Next. Some banks have multiple choices, Consumer vs. Business accounts, Express Web Connect vs. Direct Connect. Be sure to pick the correct one.
Enter your credentials, select Save this password (if using password vault) and click Connect.
You should now see a list of one or more accounts found at your bank that you can activate. If you are activating an existing account, make sure the dropdown button for that account says LINK. If it says ADD, change it to LINK and select the correct Quicken account. If it already says LINK, click the button and select the correct existing account register. If you do not do this, then the account will be added as a new account instead of being linked to the existing account register.
Repeat this step for
each account listed.
Change ADD to IGNORE for any account on the list that you do not want to activate at this time.
Click Next to continue.
It brought back the accounts but says they are unknown types. The error says Quicken did not get enough information to add the account then suggests trying it again in a few days. I'm running out of more days.
The types of errors you are reporting are inherent to the EWC method. They also typically create exception reports that Quicken's service providers will use to fix the issue when they get around to it. If the steps in the link do not resolve the issue, you will just have to wait or contact support. Support should be taking you to a higher level because EWC is a Quicken problem, not an FI problem. FI's that offer Web Connect QFX downloads are usually the more reliable EWC FI's because they are not scraped.
If you haven't, you could contact each of the FI's involved, ask for their IT support customer service, and ask if they have a Direct Connect service available. If they do and if they turn it on for you, you should be able to One Step for those FIs.
Does the fact I do not seem to have the file have an impact on the EWC functionality??
This has been in place for a long time but I wonder if it is getting in the way of Q getting to my account info. None of the other EW connected accounts have this however they continue to fail with the same cc-501 error.
Target is another account that I continue to get the cc-501 error and it does NOT have 2 step authentication. Kohls is another.
Now, I wonder why Q does not have that in their knowledge base for techs to go to early in the troubleshooting. They spent close to 8 hours total in chat and phone support sessions going through everything else except clearing out the accounts.
If you have connections at Q, please ask them to get that out to people. It makes sense to clear it out but who knew those keystrokes to accomplish it.
If this holds, I'll give you another star on Tuesday markus1957. Thank you!!
"Quicken needs a new kitchen, bathrooms, central air and upgraded boiler – in other words a complete gutjob. Putting new vinyl siding might make it look nice if H.I.G. is looking for a quick sale, but the issues will shine through when you do an inspection. For at least the past 5–6 years Quicken has been piecemealed together, and this is what led them to where they are now."
If they want to survive and thrive, they better get on top of the problems and support issues.
Usually CC 503 also that your password doesn't meet the requirements posted on your financial institutions website. A good example of this is a requirement that the password contain between 8-12 characters, but you enter 13 characters. Your bank's website has the ability to simply stop "reading" the characters at 12 (ignoring the 13th) but Quicken must hard-stop at that 12th character. We've noticed that your password format contains 13 characters. Therefore, we would like to recommend you to try changing your password to something shorter like a maximum of 8-10 characters perhaps then try reconnecting your accounts once again in Quicken.
They did not recall that the last software update, which I received in the last 10 days, would have addressed this problem. But I have been able to successfully reconnect all but 2 credit card accounts since applying the update. When I try to connect the credit cards, it attempts to rejigger (undo) all the working accounts. They fortunately were able to see it happen real time today.
I'm happy Quicken is now seeing the problem and interested in getting to root cause.
Until the next time, "Bye...!"
I've sent dozens of logs and screenshots of our work sessions and of my own tests. The engineers have ruled out corruption of the client data file and maintain it is a server issue. They make tweaks on the server based on the log results. After making adjustments I can connect for a couple of days then it stops working.
The individuals I am working with are experienced, top notch and dedicated to getting to root cause and a fix but it is taking considerable time on their part and mine.
Today I noticed this in the connlog: *** AddAccount failed due to missing Account Type *** As I examine the account use and types all are identified correctly in both the client UI and via the qdfview they provided me.
So the problem is real and it is not going away. It is like the whack-a-mole game. It keeps popping up. Others are seeing it with other EWC FI's. If we ever get to root cause I'll post the results.
This conversation is no longer open for comments or replies.
This conversation is no longer open for comments or replies.
- 7850 Conversations
- 4646 Followers