[英]SSRS Data Driven Subscription Not Generating File
In SQL Server 2014 I have a data driven subscription that is executing successfully, but no file is generated.在 SQL Server 2014 中,我有一个成功执行的数据驱动订阅,但没有生成文件。 It is a Windows File Share subscription and the report has three parameters.
它是 Windows 文件共享订阅,报告包含三个参数。 I've tried removing all the parameters to see if it was an issue with that, but it still does not work.
我已经尝试删除所有参数以查看是否存在问题,但它仍然无法正常工作。 I've also verified the file path and the query the subscription is based is correct so don't think there is an issue there.
我还验证了文件路径,并且订阅所基于的查询是正确的,所以不要认为那里有问题。
The subscription returns the message:订阅返回消息:
Processing: 0 processed of 281 total;
处理:0 处理,共 281 个; 0 errors.
0 个错误。
EDIT #1:编辑#1:
More information:更多信息:
Images of steps followed:后续步骤的图片:
EDIT #2:编辑#2:
I'm getting the following errors from the log file located at "C:\Program Files\Microsoft SQL Server\MSRS12.MYINSTANCE\Reporting Services\LogFiles"我从位于“C:\Program Files\Microsoft SQL Server\MSRS12.MYINSTANCE\Reporting Services\LogFiles”的日志文件中收到以下错误
1) Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 1355, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. 1) 抛出 Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 1355, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: 报告服务器遇到配置错误。 ;
;
2) Error occurred processing subscription XX: Failure writing file filename: The report server has encountered a configuration error. 2)处理订阅XX时出错:写入文件文件名失败:报表服务器遇到配置错误。
3) Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The report server has encountered a configuration error. 3) Microsoft.ReportingServices.Diagnostics.Utilities.RSException:报表服务器遇到配置错误。 ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:报告服务器遇到配置错误。
You can check the Subscriptions
table in the ReportServer database for more detail about the subscriptions.您可以查看ReportServer数据库中的
Subscriptions
表以获取有关订阅的更多详细信息。 For more detail, you can refer to the How to monitor report subscriptions .更多详细信息,您可以参考如何监控报告订阅。
You can check the UserName column values the user have permissions and other details.您可以检查用户具有权限的 UserName 列值和其他详细信息。
SELECT *
FROM ReportServer.dbo.Subscriptions AS s
JOIN
ReportServer.dbo.Users AS us
ON us.UserID = s.OwnerId;
At the same time you can check the ExecutionLog3
table RowCount
column in order to figure out the subscribed report returned any rows.Therefore, you can find out more details about the issue of the report.同时您可以查看
ExecutionLog3
表的RowCount
列,以找出订阅的报表返回的任何行。因此,您可以找到有关报表问题的更多详细信息。
EDITED已编辑
I simulated your error in my SSRS and then handled the problem with the help of the following steps.我在我的 SSRS 中模拟了您的错误,然后在以下步骤的帮助下处理了该问题。
"An impersonation error occurred using the security context of the current user"
“使用当前用户的安全上下文发生模拟错误”
error.错误。
At first I refered to Configuration Manager Report Subscription to File Share fails with “An impersonation error occurred using the security context of the current user.”起初,我参考了Configuration Manager 报告订阅文件共享失败,并显示“使用当前用户的安全上下文发生模拟错误”。 link but it didn't help to me.
链接,但它对我没有帮助。
Did you check the log files or Report Manager for more info?您是否检查了日志文件或报告管理器以获取更多信息? If you haven't, check out ExecutionLog3 for more info about the execution of the report
如果还没有,请查看 ExecutionLog3 以获取有关报告执行的更多信息
https://docs.microsoft.com/en-us/sql/reporting-services/report-server/report-server-executionlog-and-the-executionlog3-view?view=sql-server-ver15 https://docs.microsoft.com/en-us/sql/reporting-services/report-server/report-server-executionlog-and-the-executionlog3-view?view=sql-server-ver15
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.