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

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

invalid query locator

Power BI Report is refreshed in PBI services and the following error constantly occurs:

 

DataSource.Error: <pii>invalid query locator</pii>. <pii>{[...]}</pii>. ;invalid query locator. The exception was raised by the IDbCommand interface. Table:

 

I have downloaded the report, then refreshed the preview and republished it to PBI Services, hoever this error keeps coming back.

The report refreshes on the desktop version with no problem

Status: Investigating

Hi @Anonymous ,

 

May I know what are your data sources In your report? Did you make any operations like Merge for different data sources? If you open Power Query(Transform data) and check the steps in the downloaded pbix file, will you see any warning or error?

 

Best Regards,

Community Support Team _ Caiyun

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

Hi @Anonymous ,

 

May I know what are your data sources In your report? Did you make any operations like Merge for different data sources? If you open Power Query(Transform data) and check the steps in the downloaded pbix file, will you see any warning or error?

 

Best Regards,

Community Support Team _ Caiyun

Paul_Ben
Frequent Visitor

Hi @Anonymous , while not a solution to the underlying problem I think, it may get the published report to refresh.

 

In my instance I was pulling more than 10 tables from Salesforce which tends to be the usual error "invalid query locator". I then merge these into an intermediary table before then joining with other data I have from other systems like CRM Dynamics. All my reporting works of the one final combined table only.

 

For some reason, if I have the intermediary tables ticked "Enable Load" when you Transform data, the published report will fail with the error "invalid query locator" but if I un-tick Enable Load on the intermediary tables it will refresh fine when published.