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

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
Anonymous
Not applicable

Export to File in Group stopped working (strange error)

Hello,

 

Project description:

We use app owns data model with PBI Embedded.

Recently Export to File in Group stopped working.

We receive the following error:

"status""Failed",
    "error": {
        "code""RefreshUserMetadataAPIError",
        "message""RootActivityId(-): Screenshot Service Client received a user error exception. Response had <ErrorCode=RefreshUserMetadataAPIError> and <StatusCode=400>",
        "details": []
    }
 
This is pretty urgent, so we would appreciate a prompt response.
Thank you!
7 REPLIES 7
Juniorflip
Frequent Visitor

How were you able to generate that error in C#?  All I can get out of the body is these.

public string Id { get; set; }
[JsonProperty(PropertyName = "createdDateTime")]
public DateTime? CreatedDateTime { get; set; }
[JsonProperty(PropertyName = "lastActionDateTime")]
public DateTime? LastActionDateTime { get; set; }
[JsonProperty(PropertyName = "reportId")]
public Guid? ReportId { get; set; }
[JsonProperty(PropertyName = "reportName")]
public string ReportName { get; set; }
[JsonProperty(PropertyName = "status")]
public ExportState? Status { get; set; }
[JsonProperty(PropertyName = "percentComplete")]
public int? PercentComplete { get; set; }
[JsonProperty(PropertyName = "resourceLocation")]
public string ResourceLocation { get; set; }
[JsonProperty(PropertyName = "ResourceFileExtension")]
public string ResourceFileExtension { get; set; }
[JsonProperty(PropertyName = "expirationTime")]
public DateTime? ExpirationTime { get; set; }

jwademcg
Advocate I
Advocate I

Receiving same error, urgent for us as well.

 

Going to open ticket.

Anonymous
Not applicable

@jwademcg Did you solve the problem or do you have any information from the support team?

@Anonymous for the one in February, it was confirmed as a bug that they fixed overnight.  But I did receive it again on one report for the first time again yesterday as well, but have had several sucessfull exports since then so hopefully it was just transient.  Have you been getting the error recently as well?

Anonymous
Not applicable

@jwademcg Yes, I was having the very same issue for most of the day today. Then it changed to this:

Screenshot Service Client received an exception. Response had <ErrorCode=ScreenshotEngineRequestTimeout> and <StatusCode=408


But it started to work an hour ago or so...

I'm still getting these once every 1-2 days, and it doesn't appear to be tied to capacity size.  So not sure what to do other than issue a ticket.  @Anonymous are you still getting these?

Anonymous
Not applicable

Hey.
I am also getting this error when i try to export  file to PDF, via a Power Automate job.

 

Error code:

 

Screenshot Service Client received an exception. Response had <ErrorCode=ScreenshotEngineRequestTimeout> and <StatusCode=408>.


Edit: 
Might be connected to this issue:
Reports on Premium Workspace Load Forever - Microsoft Power BI Community

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.