Error when loading data -Internal error: Reference to undeclared entity 'nbsp'. Line 29, position 33

[dcresp]

When trying to aceess XML data from Australian Burea of Statistics (ABS) through the http://stat.data.abs.gov.au/ service using the SDMX (XML) download service, I reguarly run into issues with the following error - 

Processing error:

Xml processing failed. Either the input is invalid or it isn't supported. (Internal error: Reference to undeclared entity 'nbsp'. Line 29, position 3

This is an intermittent error and occurs in different locations associated with downloadin the data. It reguarly pops up when using the service and setting automatic refresh. However, some refreshes work and others fail. The following is an example of refresh errors. There have been no changes to the file during this period.

Refresh history

ScheduledOneDrive

Details Type Start End Status Failure message

Show	On demand	2/12/2017, 5:15:19 PM	2/12/2017, 5:15:25 PM	Failed	There was an error when processing the data in the dataset.
	Scheduled	2/12/2017, 9:07:10 AM	2/12/2017, 9:11:19 AM	Completed
	Scheduled	2/12/2017, 8:37:15 AM	2/12/2017, 8:41:26 AM	Completed
Show	On demand	2/11/2017, 5:59:31 PM	2/11/2017, 5:59:40 PM	Failed	There was an error when processing the data in the dataset.
Show	On demand	2/11/2017, 5:59:19 PM	2/11/2017, 5:59:28 PM	Failed	There was an error when processing the data in the dataset.
Show	On demand	2/11/2017, 5:59:09 PM	2/11/2017, 5:59:11 PM	Failed	There was an error when processing the data in the dataset.
Show	Scheduled	2/11/2017, 12:07:59 AM	2/11/2017, 12:09:13 AM	Failed	There was an error when processing the data in the dataset.

This particular file can also refresh fine using PBI Desktop. 

The same error has also been occuring on a PBI Desktop file intermittently when looking at the Query Editor refresh but when you go out of Query Editor and refresh it works file.

As the XML data is all web based I am not needed to refresh through a Gateway and I am able to use Conect Directly. 

I have contacted the ABS and they have reviewed their XML data and it does not have any mention of nbsp in the XML and does not have any errors in. The fact that this error is intermittent and that PBI Desktop can refresh the data makes me think that the issue is somthing to do with PBI rather than the XML data. 

All the errors that I am getting for this problem come up with the same message about nbsp'. Line 29, position 3.

Can somone please look into this issue.

Thank you for your assistance.

I am happy an example PBI file that will demonstrate the issue if you can let me know where to send this to. 

[v-haibl-msft]

@dcresp

I’ve got response from the product team.

To the best of our ability to tell, this is a server-side problem. The server must intermittently be returning XML data which contains the entity &nbsp. This entity is valid in HTML but not in XML. (You can see that this is an invalid entity from inside the Power BI Desktop editor by evaluating the expression Xml.Document("<a>hello&nbsp;</a>") -- you will get the same error as is reported here.)

One additional possibility to check with the site owner is whether it's possible to get an HTML response instead of an XML response from these particular endpoints. It may be that the site is returning some kind of error as HTML.

Best Regards,

Herbert

[kalessine]

Hi!

I just thought i would add my 2c, the ABS SDMX data service returns a HTML error page if the service is queried more than twice every 1-2 seconds from the same IP Address..

Hope this Help...

   James Gardner

[dcresp]

@kalessine Thanks for the feedback. I wonder if this could be part of the issue with the error that I am getting. I am not generally doing multiple queries but the queries that I am doing are getting quite large amounts of data and I wonder if this is trigering the error message.

Thanks for your feedback.

Regards

David

[dcresp]

@kalessine Hi James, thank you very much for the sugestion. It looks like this is the source of the problem. The ABS have made recent changes to their systems and it now seems to be working better. Greatly apreciate the sugestion.

David

[v-haibl-msft]

@dcresp

Does this issue persist after the changes made by ABS?

Best Regards,

Herbert

[dcresp]

@v-haibl-msft HI Herbert, it does seem a lot better but as the followign shows it is still getting some errors.

Details Type Start End Status Failure message

Show	Scheduled	‎5‎/‎03‎/‎2017‎ ‎9‎:‎00‎:‎02‎ ‎PM	‎5‎/‎03‎/‎2017‎ ‎9‎:‎00‎:‎16‎ ‎PM	Completed
Show	Scheduled	‎4‎/‎03‎/‎2017‎ ‎9‎:‎00‎:‎04‎ ‎PM	‎4‎/‎03‎/‎2017‎ ‎9‎:‎03‎:‎24‎ ‎PM	Completed
Show	Scheduled	‎3‎/‎03‎/‎2017‎ ‎9‎:‎00‎:‎04‎ ‎PM	‎3‎/‎03‎/‎2017‎ ‎9‎:‎00‎:‎33‎ ‎PM	Completed
Show	Scheduled	‎2‎/‎03‎/‎2017‎ ‎9‎:‎00‎:‎05‎ ‎PM	‎2‎/‎03‎/‎2017‎ ‎9‎:‎00‎:‎53‎ ‎PM	Completed
Show	Scheduled	‎1‎/‎03‎/‎2017‎ ‎9‎:‎01‎:‎03‎ ‎PM	‎1‎/‎03‎/‎2017‎ ‎9‎:‎03‎:‎24‎ ‎PM	Failed	There was an error when processing the data in the dataset.
Show	Scheduled	‎28‎/‎02‎/‎2017‎ ‎9‎:‎00‎:‎05‎ ‎PM	‎28‎/‎02‎/‎2017‎ ‎9‎:‎01‎:‎20‎ ‎PM	Completed
Show	Scheduled	‎27‎/‎02‎/‎2017‎ ‎9‎:‎00‎:‎04‎ ‎PM	‎27‎/‎02‎/‎2017‎ ‎9‎:‎02‎:‎15‎ ‎PM	Completed

[v-haibl-msft]

@dcresp

That's good news... I didn’t receive any more response from the product team except the last reply from me. Do you have any other concern about the response from the product team? I can help to forward it to the team.

Best Regards,

Herbert

[v-haibl-msft]

@dcresp

Please let me know if you still have concern about it if you see this message.

Best Regards,

Herbert

[v-haibl-msft]

@dcresp

Please let us know if you have any update about it.

Best Regards,

Herbert