PowerBi 报告服务器PBIRS 2021 年 1 月说“无法连接到分析服务服务器”,即使我没有使用它

如何解决PowerBi 报告服务器PBIRS 2021 年 1 月说“无法连接到分析服务服务器”,即使我没有使用它

我们有 3 台服务器开发、测试和直播。每个服务器是:

  • 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 supportedVersion)
   --- End of inner exception stack trace ---
   at Microsoft.PowerBI.DataExtension.Msolap.SchemaCommand.GetModelMetadata(String catalogName,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?

我可以:

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

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

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

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

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

解决方法

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

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

,

不是答案,而是替代方案/解决方法。

我们最终创建了一个新的空白报告并将所有内容剪切并粘贴到其中。现在它可以运行了。

我们仍然不知道是什么导致它失败。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
参考1 参考2 解决方案 # 点击安装源 协议选择 http:// 路径填写 mirrors.aliyun.com/centos/8.3.2011/BaseOS/x86_64/os URL类型 软件库URL 其他路径 # 版本 7 mirrors.aliyun.com/centos/7/os/x86
报错1 [root@slave1 data_mocker]# kafka-console-consumer.sh --bootstrap-server slave1:9092 --topic topic_db [2023-12-19 18:31:12,770] WARN [Consumer clie
错误1 # 重写数据 hive (edu)> insert overwrite table dwd_trade_cart_add_inc > select data.id, > data.user_id, > data.course_id, > date_format(
错误1 hive (edu)> insert into huanhuan values(1,'haoge'); Query ID = root_20240110071417_fe1517ad-3607-41f4-bdcf-d00b98ac443e Total jobs = 1
报错1:执行到如下就不执行了,没有显示Successfully registered new MBean. [root@slave1 bin]# /usr/local/software/flume-1.9.0/bin/flume-ng agent -n a1 -c /usr/local/softwa
虚拟及没有启动任何服务器查看jps会显示jps,如果没有显示任何东西 [root@slave2 ~]# jps 9647 Jps 解决方案 # 进入/tmp查看 [root@slave1 dfs]# cd /tmp [root@slave1 tmp]# ll 总用量 48 drwxr-xr-x. 2
报错1 hive> show databases; OK Failed with exception java.io.IOException:java.lang.RuntimeException: Error in configuring object Time taken: 0.474 se
报错1 [root@localhost ~]# vim -bash: vim: 未找到命令 安装vim yum -y install vim* # 查看是否安装成功 [root@hadoop01 hadoop]# rpm -qa |grep vim vim-X11-7.4.629-8.el7_9.x
修改hadoop配置 vi /usr/local/software/hadoop-2.9.2/etc/hadoop/yarn-site.xml # 添加如下 <configuration> <property> <name>yarn.nodemanager.res