Forum Discussion

Franklin1's avatar
Franklin1
Advocate I
8 years ago

invalid query locator - salesforce

Hey all,

 

I have a report created on PBI Desktop with data from Salesforce.

The report was created and published to power bi service months ago.

Everything worked perfectly - the report is refreshed as scheduled.

Everything is in the cloud, hence I don't need no Gateway.

Suddenly, in the last few weeks the schedule refresh is not working and the error message I receive is "invalid query locator Table:XXX".

The name of the table (XXX) is not defined, and each time it is a different table.

 

I have read in salesforce documents a lot about the query locator.

What i don't understaand is how it happens all of a sudden, and what is the workaround i can do in Power BI to overcome this issue.

 

Please assist.

 

Thanks a lot!

Need Help

18 Replies

  • ivan_larson_cki's avatar
    ivan_larson_cki
    Helper III
    6 years ago

    I recently discovered a trick that fixed the issue for our worst-performing dataset.

     

    We had some queries that weren't being used for visualizations, but were only pulled to merge or append into other queries. In the Query Editor, I de-selected "Enable Load". As such, the data for these queries is still added where needed, but the queries don't need to be loaded themselves. A dataset that would never refresh has so far succeeded in about one third of its refreshes after this update.

  • v-yulgu-msft's avatar
    v-yulgu-msft
    Microsoft Employee
    8 years ago

    Hi Franklin1,

     

    Please check whether table name "XXX" is an existing name in source dataset. Or whether it has been changed.

     

    Regards,

    Yuliana Gu

    • Franklin1's avatar
      Franklin1
      Advocate I
      8 years ago

      Thanks Yuliana,

       

      It is an existing name.

      It is all worked well up until a few weeks ago.

       

      Any other idea?

       

      Thanks.

    • tmfitz's avatar
      tmfitz
      Frequent Visitor
      8 years ago

      I am having the same issue.  Cannot get my queries to Salesforce to refresh on schedule in PBI Service.  Works fine when I refresh from PBI Desktop.

       

      Help!

      • tmfitz's avatar
        tmfitz
        Frequent Visitor
        8 years ago

        Me too!  Been trying to work with PBI support for weeks now.  Have time schedule for today.  Will come back and update you. So frustrating. :smileysad:

  • ivan_larson_cki's avatar
    ivan_larson_cki
    Helper III
    7 years ago

    I've had this problem frequently, and it seems to be a matter of the file being strained in how much it can import. File size doesn't strongly correlate with the problem as I have files of 18 MB that refresh just fine and files of only 9 MB that can't refresh automatically. But once I'm importing from ~6 or more Salesforce objects into a dataset, I'll start getting "Invalid Query Locator" errors sometimes when refreshing. Sometimes, these errors arise infrequently enough that reports will still continue to refresh most times. But once I use 8 or more Salesforce objects in one dataset, there's almost no chance that the report will ever refresh in the PBI service. I have end users who need to see information stored across this many objects for various projects, and we need a solution for this problem.

  • epresson's avatar
    epresson
    Frequent Visitor
    7 years ago

    Has anyone come up with a solution? I'm also having this issue. I have a report with 8 salesforce objects and it is not able to refresh via PBI service. 

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Getting the same issue for larger reports, sometimes just refreshing the desktop file + republishing works, other times I just have to wait. Really hope someone finds a solution to this one

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Thanks Ivan.. This solved my issue enableling the queries from uploading.  I had merged and appended tables together and received this issue "Invalid Query Locator" right after. Like many of you i was able to refresh on the PBI desktop, but failed online.  This resolved the the Invaild Query locator issue.

    Thanks Again😀