Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Multiple Double Records Notification

Hello,

 

Since a few weeks, we occasionally recieve this message if we try to refresh the datafile connected to our dashboards:

''The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.

Please try again later or contact support. If you contact support, please provide these details.''

with the details from below: 

 

Cluster URI : WABI-WEST-EUROPE-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 364a04c6-ed32-4e1b-8971-5b2bb20cfbc0
Request -ID: cc948b83-7132-416b-a0e3-0f97e03e5d68
Time: 2021-02-23 13:27:04Z

 

We figured out that this problem is caused by a double record in our database. At first we always recieved an email saying that we have a double record (or more) but for some reason we dont get that notification anymore...

 

Is this permanently or is this a change in settings?

I hope this can get fixed, because of the size of our dataset, we dont always see those double records.

 

Kind Regards,

Jennifer

Status: New
Comments
v-chuncz-msft
Community Support

@DMSJennifer 

 

You may try the latest version and remove duplicates in power query.

DMSJennifer
Helper I

@v-chuncz-msft 

We have the latest version but the issue here is not that we want to remove the duplicates, but we just want to get an email notifying us that we have a duplicate.

 

Before we always recieved an email containing this message:

'An error occured while processing the data in the dataset.'

As well as the Table and Column names where the error was located.

 

Now we get this email:

'The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.'

This time without the Table and Column names where the error is.

If we look into our dataset, we can find the problem, but that takes a lot of time.

 

Can we get the notification email with the specifics of the error back? The way PowerBI notifies us now is very inconvenient for us.