- Remove From My Forums
-
Question
-
I have a problem with a report containing a subreport not running successfully when deployed to the Report Server.
The report runs successfully every time in the VS Development environment, so parameters are all setup correctly and the result is as expected accross the whole report.
No errors or warnings are listed when building or deploying.
the subreport is in the same project as the main report and deployed to the same folder in Report Manager. the individual subreport runs successfully in VS Studio (Preview Tab) and in the Report Manager portal.
the main report runs but shows the error «Subreport could not be shown» for the subreport.
Running SQL 2008 R2 Please advise.
Answers
-
Hi Mina N,
There is no need to change the data source of subreport. For the error “Subreport could not be shown”, it can be caused by various
reasons:·
Make sure that you have upload both latest main report and subreport to the report server by overwrite the original ones, as described here:
http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/0f556b62-20df-4266-a5ef-008c221d3b6d·
Make sure that the Data Source of the subreport has been configured correctly on Report Manager1. Navigate to the Security page of the subreport
2. In the security page, click Data Sources tab, choose the shared data source you have used in subreport
If all information verified and the issue still exists, could you please post more error message reported in the log file (My server has the logs
at: C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesLogFiles)?Thanks,
Lola
Please remember to mark the replies as answers if they help.
-
Proposed as answer by
Tuesday, September 6, 2011 8:08 AM
-
Marked as answer by
Lola Wang
Tuesday, September 13, 2011 9:25 AM
-
Proposed as answer by
Microsoft Forefront Threat Management Gateway 2010 Service Pack 2 Forefront Threat Management Gateway 2010 Enterprise Forefront Threat Management Gateway 2010 Standard More…Less
Symptoms
Consider the following scenario. You run the User Activity report or the Site Activity report in a Microsoft Forefront Threat Management Gateway 2010 environment. The report may run for some time and then finish suddenly and open in Windows Internet Explorer. In this scenario, the report has no details, and only the report headers and frames are displayed. You may receive the following error message in the frame where the report data should be:
Error: Subreport could not be shown
Cause
The User Activity and Site Activity reports use COM objects in the stored procedures that generate the report and therefore enable the Ole Automation Procedures option. The setting to enable Ole Automation Procedures option is a global setting on the SQL Reporting Server, and the report run may fail if this functionality is turned off while the report is still running. This problem may occur when any changes are made to the Forefront Threat Management Gateway configuration while the report is running or when multiple administrators try to run activity reports at the same time.
Resolution
To resolve this issue, install the hotfix package that is described in the following Microsoft Knowledge Base article:
2649961 Rollup 1 for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2To enable this fix, run the FixActivityReports.js script on one of the Forefront Threat Management Gateway servers. You can run this script on any Forefront Threat Management Gateway server, on an array node, or on an Enterprise Management Server.
Note The script enumerates all available arrays and corrects the stored procedure so that the Ole Automation Procedures option is not turned off for the activity reports. You may have to rerun the script if new arrays are added to the storage.
-
Start Notepad. To do this, click Start, click Run, type notepad.exe in the Open box and then click OK.
-
Paste the following script into a new file in Notepad:
var guidGenerator = new ActiveXObject("Scriptlet.TypeLib");
var fpcRoot = new ActiveXObject("FPC.Root");
try
{
WScript.Echo("Enumerating arrays:");
var arraysCollection = new Enumerator(fpcRoot.Arrays);
for (; !arraysCollection.atEnd(); arraysCollection.moveNext())
{
try
{
var array = arraysCollection.item();
var found = false;
WScript.Echo(" " + array.Name);
var rdlDefsCollection = new Enumerator(array.Reports.RdlReportDefinitions);
for(; !rdlDefsCollection.atEnd(); rdlDefsCollection.moveNext())
{
var rdlDef = rdlDefsCollection.item();
if((rdlDef.Name != "Ips_Metadata") && (rdlDef.Name != "UserActivity_Sites") && (rdlDef.Name != "Urlf_Metadata"))
{
continue;
}if (rdlDef.DataGenerationStatement.search(/--EXEC sp_configure 'Ole Automation Procedures', 0/) != -1)
{
WScript.Echo("---- DataGenerationStatement for " + rdlDef.Name +" already updated");
continue;
}found = true;
WScript.Echo("Found RDL definition " + rdlDef.Name);
WScript.Echo("---- Old version start");
WScript.Echo(rdlDef.DataGenerationStatement);
WScript.Echo("---- Old version end");
rdlDef.DataGenerationStatement = rdlDef.DataGenerationStatement.replace(/EXEC sp_configure 'Ole Automation Procedures', 0/g, "--EXEC sp_configure 'Ole Automation Procedures', 0");
WScript.Echo("---- New version start");
WScript.Echo(rdlDef.DataGenerationStatement);
WScript.Echo("---- New version end");
}
if (found)
{
WScript.Echo("Updating configuration ID...");
WScript.Echo("Old configuration ID:" + array.Reports.ReportingServicesProperties.ReportingServicesConfigurationId);
array.Reports.ReportingServicesProperties.ReportingServicesConfigurationId = guidGenerator.Guid;
WScript.Echo("New configuration ID:" + array.Reports.ReportingServicesProperties.ReportingServicesConfigurationId);WScript.Echo("Saving the current configuration...");
array.Save();
WScript.Echo("Waiting for configuration reload...");
array.WaitForReload();
}
}
catch (err)
{
WScript.Echo("An error occurred. Error Description: " + err.description);
WScript.Echo("Try running the script as an administrator");
}
}
}
catch (err)
{
WScript.Echo("An error occurred. Error Description: " + err.description);
WScript.Echo("Try running the script as an administrator");
} -
Save the file as FixActivityReports.js.
-
On a server, open an administrative command prompt.
-
Run the script in step 2 by using the following command:
cscript.exe FixActivityReports.js
Wait for the script to complete and the configuration to synchronize. You should now be able to generate User Activity and Site Activity reports.
Workaround
To work around this issue, make sure that the configuration is fully synchronized before you click Generate and View Report. To determine whether the Forefront Threat Management Gateway configuration is synchronized, click Configuration on the Monitor menu, and then check the Status column.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
References
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Need more help?
Я настроил несколько отчетов в SSRS. Каждый из этих отчетов хорошо разработан и работает должным образом.
Был сделан запрос на объединение ряда этих отчетов в один «главный» отчет. Я настроил рабочие отчеты как подотчеты и заполнил все параметры первого подотчета из «главного» отчета. Я проверил и перепроверил этот факт.
Когда я пытаюсь запустить отчет, обработка кажется слишком долгой. Вместо первого подотчета SSRS отображает Error: Subreport could not be shown.
Я проверил файл журнала, и я получаю сообщение об ошибке: processing!ReportServer_0-3!e58!04/11/2016-19:42:15::e ERROR: An error has occurred while processing a sub-report. Details: One or more parameters were not specified for the subreport ... Report.Stack trace: at Microsoft.ReportingServices.OnDemandReportRendering.SubReport.FinalizeErrorMessageAndThrow() at Microsoft.ReportingServices.OnDemandReportRendering.SubReport.RetrieveSubreport()
Я также проверил ReportServer ExecutionLogStorage и вижу, что все мои параметры заполняются в столбце параметров. Строка параметра содержит около 5 тыс. символов.
Еще немного деталей: Подотчет содержит 7 параметров:
- Администратор – одно значение
- ReportDate — одно значение
- ClientStatus — множественный выбор
- DeptStatus — множественный выбор
- Клиент — мультиселект
- AccessType — одно значение
- DataOnly — одно значение
Эти параметры отражаются в «основном» отчете. Я пытался передать параметры множественного выбора, используя методы =Parameters!ClientStatus.Value
и =Split(join(Parameters!ClientStatus.Value,","),",")
, но, честно говоря, не уверен, какой параметр отсутствует в подотчете. Насколько я могу судить, эта информация нигде не записывается.
Мы в основном отказались от этого комбинированного, «главного» отчета, но я хотел бы оставаться в курсе этого, поскольку мне интересно, может ли он повлиять на другие отчеты более тонким образом.
Если я могу предоставить дополнительную информацию, дайте мне знать.
2 ответа
Вы можете просмотреть переданные параметры, запросив ExecutionLog в базе данных SSRS.
SELECT [InstanceName]
,[ReportID]
,[UserName]
,[RequestType]
,[Format]
,[Parameters]
,[TimeStart]
,[TimeEnd]
,[TimeDataRetrieval]
,[TimeProcessing]
,[TimeRendering]
,[Source]
,[Status]
,[ByteCount]
,[RowCount]
FROM [ReportServer].[dbo].[ExecutionLog]
Вам нужно запустить отчет на SSRS-портале, очевидно, а не локально в VS или Report Designer…
2
Geert
19 Сен 2018 в 13:29
Все ли параметры в подотчете имеют значение?
Если нет, проверяются ли параметры с помощью «принять нулевое значение»?
0
C. Chagnon
12 Апр 2016 в 18:31
- Remove From My Forums
-
Вопрос
-
WSUS on Windows Server 2012. When a report is run the first summary page appears ok but none of the subsequent pages.
Error: subreport could not be shown.
Ответы
-
Restarting the server fixed the problem — made no other changes. Although WSUS installs and runs without a restart the report viewer needs one (just don’t prompt for it).
-
Помечено в качестве ответа
Stephen Strong — VTSP SQL
27 ноября 2012 г. 9:14
-
Помечено в качестве ответа
Все ответы
-
Hi,
Pls try to close the console and then reinstall microsoft report viewer 2008 redistributable
and then reboot the server to see whether the report can be run normally in the console.Regards,
Clarence
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Помечено в качестве ответа
Stephen Strong — VTSP SQL
23 ноября 2012 г. 6:51 -
Снята пометка об ответе
Lawrence Garvin
23 ноября 2012 г. 21:01
-
Помечено в качестве ответа
-
WSUS on Windows Server 2012. When a report is run the first summary page appears ok but none of the subsequent pages.
Error: subreport could not be shown.
A different thread has identified similar behavior as a FIPS-compliance configuration issue.
http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/c47cbecf-4b20-4414-98c9-197aeb847119
Although in Win2008 environments, this triggered an actual error message.
Regarding Clarence’s reference to the RV2008 redist… I’m unable to find anywhere in the WSUS v6 product documentation any reference to the requirement for RV2008 .. is this now a native component of Win2012? If not, and it’s still requires as an ancillary
installation, I would check, also, that you have the latest version of the RV2008 redist installed.Actually, inasmuch as the RV2008 is a .NET3.5 application, and Win2012 is natively .NET4, my suspicion would be that Win2012, if it has anything natively, would have RV2010 or RV2012. (It’s a shame it’s not actually documented.)
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP — Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin-
Изменено
Lawrence Garvin
23 ноября 2012 г. 21:12
-
Изменено
-
Restarting the server fixed the problem — made no other changes. Although WSUS installs and runs without a restart the report viewer needs one (just don’t prompt for it).
-
Помечено в качестве ответа
Stephen Strong — VTSP SQL
27 ноября 2012 г. 9:14
-
Помечено в качестве ответа