Report Document.Load Method Hangs

Question

The following code is an exceprt from an asp.net web application we developed.  The report file (TestReport.rpt) file was designed using a 'manually' created schema (xsd) that mirrors the structure of pApptDT. The .xsd file has no DB connection info stored in it.  NOTE: the DBServiceORA and Registrations are base and middle tier classes respectively that do the heavy lifting.
protected void Page_Load(object sender, EventArgs e)
    mDBService = (DBServiceORA)Session["DBService"];
    this.BuildReport();
protected void BuildReport()
    ReportDocument pReport = new ReportDocument();
    try
        DataTable pApptDT = Registrations.GetApptSmry (mDBService);
        string pReportFile = Server.MapPath(Global.WEB_ROOT + @"/Reports_Appointment/TestReport.rpt");
        pReport.Load(pReportFile);
        pReport.SetDataSource(pApptDT);
        MemoryStream pStream = (MemoryStream)pReport.ExportToStream(ExportFormatType.PortableDocFormat);
        HttpContext.Current.Response.Clear();
        HttpContext.Current.Response.ContentType = "application/pdf";
        HttpContext.Current.Response.AddHeader("Content-Disposition", "inline; filename=Report.pdf");
        HttpContext.Current.Response.BinaryWrite(pStream.ToArray());
    catch (Exception ex)
        Response.Write("<p>" + ex.Message + "</p><p>" + ex.StackTrace + "</p>");
    finally
        pReport.Close();
        pReport.Dispose();
This code has worked for over a year in our VS2008 development environment.  We use IIS, .Net 3.5, and ODP.Net with an Oracle 10g DB.  In our development environment we use IIS (not the built-in web server) which uses Windows integrated security.   My company recently pushed down new global policies to all desktops.  These new ploicies affected Local Security Policies and permissions on some files in the \windows\system32 directory.  When stepping through the code with the debugger, the application now hangs on the pReport.Load method.
I need help in understanding the internals of the CR ReportDocument.Load method. We think the problem is somehow associated with CR trying to connect to a non-existent DB using some protocol that got affected by the policy changes. Can anyone shed some light on our problem, in particular what's happening inside the Load method.
Thanks
Dan

Answer 1

Tried several options.
OPTION 1:
Created new VS2008 "Crystal Reports Application".
'Manually' created schema (Activity.xsd) containing no DB connection information.
Created Activity.rpt (that referenced the above Activity.xsd file).
Created our 'normal' aspx page with code as follows:.
DataTable pActivityDT = mDBService.GetDataTable("select * from E_ACT;");
string pReportFile = Server.MapPath(@"/CRTestApp1/Activity.rpt");
pReport.Load(pReportFile);
pReport.SetDataSource(pActivityDT);
MemoryStream pStream = (MemoryStream)pReport.ExportToStream(ExportFormatType.PortableDocFormat);
HttpContext.Current.Response.Clear();
HttpContext.Current.Response.ContentType = "application/pdf";
HttpContext.Current.Response.AddHeader("Content-Disposition", "inline; filename=Report.pdf");
HttpContext.Current.Response.BinaryWrite(pStream.ToArray());
First attempt at displaying the above page results in making it past the pReport.Load but hung on the pReport.SetDataSource.  All subsequent attempts hung on the pReport.Load method. (?????)
OPTION 2:
Usng the VS-generated Default page (which included the CR Viewer) the ReportSource was set declaratively as follows:
<form id="form1" runat="server">
    <div>
        <CR:CrystalReportViewer ID="CrystalReportViewer1" runat="server" AutoDataBind="True"
            Height="1039px" ReportSourceID="CrystalReportSource1" Width="901px" />
        <CR:CrystalReportSource ID="CrystalReportSource1" runat="server">
            <Report FileName="Activity.rpt">
            </Report>
        </CR:CrystalReportSource>
    </div>
</form>
Attempting to display the above page results in the application hanging.  I also tried setting the source to a non-existant file just to see if an exception would be thrown.  I got the expected 'Load report Failed' message followed by parital rendering of the CR viewer.
OPTION 3:
The report displays as expected when a new connection (pproviding the DB login credentials) is created in the CR Database Expert dialog screens and the Activity (E_ACT) table is selected and used as the datasource for the report.  With this option, the designer displays data from the Activity table in the Main Report Preview screen.  When running the application the CR Viewer prompts for DB login credentails.
Hope this  sheds some light on the issue we're having.
Dan
Edited by: Dan Cannon on Dec 10, 2009 7:23 PM