April 5, 2013 at 3:03 pm
This user has another problem with a .RDLC file that's in an Intranet application we wrote. He can bring it up fine, but if he tries to export the report to Excel, then all that happens is it pops a new instance of the browser, which immediately closes. And that's it. I tried looking at his event log, but there's nothing in there. He does have MS Office 2010 installed, so it certainly should easily be able to handle whatever Excel file that SSRS 2005 wants to hand it.
So, I'm stumped, I don't know what's wrong or why.
Kindest Regards, Rod Connect with me on LinkedIn.
April 9, 2013 at 7:44 am
Hey Rod,
Is this problem isolated to this single user or are others experiencing the same issue?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 9, 2013 at 8:35 am
I'd like to add more to what I just said. For years we've been running Windows XP Pro on all users' desktops. This year we're transitioning to Windows 7 Pro. Windows XP tended to run things in more of an "administrative" mood, whereas Windows 7 almost always runs as if you are a regular user. For better, or for worse, we got in the habit of making everyone an administrator, on their own PC. (It's a practice I don't like, but the IT group that used to administer us did that, and so when they left we continued the process.) So, what we've found is that when the user first tries to use any of our SSRS 2005 reports, it first attempts to download and install the RSClientPrint.dll, and if the user isn't an administrator on his/her machine, then that fails. Once that's happened, there's no fixing it.
Kindest Regards, Rod Connect with me on LinkedIn.
April 9, 2013 at 8:49 am
Rod,
Have you tried starting IE using run as administrator and then running the application and the report? That would help determine if this is a permissions issue and then you might be able to find a workaround.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 9, 2013 at 1:32 pm
Okay. I'm not used to using the report viewer client and rdlc files. Do report executions from rdlc files get logged in the ReportServer Database? If so, can you check in ExecutionLog2 to see if the call to generate the Excel file is even making it to the report server?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 9, 2013 at 2:06 pm
I've just checked, and there is no ExecutionLog2 table in my ReportServer database. There is an ExecutionLog table there, though, and so I checked that out. I ran the report from the Intranet website using this systax:
select * from ExecutionLog order by TimeStart DESC
but it didn't show the execution of the .RDLC report. In fact, the last report in that table is from earlier this month, so I suspect that when a report is run using a .RDLC file, it doesn't effect the ReportServer.
Kindest Regards, Rod Connect with me on LinkedIn.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply