Forum Discussion
Solved
Error connecting to Azure Analysis Services after PowerBI October 2020 upgrade
Hi After upgrading the PowerBI report server from May 2020 to October 2020, connection to Azure Analysis Services is having error below: I am able to test successfully the connection in t...
Hi iamsordz
Thank for your patience.
We have found a mitigation for some customers that are experiencing this issue in the October release. Let me know if the following works for you:
Copy the following libraries from the bin directory of PowerBI Desktop for RS into PowerBI Report Server's PowerBI directory
- For Desktop for RS, copy the following files from C:\Program Files\Microsoft Power BI Desktop RS\bin (adjusting for your base installation directory)
- Microsoft.AnalysisServices.AzureClient.dll
- Microsoft.AnalysisServices.AzureClient.dll.manifest
- msolap.dll
- Copy the files to Power BI Report server C:\Program Files\Microsoft Power BI Report Server\PBIRS\PowerBI (adjusting for your base installation directory)
Thanks,
Gabe
- For Desktop for RS, copy the following files from C:\Program Files\Microsoft Power BI Desktop RS\bin (adjusting for your base installation directory)
gsprague
Microsoft Employee
Microsoft EmployeeHi iamsordz
Thank for your patience.
We have found a mitigation for some customers that are experiencing this issue in the October release. Let me know if the following works for you:
Copy the following libraries from the bin directory of PowerBI Desktop for RS into PowerBI Report Server's PowerBI directory
- For Desktop for RS, copy the following files from C:\Program Files\Microsoft Power BI Desktop RS\bin (adjusting for your base installation directory)
- Microsoft.AnalysisServices.AzureClient.dll
- Microsoft.AnalysisServices.AzureClient.dll.manifest
- msolap.dll
- Copy the files to Power BI Report server C:\Program Files\Microsoft Power BI Report Server\PBIRS\PowerBI (adjusting for your base installation directory)
Thanks,
Gabe
Hi gsprague
Thanks for the workaround for PowerBI report connecting to Azure Analysis Services.
But now similar issue is encountered for published PowerBI report connecting to Azure SQL. Do I need to copy other files for this?
Here is the PowerBI log:
2021-01-26 23:03:10.2732|ERROR|53|PBI.Win.DataExtensionException|ExceptionType:Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException;DataExtensionErrorDetails:Details: Message=Failed to get CSDL., HResult=0x80004005, ErrorCode=QuerySystemError, Language=en-US, ProviderErrorCode=0xC1070000, ProviderErrorMessage=[2663DD5278984E7565A2F88E29150C3F45B0F0A259F58B6FD892970FE6450AA7], ProviderGenericMessage=[COM error: COM error.], ErrorSource=PowerBI, ErrorSourceOrigin=MsolapWrapper, OnPremErrorCode=, InnerErrorDetails=[Type=MsolapWrapper.MsolapWrapperException, Message=Failure encountered while getting schema];stackTrace: at Microsoft.PowerBI.DataExtension.Msolap.SchemaCommand.GetModelMetadata(String catalogName, String perspectiveName, String supportedVersion) at Microsoft.PowerBI.ReportingServicesHost.LocalReportProcessingHost.ExecuteSchemaCommand[T](ExploreHostDataSourceInfo dataSourceInfo, IDbConnectionPool connectionPool, IConnectionFactory connectionFactory, IConnectionUserImpersonator connectionUserImpersonator, QueryExecutionOptionsBase queryExecutionOptions, ITelemetryService telemetryService, Func`2 action, String failTelemetryMessage, ServiceErrorStatusCode statusCode, ExploreBaseEvent exploreEvent);message:GetModelMetadata;| RequestID = 2dfeffdb-1328-27b3-9a33-24f8395cd3b6 ClientSessionID = 95ce6add-0181-ae28-35c1-8e8a9ebca519 2021-01-26 23:03:10.2732|ERROR|53|PBI.Win.ReportingServicesHostTrace|type:Error;message:library:Throwing Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: , Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'f7e28acc-345b-4677-865c-740ed0704517_-233041988'. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schema at MsolapWrapper.Utils.ThrowErrorIfHrFailed(Int32 hr, String message) at MsolapWrapper.CDbSchemaRowsetWrapper.ExecuteSchemaRowset(Guid schema, Object[] restrictions, PropertySetCollection propSets) at MsolapWrapper.SchemaCommand.ExecuteReader(Guid schema, Object[] restrictions) at MsolapWrapper.SchemaCommand.GetModelMetadata(Object[] restrictions) at Microsoft.PowerBI.DataExtension.Msolap.SchemaCommand.GetModelMetadata(String catalogName, String perspectiveName, String supportedVersion) --- End of inner exception stack trace --- at Microsoft.PowerBI.DataExtension.Msolap.SchemaCommand.GetModelMetadata(String catalogName, String perspectiveName, String supportedVersion) at Microsoft.PowerBI.ReportingServicesHost.LocalReportProcessingHost.ExecuteSchemaCommand[T](ExploreHostDataSourceInfo dataSourceInfo, IDbConnectionPool connectionPool, IConnectionFactory connectionFactory, IConnectionUserImpersonator connectionUserImpersonator, QueryExecutionOptionsBase queryExecutionOptions, ITelemetryService telemetryService, Func`2 action, String failTelemetryMessage, ServiceErrorStatusCode statusCode, ExploreBaseEvent exploreEvent) --- End of inner exception stack trace ---;;| RequestID = 2dfeffdb-1328-27b3-9a33-24f8395cd3b6 ClientSessionID = 95ce6add-0181-ae28-35c1-8e8a9ebca519 2021-01-26 23:03:10.2732|ERROR|53|Failure in conceptualschema| RequestID = 2dfeffdb-1328-27b3-9a33-24f8395cd3b6 ClientSessionID = 95ce6add-0181-ae28-35c1-8e8a9ebca519 Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'f7e28acc-345b-4677-865c-740ed0704517_-233041988'. Verify that the connection information is correct and that you have permissions to access the data source. ---> Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schemaThanks.
George