We couldn't import data from MailChimp There was an error when processing the data in the dataset. Please try again later or contact support. If you contact support, please provide these details. Data source errorWeb.Contents failed to get contents from 'https://us2.api.mailchimp.com/3.0/reports/375380f257/unsubscribed/?count=100&offset=0' (500): Internal Server Error. The exception was raised by the IDataReader interface. Activity ID3dd14f2a-5497-41a8-90ff-da941e858ff8 Correlation IDd3b93657-8677-a701-1076-b880be71532a Request ID33efca1b-6560-381c-477f-2d58c4ad8231 Status code400 TimeSat Jan 21 2017 18:51:53 GMT-0800 (PST) Version13.0.1700.1015 Cluster URIhttps://wabi-west-us-redirect.analysis.windows.net
16 Comments
- v-haibl-msft
Microsoft Employee
Are you trying to get data from Mailchimp content pack in Power BI Service? I just tried to do it and I can get the dashboard successfully with no error message. I just input my mailchimp credential with no other action.
Best Regards,
Herbert
- Vicky_Song
Impactful Individual
Status changed:NewtoNeeds Info - markjmtNew Member
That's just what I did. Several times and got the same result. Could it be the size of the mailchimp database? We have over 3,000 campaigns and near 40,000 in the list.
- jmaurer17Frequent VisitorI am also having an issue importing data from MailChimp:Data source errorWeb.Contents failed to get contents from 'https://us1.api.mailchimp.com/3.0/reports/37eb248967/click-details/?count=100&offset=0' (503): Service Unavailable. The exception was raised by the IDataReader interface.Cluster URIWABI-US-EAST2-redirect.analysis.windows.netActivity ID35209b9a-7127-d0d1-4262-9a5dfe693e52Request ID4eabc9fe-08c5-7136-d68c-8ec9a1886fe2Time2017-01-24 16:07:17Z
- v-haibl-msft
Microsoft Employee
Hi All,
An existing issue has already been reported internally to PBI Team: CRI 30266991
I’ll post here once there is an update about it.
Best Regards,
Herbert
- Vicky_Song
Impactful Individual
Status changed:Needs InfotoAccepted - v-haibl-msft
Microsoft Employee
The team have looked into some traces provided by some other users who have the same problem. They suggest you to contact [email protected] for help, you need to work with Mailchimp support to understand why Mailchimp is returning a 500/503 for this customers data
Best Regards,
Herbert
- jmaurer17Frequent Visitor
v-haibl-msft,
MailChimp insists that the issue is on the Power BI end. As you can see below, I am now getting an API response of 200 (Ok). Below are the details:
Activity ID7a5bf74d-52b0-4197-a048-be1189fb4f9c
Request IDf6ccc7f6-4387-7d3a-ed52-ca26b3ab208c
Correlation ID72c9aa92-c35b-63e0-7832-1f433cef37cf
Status code200
TimeFri Feb 03 2017 10:52:03 GMT-0500 (Eastern Standard Time)
Version13.0.1700.1121
Cluster URIhttps://wabi-us-east2-redirect.analysis.windows.netOddly, I can successfull call the API in the desktop. Am I the only one having issues with the MailChimp content pack? Am I calling too many records... I'm not seeing a 403 Exceed Error?
- frankedNew Memberv-haibl-msft any update on this seeing that someone posted that Mailchimp battered it back to you?
- markjmtNew Member
MailChimp came back and said it appeared to be a problem on their end:
Laura (MailChimp)
Feb 10, 1:17 PM ESTHi Mark,
Thanks for following up with this. This time I was able to get some information from the API , and it looks like the issue is actually something on our end. To be totally transparent, I am not sure exactly where the issue lies, but it appears to be related to unsubscribers of a particular campaign. I went ahead and passed these details to our developers so they can do some investigating. While I'm not able to provide a timeframe for the fix, you're welcome to check in any time with ticket ID 1668389 about our progress.
Again, thank you so much for your patience while we work on this.
Thank You,
LauraNow, when I log into Powerbi.com, I get this:
https://portal.office.com/BoxError.aspx?aspxerrorpath=/default.aspx
Server Error in '/' Application.
Runtime Error
Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.