當打開查詢設計器時，報表生成器3.0凍結

Question

我一直在尋找天，我找不到解決此問題的任何東西。當我打開報告生成器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). 

Answer 1

我能夠通過重新創建數據源和查詢來解決此問題。這是非常耗時的，但一直是解決這個問題的唯一方法。