Forum Discussion

AAAA's avatar
AAAA
Frequent Visitor
3 years ago
Solved

Rest API datasets error PowerBISqlCommandTimeout

Hello 

 

When running the rest api call: 

Invoke-RestMethod -Uri "https://api.powerbi.com/v1.0/myorg/admin/datasets"  -Headers $token -Method Get
 
I am getting this error (started today):
 
{
    "error": {
        "code": "PowerBISqlCommandTimeout",
        "pbi.error": {
            "code": "PowerBISqlCommandTimeout",
            "parameters": {},
            "details": []
        }
    }
}
Anybody knows what it could be? I can't find any reference to PowerBISqlCommandTimeout.
 
Thanks 
Miguel
 
 
 
 
 

 

Need Help
  • AAAA's avatar
    AAAA
    3 years ago

    Managed to solve the issue by adding this before the webcall:

    $client = [System.Net.Http.HttpClient]::new()
    $client.Timeout = 300
     
    Happy weekend everybody!
     

4 Replies

  • ibarrau's avatar
    ibarrau
    Super User
    3 years ago

    Hi. Is that all the error? can you check for a status code and text of the response? that might helps us understand more about the issue.

    Regards,

    • AAAA's avatar
      AAAA
      Frequent Visitor
      3 years ago

      Thanks for checking.

      That is all the error message unfortunately.

       

      If instead I use the MicrosoftPowerBIMgmt.Data Get-PowerBIDataset method in PowerShell:

       

      Get-PowerBIDataset -Scope Organization


      I get this error:

      Get-PowerBIDataset: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.

       

      I've no idea where to change the timeout.

       

      Thanks

      • ibarrau's avatar
        ibarrau
        Super User
        3 years ago

        That's weird. A request will always response a status code.

        Check adding a "Top" or "First" parameter on the MicrosoftPowerBIMgmt.Data for getting a small number. If that's not working, then you might have an access or permission issue with that token.

        Regards,

  • AAAA's avatar
    AAAA
    Frequent Visitor
    3 years ago

    Managed to solve the issue by adding this before the webcall:

    $client = [System.Net.Http.HttpClient]::new()
    $client.Timeout = 300
     
    Happy weekend everybody!