This is a migrated thread and some comments may be shown as answers.

Report Viewer does not work in Web mode for silverlight.

1 Answer 99 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Manav
Top achievements
Rank 1
Manav asked on 25 Nov 2010, 02:47 PM
Hi, 

I'm currently evaluating your reporting package. I've been able to deploy the report service (the one that does the rendering) successfully on both a self-hosted WCF application as well as IIS-5. I can view my reports successfully when I run the Silverlight Report Viewer in Silverlight's out of browser mode with elevated trust level enabled. 

However, I get a problem when this the elevated trust level option is unchecked or when I run the Silverlight application in it Web mode.  When the report viewer is opened it briefly tries to connect to the report viewer service, but very quickly comes up with the following error: 

"An exception occurred during the operation, making the result invalid.  Check InnerException for exception details."

I'm not sure how to get more info from the error. I'm a little confused as everything works fine in the out of browser mode, but not in the web mode. Is there a difference I need to be aware of, and you do have any suggestions as to a possible solution? 

Thanks. 

1 Answer, 1 is accepted

Sort by
0
Fletcher Aluminium
Top achievements
Rank 1
answered on 14 Dec 2010, 04:00 AM
Hey Manav,

Follow these steps:

  1. Go to Fiddler 2 and download it.
  2. Run Fiddler and go to Tools > Fiddler Options
  3. Click on Connections Tab
  4. Make sure "Use PAC Script" is ticked.
  5. Load up your Silverlight application, and then attempt to run your report (however you had it doing it before, be via button or on page load).
  6. Once it has come up with the failure go back to Fiddler, and you should see an entry with a Red Entry
  7. It should be your particular service.  i.e. ReportService.svc for example
  8. Click on the record above that which should be green and has the same name
  9. then on the right hand side, there are several tabs/buttons and one of them is called TextView
  10. Click on that and see what the error you got was.
Through this method I was able to find out that my particular inner exception was caused by an Authorization Violation.

Regards,


Shaun Sharples
Fletcher Aluminium
Tags
General Discussions
Asked by
Manav
Top achievements
Rank 1
Answers by
Fletcher Aluminium
Top achievements
Rank 1
Share this question
or