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

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
Anonymous
Not applicable

DBCC Error in Dataset refresh

Hi,

 

I'm getting the following errors when refreshing a Dataset.

Database consistency checks (DBCC) failed while checking the segment statistics. Database consistency checks (DBCC) failed while checking the data segments. Database consistency checks (DBCC) failed while checking the 'PaintCostAmount (226)' column. Database consistency checks (DBCC) failed while checking the 'VehicleSales Vehicles (31)' table. Database consistency checks (DBCC) failed while checking the '85ebc017-b957-45f2-9425-ba405c904d27' database. An error occurred while attempting to save the dataset (reference ID '85ebc017-b957-45f2-9425-ba405c904d27').

 

I've run DBCC CHECKDB without errros.

The report runs correctly in Desktop.

November 2020 version of the Gateway (didn't fix it)

Same on both powerBI.com and also dedicated capacity.

 

Report runs fine against another DB with identical schemas.

 

Any ideas, or where to look next?

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Micorsoft have confirmed this as a bug. Incremental refresh fails but full refresh works. There is a problem with too many NULL values in the reported column.

They said it will be corrected in a newer version.

Hope this helps others.

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

Just an FYI for this issue.

 

The table in question has incremental refresh set to keep 37 months, update 37 months if updateddatetime field changes.

If I turn off incremental refresh for this table, the report updates without issue.

I had a feeling it was due to implementing incremental refresh.

 

Still njo fix, but I see December's version of the gateway is out, so might try that.

Anonymous
Not applicable

Micorsoft have confirmed this as a bug. Incremental refresh fails but full refresh works. There is a problem with too many NULL values in the reported column.

They said it will be corrected in a newer version.

Hope this helps others.

Anonymous
Not applicable

Hello, I don't have a solution yet but I did just encounter this issue last evening suddenly.  I published successfully then made one more change and subsequently received internal server errors.  I will submit ticket and share any results here.

Anonymous
Not applicable

Hi, I'm still looking for a solutions for this issue. Can you shed any light on your findings yet?

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

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

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors