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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Unusual error messages from XMLA refresh commands

We have XMLA refresh commands that refresh certain tables within a larger model. The commands are executed from an Analysis Services task in SSIS. Today we are getting strange error messages logged in SSIS from these commands. The refreshes actually appear to have succeeded, but we still get the error messages. It's almost like the response from the Power BI Service is invalid somehow. Here are a few examples:

 

"Cannot access closed stream"

 

"'Element' is an invalid XmlNodeType.  Line 1508, position 28."

 

"The trace events reader has failed to stop successfully."

 

"Stream does not support reading."

 

"The 'G' start tag on line 108 position 346 does not match the end tag of 'I'. Line 108, position 2100."

 

Any ideas on what these could mean? Thanks.

 

 

Status: Investigating

Hi @nicg 

 

May I know whether you have checked the refresh history of this dataset in Power BI service? Is there any refresh errors there? Have you ever checked in your report whether your data has been latest?

 

Best Regards,

Community Support Team _ Caiyun

Comments
v-cazheng-msft
Community Support
Status changed to: Investigating

Hi @nicg 

 

May I know whether you have checked the refresh history of this dataset in Power BI service? Is there any refresh errors there? Have you ever checked in your report whether your data has been latest?

 

Best Regards,

Community Support Team _ Caiyun

nicg
Advocate II

Yes, the data does actually refresh. The refresh history shows completion (no errors). So it seems like the refresh is successful, but something is wrong with the response from the PBI Service to SSIS.

 

Everything is working normally again today. Not sure what changed.