首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >报表生成器3.0在打开查询设计器时冻结

报表生成器3.0在打开查询设计器时冻结
EN

Stack Overflow用户
提问于 2014-01-15 17:42:00
回答 4查看 4.8K关注 0票数 2

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

数据集嵌入在报表中。

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

我所做的测试:

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

SSRS日志在引用我将要打开的报告时显示了这一点。

代码语言:javascript
复制
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).
EN

回答 4

Stack Overflow用户

回答已采纳

发布于 2014-01-17 21:23:03

我能够通过重新创建数据源和查询来解决这个问题。这是相当费时的,但却是解决这个问题的唯一办法。

票数 3
EN

Stack Overflow用户

发布于 2020-10-03 08:56:45

我本人曾多次遇到这个问题,这主要是由两个原因引起的:

  1. 您正在尝试编辑使用报表生成器的不同版本创建的报表。不幸的是,RB中没有实质性的向后兼容性,所以只有在这种情况下才能从头重新创建DataSource和DataSet。
  2. DataSet的源缺少一个列--即在Dataset定义中有一个列[Name],但是表--即源--没有它。

有时还有其他原因,但我无法证实。然而,上面的清单我能够确认。

票数 1
EN

Stack Overflow用户

发布于 2020-07-27 19:22:49

我也遇到过类似的问题,如果右键单击dataset并单击"Query",那么Report就会冻结,但解决方法更简单:单击"Dataset Properties“而不是"Query”,然后单击"Query“按钮(如果愿意,可以直接在"Query”框中编辑)。

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/21144520

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档