You don't have permissions to the underlying external dataset.

[sumneshnepalia]

I have downloaded a published Power BI report and get following error when loading local model

Feedback Type:
Frown (Error)

Timestamp:
2024-10-16T08:52:26.9536921Z

Local Time:
2024-10-16T09:52:26.9536921+01:00

Session ID:
cbd11741-a83b-4de7-a782-492aad1a965f

Release:
October 2024

Product Version:
2.137.751.0 (24.10) (x64)

Stack Trace:
Microsoft.PowerBI.Client.Windows.AnalysisServices.ExternalDatasetPermissionValidationException
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesCallbackHelper.<AddPowerBIServiceCredentialsToConnectionStringIfRequired>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.QueryEvaluator.ProxyModelEvaluator.<GetConnectionStringBuilder>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.QueryEvaluator.ProxyModelEvaluator.<EvaluateProxyModelQuery>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.QueryEvaluator.ProxyModelEvaluator.<>c__DisplayClass15_0.<<EvaluateForLoadAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Evaluation.LoadToModelQueryEvaluationService.<EvaluateForLoadAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass11_0`1.<<RunInAsyncActivity>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__11`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.<EvaluateQueries>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.<ExecuteInternal>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.<Execute>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass11_0`1.<<RunInAsyncActivity>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<RunInAsyncActivity>d__11`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.<>c__DisplayClass18_0.<<LoadToModel>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<>c__DisplayClass9_0.<<RunExtendedModelChangeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<ContinueWithAsyncOperation>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.<LoadToModel>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.<>c__DisplayClass43_0.<<StartLoadToReportFlow>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext()

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.137.751.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesCallbackHelper+<AddPowerBIServiceCredentialsToConnectionStringIfRequired>d__0","Error":"Microsoft.PowerBI.Client.Windows.AnalysisServices.ExternalDatasetPermissionValidationException","MethodDef":"MoveNext","ErrorOffset":"571","ErrorCode":""}

InnerException0.Stack Trace:
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesCallbackHelper.<AddPowerBIServiceCredentialsToConnectionStringIfRequired>d__0.MoveNext()

OS Version:
Microsoft Windows NT 10.0.22621.0 (x64 en-GB)

CLR Version:
4.8 or later [Release Number = 533320]

Peak Virtual Memory:
71.2 GB

Private Memory:
684 MB

Peak Working Set:
1.12 GB

IE Version:
11.1.22621.0

User ID:
908d268d-f73c-427a-87de-98826877ff25

Workbook Package Info:
1* - en-GB, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

AS Live Connection:
True

Enabled Preview Features:
PBI_sparklines
PBI_scorecardVisual
PBI_fieldParametersSuperSwitch
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_newCard
PBI_buttonSlicerAuthoring
PBI_EimLessElevatedUser
PBI_mobileAutoReportLayout
PBI_daxInlineCopilot
PBI_aiNarrativesVisual
PBI_generateMeasureDescriptionsButton
PBI_visualCalculationsAuthoring
PBI_desktopReportAuthoringCopilot

Disabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_b2bExternalDatasetSharing
PBI_enhancedTooltips
PBI_onObject
PBI_odspSaveBackgroundUpload
PBI_publishDialogsSupportSubfolders
PBI_tmdlInDataset
PBI_enhancedReportFormat
PBI_directLakeRemoteModeling
PBI_advancedSlicerTypeList
PBI_qnaImproveLsdlCopilot

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
100%

Supported Services:
Power BI

[MakeCodeNotWar]

For me the solution was to change the connection.

Go to 'File' -> 'Options & Settings' -> 'Data source settings' 

Now select the Sql analytics endpoint of your lakehouse, NOT the lakehouse itself! For a model modification you have to use a DirectQuery connection instead of a DirectLake connection.

[sumneshnepalia · Accepted solution]

thanks @Ritaf1983  for response, I resolved it by downoloading with following option

A copy of your report and data (.pbix)

[Ritaf1983]

Hi @sumneshnepalia 

The error you're encountering seems to be related to permission validation issues when trying to connect to an external dataset in Power BI. Here are a few things to check and possible solutions:

### 1. **External Dataset Permissions**
- **Re-authentication**: Ensure that you are signed into Power BI Desktop with the same account that has access to the external dataset. Sometimes, the issue arises if the Power BI Desktop session is not authenticated correctly, or if there is a mismatch between the account credentials.
- **Clear Credentials**: Go to "File" > "Options and settings" > "Data source settings," find the external dataset, and clear the existing credentials. Then, re-authenticate to see if this resolves the issue.
- **Check Service Account Permissions**: Verify that the account you're using has the correct permissions set up on the Power BI Service. If the dataset was configured with a specific service account, ensure that it has the appropriate level of access.

### 2. **Check for DirectQuery Issues**
- Since the error mentions a connection issue, it's possible that the dataset you're trying to access uses DirectQuery. Make sure that all required ports are open and that network settings allow for the necessary connections. If using a VPN or proxy, check that it's not blocking the required access.

### 3. **Try Refreshing from Power BI Service**
- Since refreshes still work through the Power BI Service, try downloading a fresh copy of the report from the service. There might have been a configuration change or update that isn’t reflected in your local version.

### 4. **Update Power BI Desktop**
- **Downgrade or Update**: Make sure you’re using the latest version of Power BI Desktop. If you recently updated and started facing issues, consider downgrading to the previous stable version to see if the problem persists. Occasionally, new releases can introduce bugs that affect connectivity.

### 5. **Use Diagnostic Tools**
- **View Diagnostics**: Use the diagnostic tools in Power BI Desktop to get more details on why the connection fails. This can provide insights into any missing configurations or specific network-related issues.
- **Service-Specific Permissions**: Ensure that the configuration on the dataset in the Power BI Service is consistent with how it was set up for local connections, especially for live connections or datasets that connect via Analysis Services.

If the above suggestions do not solve the issue, consider reaching out to your IT or network team to verify any changes in network policies or security settings, or check with Microsoft Support for deeper insights.

Guide for support tickets :

https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly