打开查询设计器时，Report Builder 3.0会冻结

Posted 2023-02-04

我一直在寻找几天，我找不到任何解决这个问题的方法。当我打开报表生成器3.0时，我能够看到并打开报表。我可以打开报告。我可以查看数据集属性。当我点击查询时，它会挂起。如果特定报告中的查询仅为文本，我可以打开它。如果查询是使用查询设计器的gui进行的，则会冻结并最终失败。

数据集嵌入在报告中。

如果我创建一个新报告，我只能在该报告中打开查询设计器。它似乎只影响本周之前创建的报告。

测试我已经执行：

• 不同的用户档案
• 不同的用户
• 不同的用户配置文件在不同的计
• 另外计算机上的不同用户
• 安装sql server 2008 r2 SP2
• 卸载并重新安装报表生成器3.0

SSRS日志在参考我正在打开的报告时显示了这一点。

library!ReportServer_0-2!1328!01/15/2014-12:24:15:: Call to GetSystemPropertiesAction().
library!ReportServer_0-2!11fc!01/15/2014-12:24:15:: Call to ListChildrenAction(/, False).
library!ReportServer_0-2!1328!01/15/2014-12:24:18:: Call to ListChildrenAction(/CustomReports, False).
library!ReportServer_0-2!11fc!01/15/2014-12:24:19:: Call to ListChildrenAction(/CustomReports/Missing Weeks Reports, False).
library!ReportServer_0-2!1328!01/15/2014-12:24:21:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!11fc!01/15/2014-12:24:21:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!11fc!01/15/2014-12:24:21:: Call to GetReportDefinitionAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!1328!01/15/2014-12:24:22:: Call to GetItemDataSourcesAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!11fc!01/15/2014-12:24:22:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!11fc!01/15/2014-12:24:22:: Call to GetReportItemReferencesAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!1328!01/15/2014-12:24:23:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!1328!01/15/2014-12:24:23:: Call to GetReportParametersAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!11fc!01/15/2014-12:24:23:: Call to GetPropertiesAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC, PathBased).
library!ReportServer_0-2!1328!01/15/2014-12:24:23:: Call to CreateReportEditSessionAction(Parent=/CustomReports/Missing Weeks Reports, Report=MW_Royalties_RBC).
library!ReportServer_0-2!11fc!01/15/2014-12:24:27:: Call to GetItemTypeAction(/Shared Data Sources/Company 001).
library!ReportServer_0-2!1328!01/15/2014-12:24:27:: Call to GetDataSourceContentsAction(/Shared Data Sources/Company 001).
library!WindowsService_0!7cc!01/15/2014-12:28:56:: i INFO: Call to CleanBatch()
library!WindowsService_0!7cc!01/15/2014-12:28:56:: i INFO: Cleaned 0 batch records, 0 policies, 4 sessions, 0 cache entries, 2 snapshots, 12 chunks, 0 running jobs, 0 persisted streams, 25 segments, 25 segment mappings, 0 edit sessions.
library!WindowsService_0!7cc!01/15/2014-12:28:56:: i INFO: Call to CleanBatch() ends
library!ReportServer_0-2!1328!01/15/2014-12:34:37:: Call to GetSystemPropertiesAction().
library!ReportServer_0-2!1130!01/15/2014-12:34:37:: Call to ListChildrenAction(/, False).
library!ReportServer_0-2!1328!01/15/2014-12:34:39:: Call to ListChildrenAction(/CustomReports, False).
library!ReportServer_0-2!1130!01/15/2014-12:34:41:: Call to ListChildrenAction(/CustomReports/Submitted Weeks Reports, False).
library!ReportServer_0-2!1328!01/15/2014-12:34:43:: Call to ListChildrenAction(/CustomReports/Submitted Weeks Reports/Discard, False).
library!ReportServer_0-2!13f4!01/15/2014-12:34:45:: Call to ListChildrenAction(/CustomReports/Submitted Weeks Reports, False).
library!ReportServer_0-2!1130!01/15/2014-12:34:46:: Call to ListChildrenAction(/CustomReports, False).
library!ReportServer_0-2!13f4!01/15/2014-12:34:48:: Call to ListChildrenAction(/CustomReports/Missing Weeks Reports, False).
library!ReportServer_0-2!1130!01/15/2014-12:34:50:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!13f4!01/15/2014-12:34:50:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!13f4!01/15/2014-12:34:50:: Call to GetReportDefinitionAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!1130!01/15/2014-12:34:51:: Call to GetItemDataSourcesAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!13f4!01/15/2014-12:34:51:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!13f4!01/15/2014-12:34:51:: Call to GetReportItemReferencesAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!1130!01/15/2014-12:34:51:: Call to GetItemTypeAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!1130!01/15/2014-12:34:51:: Call to GetReportParametersAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC).
library!ReportServer_0-2!13f4!01/15/2014-12:34:52:: Call to GetPropertiesAction(/CustomReports/Missing Weeks Reports/MW_Royalties_RBC, PathBased).
library!ReportServer_0-2!1130!01/15/2014-12:34:52:: Call to CreateReportEditSessionAction(Parent=/CustomReports/Missing Weeks Reports, Report=MW_Royalties_RBC).

答案

我能够通过重新创建数据源和查询来解决此问题。这是非常耗时的，但一直是解决这个问题的唯一方法。

另一答案

我有两个报告相同的问题，但可以通过右键单击数据集中的任何字段，然后单击“字段属性”，然后单击“查询”选项来访问查询。不要点击设计师，RB会崩溃。我将尝试将我的查询复制到txt文件，然后重新创建数据源和查询。

C

另一答案

这对我有用：

1. 我使用查询设计器上的查询创建了一个存储过程。
2. 我使用存储过程选项来调用以前创建的存储过程，而不是使用查询设计器。