SSRS 报告 IIS7 上的远程连接超时
我有一组 SSRS05 报告，通过我们在 Win2k8 和 IIS7 上运行的网站的 2005 Web 服务调用。报告远程存储在 Web 服务器的另一台服务器上。
在我们的 QA 环境中，如果我们有一个运行时间超过 2 分钟的报告，我会收到以下错误：
消息：底层连接已关闭：服务器关闭了预计保持活动状态的连接。 状态：KeepAliveFailure
问题是 SQL 服务器显示存储过程已正确执行，报表服务器显示报表已正确呈现（约 15 分钟后），但 Web 服务器在 2 分钟（120 秒后）一致收到该错误）。
同样的报告在我们运行 IIS6 的旧环境中运行没有任何问题。我遇到的问题是，长时间运行的报告似乎在我们的生产环境中运行良好。 QA 环境是我们生产环境的复制，只是内容较少。
有什么想法吗？我已检查“Keep-Alive”状态并确保其已启用。我尝试将连接设置超时从 120（默认）更改为 300 秒，但在 120 秒时仍然失败。我觉得我们已经能够隔离到 IIS7，但我不知道在哪里可以更改超时设置。
I have a set of SSRS05 reports being called through the 2005 web service from our site that runs on Win2k8 and IIS7. The reports are stored remotely on another server from the web server.
In our QA environment, if we have a report that runs for longer than 2 minutes, I get the following error:
Message : The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
Status : KeepAliveFailure
The problem is that the SQL server shows that the stored procedure is executed correctly, the report server shows that the report was rendered correctly (after ~15 minutes), but the web server receives that error consistently after 2 minutes (120 seconds).
This same report runs with no problems on our old environment with ran IIS6. The issue I'm running into is that it looks like long running reports seem to run fine in our production environment. The QA environment as a replicate of our production environment, just with less juice.
Any ideas? I've checked the Keep-Alive status and made sure it's enabled. I've tried changing the connection settings timeout from 120 (default) to 300 seconds and it still fails at 120. I feel that we've been able to isolate to IIS7, but I'm at a lost where to look to change the timeout setting.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您有可能在 SharePoint 集成模式下运行吗？如果是这样，请参阅 配置错误故障排除。
Any chance you're running in SharePoint Integrated Mode? If so, see "An ASP.NET Timeout Error Occurs After Two Minutes of Report Processing" in Troubleshooting Configuration Errors.