Hi,
We're using SQL Reporting Services with SQL Server 2000 in a corporate environment, and have come across a problem where randomly our drill down reports, when we expand the + sign next to a group / header will reset the report as if we had just run it again. For example, I may drill down (expand) let's say two levels then click a third level and the report will "start again" with all the levels collapsed back to the original layout.
We've tried to do some basic problem solving. Here's what we (think we) know:
1) Not limited to any one report
2) It doesn't seem to matter how long a report is "left alone" for, i.e. it could be within 5 seconds of running the report that it resets, or it could be 30 minutes.
3) It's not limited to a particular drill down level.
So, my first question is whether anyone else has come across that problem? My second question is what areas should I look for that may help to diagnose the problem? My initial thoughts are:
- We're hitting a maxiumum number of concurrent users
- The session ID is becoming scrambled or expires very quickly
- There is a locking issue with the dataset driving the reports
Any suggestions (or solutions even) would be greatly appreciated.
Thanks,
MBP
We're using SQL Reporting Services with SQL Server 2000 in a corporate environment, and have come across a problem where randomly our drill down reports, when we expand the + sign next to a group / header will reset the report as if we had just run it again. For example, I may drill down (expand) let's say two levels then click a third level and the report will "start again" with all the levels collapsed back to the original layout.
We've tried to do some basic problem solving. Here's what we (think we) know:
1) Not limited to any one report
2) It doesn't seem to matter how long a report is "left alone" for, i.e. it could be within 5 seconds of running the report that it resets, or it could be 30 minutes.
3) It's not limited to a particular drill down level.
So, my first question is whether anyone else has come across that problem? My second question is what areas should I look for that may help to diagnose the problem? My initial thoughts are:
- We're hitting a maxiumum number of concurrent users
- The session ID is becoming scrambled or expires very quickly
- There is a locking issue with the dataset driving the reports
Any suggestions (or solutions even) would be greatly appreciated.
Thanks,
MBP