Forum Discussion

frankielee's avatar
frankielee
New Member
11 months ago
Solved

Power BI Report Builder Stopped Seeing My Workspaces

Hi all,

 

 

My power bi report builder just stopped seeing my workspace. Yesterday all was good and today when i click publish i get the following error: "Unable to retrieve groups or datasets from Power BI. Please check your internet connection and try again." (I pasted the full error below.)
Needless to say, i am connected to the internet. I can publish and see my workspace and datasets in Dax Studio and Power BI desktop just fine but for Report Builder they dissapeared.

I am the owner of the workspace, dataset etc. have been using the same workspace and dataset for 3+ years. 
Note: I have updated the latest Report builder after this error but it didnt fix.
Note: I have tried with other reports but get the same error.

Thanks



--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Api.CapacitiesOperationsExtensions.<GetCapacitiesAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ReportDesigner.BrowsePbiViewModel.<GetPremiumPerUserCapacities>d__142.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ReportDesigner.BrowsePbiViewModel.<<Initialize>b__138_0>d.MoveNext()
--- End of inner exception stack trace ---

  • Hey  frankielee ,

    This issue usually happens due to authentication or API changes in Power BI Service, especially after updates. Here are a few steps you can try:

     

    1) Sign Out and Back In: In Report Builder, go to File > Options > Power BI Service and sign out, then sign back in with your Power BI credentials. Sometimes tokens expire and cause this error.

    2) Check Workspace Visibility: Recently, datasets from "My Workspace" often appear under Shared with me in Report Builder instead of the expected location. Try checking there. If possible, move your dataset to a dedicated or Premium workspace for better stability.

    3) Verify Permissions and Tenant Settings: If you’re using an organizational account, ensure your admin has not changed tenant settings that restrict API access for paginated reports. External or guest users often face this issue.

    4) Clear Cached Credentials: Go to Windows Credential Manager and remove any stored Power BI credentials, then restart Report Builder.

    5) Check Network/Proxy Settings: If you are behind a corporate proxy, Report Builder might fail to authenticate. <system.net>

        <defaultProxy useDefaultCredentials="true"/>

    </system.net>

    6) Workaround: If the issue persists, you can create the paginated report directly from the Power BI Service (via Export > Paginated Report) and then open the .rdl in Report Builder.

     

    For Detailed Information (Reference):

    Dataset in My Workspace not showing up in Report Builder

    Can't see workspace datasets when trying to connect with report Builder

    Report Builder Unable to retrive workgroups or datasets from Powerbi error: 407 Proxy Authentication

     

     

    Best Regards,
    Nasif Azam

     

4 Replies

  • Hi frankielee,

    The error is occurring specifically when Report Builder tries to retrieve Premium capacities (GetPremiumPerUserCapacities)

     

    Solutions might fix your problem:

    1. Clear Power BI Cache and Refresh

    • Go to File → Options and Settings → Options
    • Under Power BI Service, clear any cached data
    • Restart Report Builder

    2. Bypass the Capacity Check

    • When publishing, instead of selecting from the dropdown, manually enter your workspace name
    • Or try selecting "My Workspace" first, then switch to your target workspace

    3. Check Your Power BI License/Capacity

    • Go to Power BI Service → Settings → Premium Per User (PPU) settings
    • Ensure your PPU license is still active
    • If you're using Premium capacity (check if the capacity is healthy)

    4. API Permissions Issue

    This often happens when:

    • Your organization recently changed API security policies

    • Your token has insufficient permissions for capacity operations

    So you can try this fixes(if it is API issue)

    • Sign out of Report Builder
    • Clear Windows Credentials for Power BI
    • Sign in using (Sign in with a different account)
    • Use your organizational account with full permissions

    Mostly: 

    • This is typically a temporary service issue or authentication token problem
    • The capacity API call is failing which prevents Report Builder from loading the workspace list.
    if this post helps, then I would appreciate a thumbs up and mark it as the solution to help the other members find it more quickly.
  • Hey  frankielee ,

    This issue usually happens due to authentication or API changes in Power BI Service, especially after updates. Here are a few steps you can try:

     

    1) Sign Out and Back In: In Report Builder, go to File > Options > Power BI Service and sign out, then sign back in with your Power BI credentials. Sometimes tokens expire and cause this error.

    2) Check Workspace Visibility: Recently, datasets from "My Workspace" often appear under Shared with me in Report Builder instead of the expected location. Try checking there. If possible, move your dataset to a dedicated or Premium workspace for better stability.

    3) Verify Permissions and Tenant Settings: If you’re using an organizational account, ensure your admin has not changed tenant settings that restrict API access for paginated reports. External or guest users often face this issue.

    4) Clear Cached Credentials: Go to Windows Credential Manager and remove any stored Power BI credentials, then restart Report Builder.

    5) Check Network/Proxy Settings: If you are behind a corporate proxy, Report Builder might fail to authenticate. <system.net>

        <defaultProxy useDefaultCredentials="true"/>

    </system.net>

    6) Workaround: If the issue persists, you can create the paginated report directly from the Power BI Service (via Export > Paginated Report) and then open the .rdl in Report Builder.

     

    For Detailed Information (Reference):

    Dataset in My Workspace not showing up in Report Builder

    Can't see workspace datasets when trying to connect with report Builder

    Report Builder Unable to retrive workgroups or datasets from Powerbi error: 407 Proxy Authentication

     

     

    Best Regards,
    Nasif Azam

     
  • Hi all,

    Thank you for your detailed answers. the problem has been resolved.

    I think it is either this step or just waiting it out for a while sorted it out. 
    4) Clear Cached Credentials: Go to Windows Credential Manager and remove any stored Power BI credentials, then restart Report Builder.