Same error with us as follows;
An error occurred while processing the data in the dataset.
XML parsing failed at line 83, column 40: Semicolon expected.
Cluster URI: WABI-NORTH-EUROPE-redirect.analysis.windows.net
Time: 2016-07-01 10:05:32Z
This is a dataset that has been refreshing 2 or 3 times a day for 6 months without fail, until yesterday.
If I take the original desktop file and refresh I get no errors. Reupload that refreshed file onto Service via OneDrive and the data refreshes, but the dataset will not refresh within Service.
Any pointers appreciated, but suspect it is a Microsoft introduced bug somewhere.....
Same for me(((
|Processing error:||XML parsing failed at line 97, column 32: Semicolon expected. .|
I think the same is happening to me -
Anyone know if this is one and the same issue that is causing the "Users may experience processing errors when refreshing datasets in the Power BI service. We are working to resolve this issue as quickly as possible." status message we're being shown... or if I should be hunting for an issue with my dataset specifically?
Refreshes fine in Desktop, so I'm a little lost....
In my case, as per my edit, it was (or so I thought) related to the fact that I had multiple queries pointing to the same table in my data source. Combining those queries into a single query resolved my issue.
I was having a think about it and also wonder if the issue could be related to a naming convention with the queries.
In my case, originally, the multiple queries that pointed to the same table were all named very similarly. i.e. they all started with the word "Optionset". I wonder if anyone else here, even if you are not pointing more than 1 query to the same table, is naming more than a single query with a matching word?
Just a thought.
From the error message, we can see that the issue is caused by dataset data. Please check if there is any changes in Dynamic CRM Online. Also you can create a new dataset to get data from Dynamic CRM Online in Power BI Desktop to see if the same dataset can be processed.
I can assure you that there had been no changes to the dataset data.
The CRM Online instance I was pointing to at the time was a staging database, so there had not even been any transactions posted in it.
All I can tell you is that one day the dataset refreshed and the next it didn't and was giving the errors previously mentioned.
I have resolved my issue now, via the workaround in my earlier post. However, this is obviously causing issues for a number of other people.
Its working normally for me again. I didn't do anything actually, and my dataset has some queries depending on the same table.
I believe they already found a solution.
Yesterday the refresh started to work for us again. However, this morning, we received the same error so I am not sure that this issue has been resolved. Has there been any other possible solutions to resolving this issue?