gpt4 book ai didi

power-bi-report-server - PowerBi 报表服务器(PBIRS 2021 年 1 月)说 "couldn' t 连接到 Analysis Services 服务器“即使我没有使用它

转载 作者:行者123 更新时间:2023-12-04 17:18:46 24 4
gpt4 key购买 nike

我们有 3 台服务器 Dev、Test 和 Live。每个服务器是:

  • Win2012R2
  • SQL2016 SP2-CU15-GDR 13.0.5865.1 和
  • PBIRS:版本 1.10.7737.32652(2021 年 1 月)

我们有一份报告,适用于开发和测试,但在 Live 中失败并出现以下错误:

An unexpected error occurred
An unexpected error occurred. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.
We couldn't connect to the Analysis Services server. Make sure you've entered the connection string correctly.:
Request ID: cc3b3bf4-bedd-12ea-2de7-01a00766d42e
Time: Wed May 12 2021 08:49:54 GMT+1200 (New Zealand Standard Time)
Service version: /powerbi/libs

报告正在使用基本身份验证进行本地连接。我们已经确认查询在使用相同凭据的所有三台服务器上运行良好。此报告使用直接查询,根本不使用分析服务。

深入研究我发现的 RS 日志:

2021-05-13 08:52:02.2425|INFO|94|Received request GET /libs/scripts/pivotTableVisuals.js| RequestID = s_7a9055a3-0edd-4db1-8896-83fb3f85a5eb 
2021-05-13 08:52:02.2894|ERROR|69|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 = dc96695b-4835-a4fe-84fc-fdb32313db5b ClientSessionID = 34bde5db-4898-1197-fb8b-0c9756551a1a
2021-05-13 08:52:02.2894|ERROR|69|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 'b8ddd68c-e96b-4e4c-be7f-3b156adb72f1_-615167943'. 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 = dc96695b-4835-a4fe-84fc-fdb32313db5b ClientSessionID = 34bde5db-4898-1197-fb8b-0c9756551a1a
2021-05-13 08:52:02.2894|ERROR|100|Failure in conceptualschema| RequestID = dc96695b-4835-a4fe-84fc-fdb32313db5b ClientSessionID = 34bde5db-4898-1197-fb8b-0c9756551a1a Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'b8ddd68c-e96b-4e4c-be7f-3b156adb72f1_-615167943'. 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
2021-05-13 08:52:02.2894|INFO|50|Sending response. Response code DOMAIN\prm 200, Elapsed time 0:00:00.0641639| RequestID = dc96695b-4835-a4fe-84fc-fdb32313db5b ClientSessionID = 34bde5db-4898-1197-fb8b-0c9756551a1a
2021-05-13 08:52:02.3519|INFO|94|Received request GET /libs/styles/InfoNav-Sprites.png| RequestID = s_e58e725f-a544-4fb8-b97c-1d3dc872e85a
2021-05-13 08:52:02.3988|INFO|94|Received request POST /api/explore/reports/b8ddd68c-e96b-4e4c-be7f-3b156adb72f1/conceptualschema| RequestID = 4bb937bc-b2d3-8dc5-2817-4e3a03b60580 ClientSessionID = 34bde5db-4898-1197-fb8b-0c9756551a1a
2021-05-13 08:52:02.4300|ERROR|107|Failure in conceptualschema| RequestID = 4bb937bc-b2d3-8dc5-2817-4e3a03b60580 ClientSessionID = 34bde5db-4898-1197-fb8b-0c9756551a1a Microsoft.ReportingServices.Diagnostics.Utilities.CannotRetrieveModelException: An error occurred while loading the model for the item or data source 'b8ddd68c-e96b-4e4c-be7f-3b156adb72f1_-615167943'. 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
2021-05-13 08:52:02.4300|INFO|107|Sending response. Response code DOMAIN\prm 200, Elapsed time 0:00:00.0238187| RequestID = 4bb937bc-b2d3-8dc5-2817-4e3a03b60580 ClientSessionID = 34bde5db-4898-1197-fb8b-0c9756551a1a
2021-05-13 08:52:14.9294|INFO|109|Started clean up of embedded models
2021-05-13 08:52:14.9294|INFO|109|Finished clean up of 0 embedded models

这一行引起了我的注意:

Microsoft.PowerBI.DataExtension.Contracts.DataExtensionException: Failed to get CSDL. ---> MsolapWrapper.MsolapWrapperException: Failure encountered while getting schema

为什么要尝试运行 MSOLAP?

我可以:

  • 使用与表相同的查询和凭据创建新报告一张 map ,它会运行。
  • 将相同的报告部署回 Dev 或测试并运行。甚至在 Dev 上运行它并查询 Live。

RS 配置、防火墙设置、SQL 设置在所有 3 个服务器上都相同

到目前为止,我读过的所有博客和帖子都走向了死胡同。 Kerberos、Windows Defender、缺少 DLL 并检查并与其他服务器进行比较,它们是相同的。

为什么这个报告不能在这台服务器上运行?

编辑:我已经慢慢地从这份报告中删除了内容。我删除了额外的选项卡,删除了所有过滤器、视觉效果和切片器,但仍然失败。我删除了唯一的查询并使用相同的信用重新添加了选择相同数据的相同查询,现在它可以工作了。该错误似乎以某种方式附加到查询/模型。

最佳答案

一条评论:错误编号 5 是“拒绝访问”。类似于忽略高位的“5”的错误编号通常也称为“拒绝访问”。即第 2 行中的 HResult = 0x80004005。

可能值得查看服务帐户的 NTFS ACL 之类的内容,尤其是在 MSOLAP 二进制文件文件夹中。

关于power-bi-report-server - PowerBi 报表服务器(PBIRS 2021 年 1 月)说 "couldn' t 连接到 Analysis Services 服务器“即使我没有使用它,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/67512682/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com