Error connecting to BoA Credit Card

I'm trying to connect to to my BoA Credit Card from Quicken for Mac (6.5.1). This used to work fine, but now I'm receiving an error: AGGREGATOR_IN_ERROR CP_SERVER_ERROR: internal.api

Any help would be appreciated. Thanks. Here's the full error message:

errors count: 1

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
error #1
level: 4 (Debug = 0, Critical = 6)

description:
Server side error.

suggestion:
Try again later.

system description:
institution login: can't setup (server error)
institution login Sync Id: (null)
BID: 26757
FI name: Bank of America - Quicken

response:
{
"code" : 200,
"resource" : {
"status" : "ACCEPTED_POLLING_REQUIRED",
"pollingReference" : "\/institution-logins\/307982190881469188\/poll",
"id" : "307982190881469188",
"clientId" : "FBCC3040-84B4-47B9-88BD-128F31356F52"
}
}

poll response:
{
"status" : "AGGREGATOR_IN_ERROR",
"aggregators" : [
{
"channel" : "FDS_DEFAULT",
"cpAggStatusCode" : "internal.api",
"aggStatus" : "CP_SERVER_ERROR",
"isProcessing" : false,
"cpAggStatusDetail" : "Customer migration to FDP COMPLETED"
}
],
"mode" : "DISCOVER_AND_ADD_ACCOUNTS",
"institutionLoginId" : "307982190881469188",
"isProcessing" : false
}

Answers

  • Quicken Jared
    Quicken Jared Moderator mod
    robare1 said:
    I'm trying to connect to to my BoA Credit Card from Quicken for Mac (6.5.1). This used to work fine, but now I'm receiving an error: AGGREGATOR_IN_ERROR CP_SERVER_ERROR: internal.api

    Any help would be appreciated. Thanks. Here's the full error message:

    errors count: 1

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    error #1
    level: 4 (Debug = 0, Critical = 6)

    description:
    Server side error.

    suggestion:
    Try again later.

    system description:
    institution login: can't setup (server error)
    institution login Sync Id: (null)
    BID: 26757
    FI name: Bank of America - Quicken

    response:
    {
    "code" : 200,
    "resource" : {
    "status" : "ACCEPTED_POLLING_REQUIRED",
    "pollingReference" : "\/institution-logins\/307982190881469188\/poll",
    "id" : "307982190881469188",
    "clientId" : "FBCC3040-84B4-47B9-88BD-128F31356F52"
    }
    }

    poll response:
    {
    "status" : "AGGREGATOR_IN_ERROR",
    "aggregators" : [
    {
    "channel" : "FDS_DEFAULT",
    "cpAggStatusCode" : "internal.api",
    "aggStatus" : "CP_SERVER_ERROR",
    "isProcessing" : false,
    "cpAggStatusDetail" : "Customer migration to FDP COMPLETED"
    }
    ],
    "mode" : "DISCOVER_AND_ADD_ACCOUNTS",
    "institutionLoginId" : "307982190881469188",
    "isProcessing" : false
    }
    Hello @robare1,

    I am sorry to hear that you are experiencing this server error. Thank you so much for taking the time to seek further discussion and support here on the Quicken Community. 

    First, save a backup by going to File > Save a Backup in the upper menu at the top of the screen while Quicken is open. Next, go to Quicken > Sign Out in the same menu. When prompted, sign back in with your QuickenID and Quicken.com password. Now, try linking your account by selecting it from the Account List in the left-hand panel, and then go to Accounts > Settings > Downloads in the upper menu and select Connect Account

    I hope to hear back from you with any updates you may be able to provide, should you have a chance to drop by and follow up with us.

    Thank you,

    Quicken Jared 
  • Vita
    Vita Member
    edited February 1
    I am having an identical problem with my Chase downloads. I tried what you suggested and got the same result. I have just renewed my subscription and I am beyond annoyed with this. A quick search on this site and Google shows this problem is RAMPANT. What exactly is QUICKEN doing to address this? [Removed-Disruptive]
  • jacobs
    jacobs SuperUser, Mac Beta Beta
    @Vita  Instead of venting to the user community, have you tried contacting Quicken Support
    Quicken Mac Subscription • Quicken user since 1993
  • robare1
    robare1 Member
    Thanks for the response Jared. We tried that and are still seeing the same exact issue. I can open a support case, but I was wondering if you had any other suggestions on how to resolve this issue. This was working just fine until the last update.
This discussion has been closed.