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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
cte_crest
Helper I
Helper I

Internal server error while publishing pbix file.

Hi folks,

 

I created a custom connector and implemented an incremental refresh in that. I defined the RangeStart and RangeEnd parameters and did the required settings. When I try to publish it, I receive an internal server 500 error. I traced the error using fiddler and got this:

{"error":{"code":"ModelOperatorOperationFailedException","pbi.error":{"code":"ModelOperatorOperationFailedException","parameters":{},"details":[]}}}

 

Could someone please help me resolve my issue? I am really stuck here and the error message here doesn't seem to help much.

5 REPLIES 5
Jayendran
Solution Sage
Solution Sage

Hi @cte_crest ,

 

Today I also got this error and I resolved it by removing the workspace from the capacity.

 

It seems my workspace is tied up with A1 capacity which was some reason stopped due to that i got this error.

v-diye-msft
Community Support
Community Support

Hi @cte_crest 

 

Do you publish .pbix file to PBI Report Server or Power BI Service?

 

If it is the former, does your account have a Power BI Pro license?

 

If it is the latter, please log on Power Bi service, upload your pbix files via Get Data -> Files -> Local file to check whether they can be published successfully.

 

If still not help, you'd better create a support ticket in Power BI Support to get further assitant.

 

Community Support Team _ Dina Ye
If this post helps, then please consider Accept it as the solution to help the other members find it more
quickly.

It's the latter one, i.e., Power BI service.

 

But, I am using an incremental refresh, and I think it would not be useful if I upload the pbix file manually. I tried with other types of pbix file, they are being published without any error. 

Hi @cte_crest 

 

To investigate further, please follow the steps below:

  1. Check the temp folder, C:\Users\User name\AppData\Local\Power BI, find the latest file after reproduce the issue and open it with notepad;
  2. Enable Tracing under Power BI Desktop File->Options and settings->Options->GLOBAL->Diagnostics, select Enable Tracing;
  3. Generate a Fiddler trace. (Fiddler Web Debugger Tool)

If available, upload them into OneDrive and post the shared link here. We will help to take a look.

In addition, try to take a reinstall or a repair of the Power BI desktop, see if this would make any difference.

 

 

Community Support Team _ Dina Ye
If this post helps, then please consider Accept it as the solution to help the other members find it more
quickly.

@v-diye-msft 

Thanks for the help.

I couldn't find Power BI at this location: C:\Users\User name\AppData\Local\Power BI.

 

However, I have followed the steps and have attached the fiddler trace here:

https://drive.google.com/file/d/1z_mBisOx8KfeSsFEl3mAxFt6DAIp3Wud/view?usp=sharing

 

Please have a look at it. Appreciate for the help!

Helpful resources

Announcements
Sept PBI Carousel

Power BI Monthly Update - September 2024

Check out the September 2024 Power BI update to learn about new features.

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

Sept NL Carousel

Fabric Community Update - September 2024

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