Some clients need to refresh the page to see a SSRS report. I.E. when the report is initially displayed, there is no data. F5 or page refresh then displays the report. This happens to some clients, but not others. I have witnessed the problem on Vista/IE 7 and Windows 7/IE 8. Perhaps a browser setting or a network issue?

Hi, Try to clean up the IE cache, reset the IE settings, reinstall IE application to see if it can solve this issue. thanks, Jerry

I've cleared the cache and reset. I've reinstalled IE on one of the Windows 7/IE 8 clients with no luck. I'm starting to think it may be a proxy server issue.

Just curious... you said few users are able to see but others are not. It happened once to us. We had a scaled out report server in different timezone pointing to a single db and the report which had date (calendar control )as filter was displaying empty for few users and for others it showed data. The fix we did was to convert the date in to a standard format. One more option is try tracing whether SSRS is making a call to the SQL Server when loaded first time. If it is not making a call to SQL SERVER, then it should be reading from cache. Suresh My Scribbling

Sorry I haven't replied sooner; we're not using a scaled-out deployment, but I'll attempt a trace next chance I get. Another strange thing I noticed today is that the report is not paging. Some do, some don't and I can't seem to find any coding differences. update (11/22): Fixed paging problem; the report was being reloaded in the PageLoad(). Also found that some reports will display on first load and some will not. The properties on the reportviewer controls are identical. Reports are being served from the webserver. AsyncRendering = false, InteractivityPostBackMode = AlwaysAsynchronous, ProcessingMode = remote. Probably do the trace in a couple of days. update (11/26) Well, I've got it working, although I'm not sure why. Not that I'm convinced that this has anything to do with the issue, but the search criteria is displayed in a modal dialog and the report is rendered on a new page by utilizing <base target="_search">. There was already a script manager on the page so I wrapped the report viewer control in an update panel and set AsyncRendering to true. It is indeed rendering the report on first load now but I can only speculate as to why. The original symptom let me to believe that the control was rendering before the content was delivered and the combination of asyncrendering and the update panel allowed the reportviewer to refresh once the content was available. It will be a few more days before I can check with some of the other clients to see if they are getting the same results. update(12/6) The async modes have helped but not 'cured' the problem entirely. One thing I noticed was the inability to serve the report the first time appears to be related to the amount of data. The rendered HTML has 15000 lines or so. I am beginning to believe it to be a problem with a bottleneck in the network that goes to the outside world. I.E. At th office, there is no problem. On the other side of the proxy server is where most clients are having problems.

I posted the same problem and I couldn't find the solution yet: http://social.technet.microsoft.com/Forums/en-US/sqlreportingservices/thread/1473c3fe-bcd7-4712-822a-b45eb631b849 anyone?

Is there a firewall between the Reporting Server and the Client machine? In my case this was the reason.

Yes, there's at least 2 firewalls, and a proxy server. Some clients only go thru one firewall and they work fine. The ones that go thru both, and the proxy server exhibit the symptom. I'm using port 443 and allowing traffic to 'walk freely' is not an option. I still haven't found a solution.

So the clients that go thru one firewall (and i'm assuming they aren't going thru any proxy) are working fine. And the ones that going thru two firewalls & a proxy server having issue. (please correct me if this is not the case) Workaround- (not sure you cant try if you have restricted zone) 1) Disable the second firewall on one of the clients that's having issue and if issue persist, we know it's not the proxy. 2) but, if the issue resolves, you need match the firewall settings with the one that's working and update the settings. Subbu

I've seen similar problems with some applications. To test my theory, add a button and execute a Form (or container) Show or Repaint event to get the UI to re-run its local code. The new WPF versions of VB are especially prone to this issue but I've seen in in earlier versions as well.__________________________________________________________________ William Vaughn Mentor, Consultant, Trainer, MVP http://betav.com http://betav.com/blog/billva http://www.hitchhikerguides.net Hitchhikers Guide to Visual Studio and SQL Server (7th Edition) Please click the Mark as Answer button if a post solves your problem!

Unfortunately, I have no control over the firewalls, and the groups that are do not make changes without formal policy changes. This could be a while.

I really don't understand about firewalls but I asked the Security Specialists to look at the firewall logs at the moment I try to access the Reporting Services and they identified there was an issue there. This way they didn't even try to avoid the correction. Maybe this way you could get them to solve it.

Update: still having an issue, haven't had an opportunity to work with the team 'owning' the firewall. Other more pressing matters have this problem on back burner...