Forum Discussion

ianbarker's avatar
ianbarker
Helper III
10 years ago

PowerBI refresh fail - Expression Error.

Has anyone seen this issue when refreshing dataset in app.powerbi.com? Seems to work ok in Desktop.   This is based on a Desktop file I have uploaded which is looking at data from Dynamics CRM.  ...
Need Help
mdawesdigitalk's avatar
mdawesdigitalk
Frequent Visitor
10 years ago

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.....

 

  • dstramilov's avatar
    dstramilov
    Helper II
    10 years ago

    Same for me(((

     

    Processing error:XML parsing failed at line 97, column 32: Semicolon expected. .
    Cluster URI:WABI-WEST-US-redirect.analysis.windows.net
    Activity ID:700326bc-35e1-4323-b411-1a6f526faa12
    Request ID:ce4a9089-64db-4305-b3c5-ff8e6d6e32ff
    Time:2016-07-01 00:30:03Z
    • Mattnade's avatar
      Mattnade
      New Member
      10 years ago

      I think the same is happening to me - 

       

      Processing errorXML parsing failed at line 157, column 39: Illegal qualified name character.
      .
      Cluster URIWABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net
      Activity ID63e7096d-018a-ab56-44b5-f5c31d16c857
      Request IDf72a9ee2-9e08-2dc1-da2f-cde6d9c9a5c6
      Time2016-07-04 00:36:54Z

       

      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....

       

      • ianbarker's avatar
        ianbarker
        Helper III
        10 years ago

        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.