cancel
Showing results for 
Search instead for 
Did you mean: 

Refresh failure on Power BI Service for Jira Datasource

Issue: Refresh failure on Power BI Service for Jira connected datasets

Error:

Error 1: -

Something went wrong.There was an error when processing the data in the dataset.

Please try again later or contact support. If you contact support, please provide these details.

Data source error:"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Web.Contents failed to get contents from 'https://jirad.aaaa.com/rest/api/2/search

(400): "}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"Web"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"https://jiradc2.ext.net.nokia.com/rest/api/2/search"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.Url","detail":{"type":1,"value":"

Cluster URI: WABI-XXX-redirect.analysis.windows.net

Activity ID: bxyz-1234-1234-8f25-fxxx

Request ID: abcd84-3333-a11a-12123-yyyy

Time: 2020-09-04 07:10:16Z

Error 2: -

When we do not use a Gateway, we get error: -

Something went wrong.There was an error when processing the data in the dataset.

Please try again later or contact support. If you contact support, please provide these details.

Data source error: We found extra characters at the end of JSON input.. The exception was raised by the IDbCommand interface. Table: search.

Cluster URI: WABI-XXXX-redirect.analysis.windows.net

Activity ID: 5yyyy-92aa-4e82-af18-xxx

Request ID: czzzz-e4ww-3123-2123-axyz

Time: 2020-09-02 07:05:39Z

Cause:

  • Cause of Error 1 is mismatch in the authentication method used on Power BI Desktop and Service.
  • Cause of Error 2 is Gateway not being bound to dataset.
    • If the data source JIRA is sitting in an on prem environment, we need to bind the dataset to a Gateway for refreshes to work in Power BI Service.
    • Any endpoint which can be reachable over internet is a cloud source. Hence, Power BI Service might show no gateway required as it recognizes it as a cloud source but based on your data source (JIRA in this case) location and environment, you need to use Gateway.

Resolution: For this particular JIRA connection in this case, we made sure a Gateway is bound to the dataset. We used Basic Auth in PBI Desktop and Organizational privacy level. Same was updated on Power BI Service – Gateway settings.

Privacy Level in Power BI Desktop: -

File -> Options and Settings -> Options -> Privacy Level of Global Setting -> Combine data according to privacy of each data source -> File setting -> Combine data according to privacy of each data

s1.JPG

Data source Settings -> Edit Permissions -> Choose Basic Auth -> OK -> Privacy Level -> choose Organizational  s2.jpgBasic Auth used in Gateway settings: -

s3.jpg

Summary:

  • The error message and Request ID indicated issue with a Column 'Age' in table 'Jira Dump' cannot be found or may not be used in this expression:Exception Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server. Error returned: 'Column 'Age' in table 'Jira Dump' cannot be found or may not be used in this expression.
  • Too few arguments were passed to the ADDCOLUMNS function. The minimum argument count for the function is 3.
  • Checked and found no column or table specific error
  • Re-checked Privacy level on Desktop and Service and changed the Privacy for JIRA as organizational on the Desktop pbix and same on Service. Auth mode was selected as Basic.
  • We found that Gateway was using Windows Authentication, changed it to Basic for JIRA. Privacy Level as Basic for Jira. Other datasources as SharePoint were in correct mode so we didn’t make any changes to it.
  • Once done, all reports successfully refreshed. Verified with 4 reports and all of them refreshes successfully.
  • Additional reference on privacy levels can be found here: https://docs.microsoft.com/en-us/power-bi/admin/desktop-privacy-levels

Author: Srishti Sharma

Reviewer: Mounika Narayana Reddy