Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0ReportViewer controlReportViewer control
Previous
 
Next
New Post
1/18/2007 10:55 PM
 
Hi all,

I've developed a UI for a reporting application using the ASP2.0 wizard control hosted within a DNN module. Basically this gets the user to select the desired report then select the report parameters and then clicking the wizard Finish button should render the ASP2.0 ReportViewer control displaying the users report ... IN A NEW BROWSER session (this is so the user can run a number of reports without having to lose the ones already run).

I developed all of this as standalone ASP2.0 application to get it going and it worked fine. I've now ported the UI to a DNN module and that part works. This module then opens a new browser whose URL is a page within DNN. This page hosts the ReportViewer control which is set up with the correct parameters by the page code-behind. This is where things go wrong and I end up with an exception as follows when I try to call the ReportViewer.ServerReport.SetParameters() method :


There is an error in XML document (1, 222).
 
System.Security.SecurityException: Request failed.
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderServerReportSoapProxy.Read5_ServerInfoHeader(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderServerReportSoapProxy.Read23_Item()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer3.Deserialize(XmlSerializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)

The action that failed was: Demand
The type of the first permission that failed was: System.Security.PermissionSet

The Zone of the assembly that failed was: MyComputer
   at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods()
   at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname)
   at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
   at Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo()
   at Microsoft.Reporting.WebForms.ServerReport.SetParameters(IEnumerable`1 parameters)
   at DesktopModules_MyReports_MyReportViewer.SetReportParameters() in c:\ASP2.0\DNN_4.3.7\Website\DesktopModules\MyReports\MyReportViewer.ascx.cs:line 88

I should also add that if I change the code so that DNN launches a new browser with the url of the demo app (ie before porting to DNN) it works.

Has anyone tried anything like this ? Am I repeating work already done ? (don't think so as I didn't get any hits on "ReportViewer" when searching the forum) Am I going about it the wrong way ?

Any advice/help appreciated. I can provide more details/source as required but I just wanted to test the waters first before I made the initial post too long. Too late :-)

I'll attempt to preempt some questions here.
1) the report server (SQL Express with Advanced Services) is running on the same machine (XP with SP2) as DNN and will be configured like this in production.
2) the report server has granted permissions to a local account. I've currently configured DNN to impersonate this
same account. I realise DNN normally runs with Form authentication but I wanted to run with Windows authentication to get this going (this may be a clue).
3) the data is coming from an SQL Express database and the local account has been granted execute permissions on the stored procedures which return the report(s) data.





Thanks
Scott
 
New Post
2/16/2007 10:15 AM
 

Hi Scott,

I suppose you have already find your trouble. If not what I can tell you is that I have used reportviewer in a dnn module with windows authentication and it works perfectly now. But I have to admit that it didn't work immediatly ;)

Did you try a report whitout any parameter to see if it works ?

Michel

 
New Post
2/18/2007 7:46 PM
 
Hi Michel,

I never did find out the problem. Not long after my original post I reconfigured the site to use Forms authentication and things began to work.

Regards
Scott
 
New Post
3/14/2007 11:14 AM
 

Hi Scott and Michel,

I am working in a similar scenario and running into exactly the same issue. I am using Windows integrated authentication on Reporting Server (I'd like to keep it that way). The ASP.Net code with no DNN works like a charm and when I put the code with ReportViewer into DNN, it gives me the same error. It seems to be a SOAP marshalling error, but I am also at a loss on why it is happening in DNN. Please let me know if you have a workaround. I'll let you know if I find anything.

  • There is an error in XML document (1, 222).
    • Request failed.
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0ReportViewer controlReportViewer control


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out