AGGREGATOR_IN_ERROR (CP_SCRIPT_ERROR:ccscrape.101) from New Cumberland FCU

deanpjjme

I am getting AGGREGATOR_IN_ERROR (CP_SCRIPT_ERROR:ccscrape.101) when I try to download from New Cumberland FCU using Quicken connect.  They just changed their web site. Their tech person says it is something with quicken.  Any suggestions?

jacobs

Well, if they just changed their website, unless they properly gave advance notice to Quicken (actually to Intuit, which handles the connectivity), then their website change likely broke the way Quicken navigates the site to handle logins and downloads. So yes, it is possible Quicken now has to make changes to catch up to what the credit union changed. (It's as if a store you visit did renovations and moved the entrance from the front of the building to the side; when you walk up to the front to enter and can't get in, it's technically your fault for trying to enter the wrong way, but only because you aren't aware they moved the entrance.) I love how banks revamp their websites and then immediately blame Quicken for connectivity problems!

What you need to do is contact Quicken Support, walk them through the fact that the credit union just changed their website, and let them verify the error with you. They'll need to escalate this to the team at Intuit that handles connectivity to financial institutions to get this fixed. It's possible they already know about it, but with more than 14,000 financial institutions and upwards of 100 such changes per week, it's possible they don't. With large financial institutions, these types of things typically get discovered quickly, and can be fixed within a day or two; with smaller financial institutions, it depends how soon the problem is flagged, and then how much work it takes to navigate the "new front door" to get logged in.

jacobs

Well, if they just changed their website, unless they properly gave advance notice to Quicken (actually to Intuit, which handles the connectivity), then their website change likely broke the way Quicken navigates the site to handle logins and downloads. So yes, it is possible Quicken now has to make changes to catch up to what the credit union changed. (It's as if a store you visit did renovations and moved the entrance from the front of the building to the side; when you walk up to the front to enter and can't get in, it's technically your fault for trying to enter the wrong way, but only because you aren't aware they moved the entrance.) I love how banks revamp their websites and then immediately blame Quicken for connectivity problems!

What you need to do is contact Quicken Support, walk them through the fact that the credit union just changed their website, and let them verify the error with you. They'll need to escalate this to the team at Intuit that handles connectivity to financial institutions to get this fixed. It's possible they already know about it, but with more than 14,000 financial institutions and upwards of 100 such changes per week, it's possible they don't. With large financial institutions, these types of things typically get discovered quickly, and can be fixed within a day or two; with smaller financial institutions, it depends how soon the problem is flagged, and then how much work it takes to navigate the "new front door" to get logged in.