[CLOSED] The function "addScript" causing the error "Syntax Error"

Hello,

I'm migrating my application from the Ext version 2.5.3 to version 3.0.0 and I have the following problem. The surface of the application contains a various control elements of Ext, eg Panels, Trees etc.. Depending on the choice of the user is generated via an Ajax call additional controls over Javascript-Code. The javascript code is passed via the method "addScript" of the ResourceManager to the client. Then the message appears in the IE browser:

Quote:

JavaScript critical error in (unknown source location)

SCRIPT1002: Syntax error

The added script code has no error. With Fiddler, I noticed that he supplied script code is embedded in the method "Ext.onReady". But it contains additionally the two strings "<#: anchor id =" ExtNetOnReadyBegin">" and <#: anchor id = "ExtNetOnReadyEnd"> " that causes the error.

abstract from Fiddler

Quote:

scriptStartupBlock|ScriptContentWithTags|{"text":" Ext.onReady(function(){\u003c#:anchor id=\"ExtNetOnReadyBegin\" /\u003eExt.net.DirectEvent.showFailure = Ext.emptyFn;Ext.ns(\"Ext.net.DirectMethods\");

--additional scriptcode

\u003c#:anchor id=\"ExtNetOnReadyEnd\" /\u003e});","type":"text/javascript"}|

With the Ext version 2.5.3, this error does not occur. Can somebody help me, to solve this problem.

Uwe

Hi,

Do you use UpdatePanel? Can you provide test case?

1 Attachment(s)

Hello all,

I have come across the exact same problem with version 3.2.1

It is on a WebForms page containing Report Viewer / Update Panel / Script Manager embedded within Viewport / Panel / Content.

I have tried removing the Update Panel but the error still persists.

sample code

Code:

<%@ Page Language="C#" %> <%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %> <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head runat="server"> <style> div#RptViewer1_ctl09 { overflow: visible !important; } </style> </head> <body> <form id="form1" runat="server"> <ext:ResourceManager ID="ResourceManager1" runat="server" Theme="Default" DisableViewState="false" ScriptMode="Debug" /> <asp:ScriptManager ID="sm1" runat="server" EnableScriptGlobalization="true" /> <ext:Panel ID="pnl_main" runat="server" Frame="true" Layout="VBoxLayout" TitleAlign="Center" Icon="Report"> <LayoutConfig> <ext:VBoxLayoutConfig Align="Center" /> </LayoutConfig> <Items> <ext:Panel ID="pnl_param" runat="server" Layout="FitLayout" Height="300" AutoScroll="true" Hidden="true"> </ext:Panel> <ext:Panel ID="pnl_rpt" runat="server" AutoScroll="true" Flex="1"> <Content> </Content> </ext:Panel> </Items> </ext:Panel> <asp:UpdatePanel runat="server"> <ContentTemplate <rsweb:ReportViewer runat="server" ID="RptViewer1" Font-Names="Verdana" Width="100%" Height="100%" ShowPrintButton="false" Font-Size="8pt" InteractiveDeviceInfos="(Collection)" ProcessingMode="Remote" WaitMessageFont-Names="Verdana" WaitMessageFont-Size="12pt" > <ServerReport ReportPath="/Reports/test" ReportServerUrl="http://127.0.0.1/ReportServer" /> </rsweb:ReportViewer> </ContentTemplate> </asp:UpdatePanel> </form> </body> </html>

Generated Error :

Attachment 24241

There must be a way to instruct Ext.Net not to insert these anchor tags in the dynamic javascript that is generated.
(hint: ResourceManager.cs #1387)

Regards,
AnFil

Hi @AnFil,

Welcome to the Ext.NET forums!

Please clarify is the problem only reproducible with a <rsweb:ReportViewer> on the page? If yes, could, please, guide me how to introduce that component into my test project?

Hello Danil,

thank you for your prompt reply.

Please find below a basic web.config to use with sample code above.

I am using MS VS 2012 Premium Edition. I think that the ReportViewer Server control is installed along with VS2012 so it should reside in the GAC.
I have also MS SQL Server 2012 installed but i dont thin that this is required.
The Reportserver is the standard ASP.NET control used for displayin SQL Server Reporting Services Reports.
You can start a new ASP.NET Report Project from VS and it will automatically configure a simple page with a Report Viewer plus a web.config with the required references.

Code:

<?xml version="1.0" encoding="utf-8"?> <configuration> <configSections> <section name="extnet" type="Ext.Net.GlobalConfig" requirePermission="false" /> </configSections> <system.web> <compilation targetFramework="4.5"> <assemblies> <add assembly="Microsoft.Web.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /> </assemblies> </compilation>     <pages> <controls> <add assembly="Ext.Net" namespace="Ext.Net" tagPrefix="ext" /> </controls> <namespaces> <add namespace="Ext.Net" /> </namespaces> </pages> </system.web> <extnet theme="Default" licenseKey="*********************" initScriptMode="Linked" /> <system.webServer> <validation validateIntegratedModeConfiguration="false" /> <modules> <add name="DirectRequestModule" preCondition="managedHandler" type="Ext.Net.DirectRequestModule, Ext.Net" /> </modules> <handlers> <add name="DirectRequestHandler" verb="*" path="*/ext.axd" preCondition="integratedMode" type="Ext.Net.ResourceHandler" /> <add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" /> </handlers> </system.webServer> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" /> <bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Ext.Net.Utilities" publicKeyToken="2c34ac34702a3c23" /> <bindingRedirect oldVersion="0.0.0.0-2.5.0" newVersion="2.5.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Transformer.NET" publicKeyToken="e274d618e7c603a7" /> <bindingRedirect oldVersion="0.0.0.0-2.1.1" newVersion="2.1.1" /> </dependentAssembly> </assemblyBinding> </runtime> </configuration>

I hope this helps,
Regards,
AnFil

Quote:

You can start a new ASP.NET Report Project from VS

Could you, please, clarify where it is the New Project wizard? I don't see. I created a project from the "Reporting" menu item, but it doesn't look to be the case.

Hello Daniil,

Please select : File / New web site
From Project Wizard select : Installed / Templates / Visual C# / ASP.Net Reports Web Site
A new asp.net website will be created and the Report Wizard will automatially load. We dont need to create a report for our example so please cancel the report wizard (select cancel twice on the pop-up windows).
You now have a project with a default web page includinga report viewer and a web.config with the proper references.
You can disregard the local report file created (.rdlc)

Regards,
AnFil

Hello Daniil,

I have done several more tests and I do not think that you will be able to reproduce the error just with the sample i provided.

Nevertheless, I think that I have pinpointed the circumstances that can trigger this error.

I do not wish to post snippets of Ext.Net source code on the forum so I will describe the situation as best as I can.

The cause of the problem is the code in ResourceManager.cs near line #1387. There is an if/else construct with four options. When the last option is reached (which is what happens when you combine Ext.Net with ReportViewer in a WebForm page) the Resource Manager engulfs the emitted client script (which includes the Direct Method Stubs plus any JS code the the page has) between two tags namely <#: anchor id =" ExtNetOnReadyBegin">" and <#: anchor id = "ExtNetOnReadyEnd"> ". Please look at the screenshot to see the structure of the code that is emmited on the client as dynamic script. As it is obvious, the tags cause a Javascript syntax error and the problem occur.

I will try to compile an altered version of ext.net.dll that bypasses the tag insertion and test with that to see what happens.

till later,
regards,
AnFil

Quote:

The cause of the problem is the code in ResourceManager.cs near line #1387.

Well, this line is executed with a very simple page like this one below and it works well. Something else is a culprit.

Example

Code:

<%@ Page Language="C#" %> <!DOCTYPE html> <html> <head runat="server"> <title>Ext.NET v3 Example</title> </head> <body> <form runat="server"> <ext:ResourceManager runat="server" /> </form> </body> </html>

Quote:

I will try to compile an altered version of ext.net.dll that bypasses the tag insertion and test with that to see what happens.

It is unlikely that it is going to help. On your screenshot Ext.onReady's function is empty. As for <#:anchor> things they should be got rid later in life cycle. That is an internal rendering process in Ext.NET. But something goes wrong and it is not removed. Though, even if <#:anchor> would go away somehow, the function is empty still as I already mentioned. It needs to investigate the reason of that. I would be happy to investigate, but I don't think I can do it without getting it reproducible locally on my side.

Hello Daniil,

- thank you for your reply.
- It is expected that the function appears empty in the screenshot since i removed all Js code and Direct Methods removed to make things simpler. Same thing happens if there is any code between the tags).
- The important piece of information is that this pair of anchors is a temporary runtime feature that is removed (server-side) later in the dynamic script creation process.
- I will investigate if the Visual Studio debugger gets mixed up and stops the execution of the dynamic script before the tags have a chance to be removed later.
- I will also deploy code in mock production server to establish if this problem appears only during debugging but not in deployed code.

- I will post here any conclusions.

Thank you for pointing me in the correct direction,
Regards,
AnFil

Quote:

- It is expected that the function appears empty in the screenshot since i removed all Js code and Direct Methods removed to make things simpler. Same thing happens if there is any code between the tags).

Ah, okay. Thank you for clarifying.

Please try the following. There is Ext.Net\Core\InitScriptFilter.cs file. Please set a breakpoint on the line #77 inside the Transform method.

Code:

protected virtual string Transform() { return ExtNetTransformer.Transform(HttpContext.Current.Response.ContentEncoding.GetString(this.htmlList.ToArray())); // here }

Please post the result of
HttpContext.Current.Response.ContentEncoding.GetString(this.htmlList.ToArray())
and
ExtNetTransformer.Transform(HttpContext.Current.Response.ContentEncoding.GetString(this.htmlList.ToArray()));
for the problematic page.

For example, I tried with this simple page.

Example

Code:

<%@ Page Language="C#" %> <!DOCTYPE html> <html> <head runat="server"> <title>Ext.NET v3 Example</title> </head> <body> <form runat="server"> <ext:ResourceManager runat="server" /> </form> </body> </html>

Before transformation (additional manual formatting was applied to improve readability)

Code:

<!DOCTYPE html> <html> <head> <title>Ext.NET v3 Example</title> </head> <body> <form method="post" action="Work3.aspx" id="ctl01"> <div class="aspNetHidden"> <input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="" /> <input type="hidden" name="__EVENTARGUMENT" id="__EVENTARGUMENT" value="" /> <input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKMTc1OTU1NjkzNmQYAQUeX19Db250cm9sc1JlcXVpcmVQb3N0QmFja0tleV9fFgEFBWN0bDAzdX2wS05fQK2ohA5LlrJnJ+rasJgnLacyAAhcw2QXcJA=" /> </div> <script type="text/javascript"> //<![CDATA[ var theForm = document.forms['ctl01']; if (!theForm) { theForm = document.ctl01; } function __doPostBack(eventTarget, eventArgument) { if (!theForm.onsubmit || (theForm.onsubmit() != false)) { theForm.__EVENTTARGET.value = eventTarget; theForm.__EVENTARGUMENT.value = eventArgument; theForm.submit(); } } //]]> </script> <div class="aspNetHidden"> <input type="hidden" name="__VIEWSTATEGENERATOR" id="__VIEWSTATEGENERATOR" value="3FB72D2A" /> </div> <#:item selector="headstart" index="20"> <script type="text/javascript" src="/extjs/ext-all-debug-js/ext.axd?v=29937"></script> <script type="text/javascript" src="/extjs/packages/ext_theme_gray/build/ext-theme-gray-debug-js/ext.axd?v=29937"></script> <script type="text/javascript" src="/extnet/extnet-all-debug-js/ext.axd?v=29937"></script> </#:item> <#:item selector="headend"> <script type="text/javascript"> //<![CDATA[ Ext.net.ResourceMgr.init({id:"ctl03",aspForm:"ctl01",theme:"gray",locale:"en-US"}); Ext.onReady(function(){ <#:anchor id="ExtNetOnReadyBegin" /> <#:anchor id="init_script" /> <#:anchor id="ExtNetOnReadyEnd" /> }); //]]> </script> </#:item> <#:item selector="headstart" index="10"> <link type="text/css" rel="stylesheet" href="/extjs/packages/ext_theme_gray/build/resources/ext-theme-gray-all-embedded-css/ext.axd?v=29937" id="ext-theme" /> <link type="text/css" rel="stylesheet" href="/extnet/resources/css/extnet-all-debug-embedded-css/ext.axd?v=29937" id="extnet-styles" /> </#:item> <ext.net.initscript.warning> <script type="text/javascript">Ext.onReady(function(){Ext.Msg.show({title:'Warning',msg:'The <code>web.config</code> file for this project is missing the required DirectRequestModule.<br /><br /><div style="margin-left:48px;"><b>Example</b><br /><br /><code><system.web><br />  <httpModules><br />    <add name="DirectRequestModule" type="Ext.Net.DirectRequestModule, Ext.Net" /><br />  </httpModules><br /></system.web></code><br /><br />More information available at "<a href="https://examples3.ext.net/?/Getting_Started/Introduction/Overview/">Getting Started</a>".</div><br />',buttons: Ext.Msg.OK,icon: Ext.MessageBox.WARNING});});</script> </ext.net.initscript.warning> <#:item selector="warning" /> <#:item selector="viewstate" /> <#:inputs ref="init_script" index="-100" /> <#:item selector="postback" /> <#:item selector="removeblocks" /> <#:item selector="removeLeadingEmptyLines" /> <#:item selector="removeLeadingEmptyLinesAfterForm" /> </form> </body> </html>

After transformation (additional manual formatting was applied to improve readability)

Code:

<!DOCTYPE html> <html> <head> <link type="text/css" rel="stylesheet" href="/extjs/packages/ext_theme_gray/build/resources/ext-theme-gray-all-embedded-css/ext.axd?v=29937" id="ext-theme" /> <link type="text/css" rel="stylesheet" href="/extnet/resources/css/extnet-all-debug-embedded-css/ext.axd?v=29937" id="extnet-styles" /> <script type="text/javascript" src="/extjs/ext-all-debug-js/ext.axd?v=29937"></script> <script type="text/javascript" src="/extjs/packages/ext_theme_gray/build/ext-theme-gray-debug-js/ext.axd?v=29937"></script> <script type="text/javascript" src="/extnet/extnet-all-debug-js/ext.axd?v=29937"></script> <title>Ext.NET v3 Example</title> <script type="text/javascript"> //<![CDATA[ Ext.net.ResourceMgr.init({ id: "ctl03", aspForm: "ctl01", theme: "gray", locale: "en-US" }); Ext.onReady(function () { }); //]]> </script> </head> <body> <form method="post" action="Work3.aspx" id="ctl01"> <div class="aspNetHidden"> </div> <div class="aspNetHidden"> <input type="hidden" name="__VIEWSTATEGENERATOR" id="__VIEWSTATEGENERATOR" value="3FB72D2A" /> </div> </form> </body> </html>

Quote:

... I have done several more tests and I do not think that you will be able to reproduce the error just with the sample i provided.

Could you, please, clarify why you don't think that I will be able to reproduce it?:) Following your steps to create a Reports web site it looks like I've got it reproducible. I am investigating. The previous post might be disregarded.

Hello Daniil,

- I made that quotation because I observed that the compiler intervened after the Report Viewer had executed a report. Since in my posted example there was no actual report for the Report Viewer to load and process I assumed (apparently incorrectly) that that the stoppage will not occur.

- I am not yet done investigating the issue further, but my current estimate is that we are not dealing with a bug in Ext.Net, but with a specific situation where the Visual Studio JS debugger prematurely intervenes and stops code execution due to this temporary tag being inserted.

- I have discovered that if i continue code execution in VS things proceed as normal and the tag is actually removed at a later time exactly as you described.

- I will try tonight to deploy the code in production server with actual SQL Server Reports and I am confident that there will be no problem in report execution and no JS errors will occur in clients browser.

Regards,
AnFil

P.S.: Since I am new here, I would like to sincerely congratulate the whole Ext.Net team. You are doing excellent work and you make programmer's daily lives easier. I would never consider utilising Ext JS by itself. Ext.Net is the true productivity multiplier and it is an amazing experience to discover. For that I am grateful.

Thank you very much for the kind words! It motivates!

Quote:

- I will try tonight to deploy the code in production server with actual SQL Server Reports and I am confident that there will be no problem in report execution and no JS errors will occur in clients browser.

I am afraid the error will be reproducible still.

I am testing with this page of a basic Reports web site that I created following your steps.

Example

Code:

<%@ Page Language="C#" %> <%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %> <script runat="server"> protected void Page_Load(object sender, EventArgs e) { X.Js.AddScript("alert('Page_Load');"); } </script> <!DOCTYPE html> <html> <head runat="server"> <title>Ext.NET v3 Example</title> </head> <body> <form runat="server"> <ext:ResourceManager runat="server" DisableViewState="false" /> <ext:Button runat="server" Text="Ext.NET Button" Handler="alert('Hello!');" /> <asp:ScriptManager runat="server" /> <rsweb:ReportViewer runat="server"> <LocalReport ReportPath="report1.rdlc" /> </rsweb:ReportViewer> </form> </body> </html>

So far, I have found out the following.

1. The initial page load happens well.
2. Then <rsweb:ReportViewer> initiates a Microsoft AJAX request to load its content.
3. Something wrong is happening during that request - the ResourceManager is being re-rendered. It should not happen. It is like <rsweb:ReportViewer> somehow wraps a ResourceManager into <asp:UpdatePanel> (not supported, actually) or does something else. So far, I could not determine what happens exactly.
4. I could reproduce the similar (same?) issue without <rsweb:ReportViewer> in a regular ASP.NET project. If wrap a ResourceManager into an UpdatePanel, the same issue appears after a Microsoft AJAX request. Well, that is not supported scenario - having a ResourceManager inside an UpdatePanel, but I am just posting my findings hoping that it might help narrow the problem down.

Example

Code:

<%@ Page Language="C#" %> <!DOCTYPE html> <script runat="server"> protected void Page_Load(object sender, EventArgs e) { X.Js.AddScript("alert('Page_Load');"); } protected void Button_Click(object sender, EventArgs e) { } </script> <html> <head runat="server"> <title>Ext.NET v3 Example</title> </head> <body> <form runat="server"> <asp:ScriptManager runat="server" /> <asp:UpdatePanel runat="server"> <ContentTemplate> <ext:ResourceManager runat="server" /> <asp:Button runat="server" Text="ASP.NET Button" OnClick="Button_Click" /> </ContentTemplate> </asp:UpdatePanel> </form> </body> </html>

5. I am still investigating.

Hello Daniil,

- I think that during one of several tests I had the Update Panel removed and I was still getting the same behavior.
- I will also test if removing the update panel causes problems with the report viewer (which is also using ajax).

- It is a little bit messy to be honest. We have the Ext.Net Resource Manager producing dynamic JS in the App. namespace and then we have ASP.NET Script Manager doing the same in the Sys. namespace in order to load Report Viewer's scripts and then we also wrap the Report Viewer inside an Update Panel that also does also its own stuff.

- I would like to note that in the page markup only the Report Viewer is "wrapped" inside the Update Panel. The rest of the page (including all Ext.Net controls and Resource manager) are outside the Update Panel. If course this doesn't necessarily means that during dynamic script rendering the whole thing does not become intertwined.

Regards,
AnFil.

P.S.: Glad to hear it helps. It is also the thruth. Keep up the good work.

So far, I tend to think that a ReportViewer somehow forces re-rendering of ResourceManager. I cannot prove it since I don't know what happens exactly. I would be happy to look under hood of ReportViewer, but I could not find its sources.

Intuitively I feel that it is a problematic scenario to use Ext.NET and ReportViewer on the same page. Well, it is already problematic. But I mean that even if solve this problem, others might appear.

Would it be appropriate for you to move a ReportViewer into an individual page and load it as a child iframe on a page with Ext.NET as a parent?

Code:

<ext:Container runat="server" Height="300" Width="300"> <Loader runat="server" Mode="Frame" Url="Report.aspx" /> </ext:Container>

Hello Daniil,

- That is a very interesting suggestion. I assume that it will be loaded as an iframe.
(Weren't there some memory issues back in Ext JS 4.x with iframes?)

- I will thoroughly test all scenarios (UpdatePanel+ReportViewer+ExtNetPanels, ReportViewer+ExtNetPanels, ReportViewerViaLoader) and i will post the results here when completed.

Regards,
AnFil

Quote:

- That is a very interesting suggestion. I assume that it will be loaded as an iframe.
(Weren't there some memory issues back in Ext JS 4.x with iframes?)

My last investigation made me think that it is rather a problem with browsers and big JavaScript files.
http://forums.ext.net/showthread.php...l=1#post213872

So, your iframe is not going to hold Ext.NET and its JavaScript files and it should be okay.

Hello Daniil,

- just a quick trivial question.
- Can a container like the one you suggest participate in the Layout of a parent panel for instance (in italics):

Code:

<ext:Panel ID="pnl_main" runat="server" Frame="true" Layout="VBoxLayout" TitleAlign="Center" Icon="Report"> <LayoutConfig> <ext:VBoxLayoutConfig Align="Center" /> </LayoutConfig> <Items> <ext:Panel ID="pnl_param" runat="server" Layout="FitLayout" Height="300" AutoScroll="true" Hidden="true"> </ext:Panel> <ext:Container ID="pnl_rpt" runat="server" AutoScroll="true" Flex="1"> <Loader runat="server" Mode="Frame" Url="Report.aspx" /> </ext:Container> </Items> </ext:Panel>

- The reason for that is that I want the Report Viewer to resize accordingly (Viewport plus top panel collapsing ).

Regards,
AnFil

Yes, the Container itself will participate in the layout. Also the iframe element will be stretched to take all the available size in the Container. But how the report element is going to be sized inside the iframe element is not under control of Ext.NET layout.

Hello Daniil,

- I have completed the tests (without an iframe for now) and I have good news.
- Everything works as expected in all browsers tested(IE11,FF,Chrome).

Observations:
1. In debug mode inside VS 2012 the debugger stops code execution only once during the initial loading of the page. Selecting to continue allows the page to load as expected. Subsequent page reloads trigger the same behaviour (break once, select to continue, all goes well). So far, it seems that the theory that the debugger prematurely intervenes and complains about the syntax error before the anchor tag gets a chance to be replaced holds water.
2. I deployed to production server and no error is raised in the browsers and the page behaves as designed including layouts etc.
3. I made a little tweak that helped make the initial loading of the page smoother: I do not assign a report path to the report viewer inside its markup tag. I populate the ReportPath property of the Report Viewer in the page's Page_Load event. This causes the report to be loaded a bit later in the page lifecycle when all the scripts had a chance to load properly.

- I am attaching a sample page for future reference.
- The sample also demonstrates how to reload a report via a Direct Method passing user defined parameters. (The actual code that passes parameters to the report is outside the scope of this sample).

Code:

<%@ Page Language="C#" %> <%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %> <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head runat="server"> <title>Reports</title>  <style> div#RptViewer1_ctl09 { overflow: visible !important; } </style> <script runat="server"> protected void Page_Load(object sender, EventArgs e) { // check both Ext.Net and ASP.Net for initial loading status in ordr to be on the safe side if (!X.IsAjaxRequest && !Page.IsPostBack) { //Prepare Report this.RptViewer1.ServerReport.ReportPath ="\Reports\test"; //load report this.RptViewer1.ServerReport.Refresh(); } } [DirectMethod] public void Reload_Report(string some_parameter) { // pass parameters to report through ReportViewer.ServerReport.SetParameters method //reload happens in callback handler of Direct Method (client-side) } </script> <script type="text/javascript"> function reload_rpt() { //sample user parameter to pass to report var rpt_id = App.txt_rpt_id.value; App.direct.Reload_Report(rpt_id, { success: function () { //refresh report using ReportViewers client JS library. This is ReportViewer's JS library, not Ext JS. var viewer = $find("RptViewer1"); if (!viewer.get_isLoading()) viewer.refreshReport(); //end of Report Viewer JS library code }, eventMask: { showMask: true, msg: "Please wait..." }, failure: function (errorMsg) { Ext.Msg.alert("Problem", errorMsg); } }); </script> </head> <body> <form id="form1" runat="server"> <asp:ScriptManager ID="sm1" runat="server" EnableScriptGlobalization="false" ScriptMode="Debug" /> <ext:ResourceManager ID="ResourceManager1" runat="server" Theme="Default" DisableViewState="false" ScriptMode="Debug" /> <ext:Viewport ID="vport_main" runat="server" Layout="FitLayout"> <Items> <ext:Panel ID="pnl_main" runat="server" Frame="true" Layout="VBoxLayout" TitleAlign="Center" Icon="Report"> <LayoutConfig> <ext:VBoxLayoutConfig Align="Stretch" /> </LayoutConfig> <Items> <ext:FormPanel ID="pnl_param" runat="server" AutoScroll="true" Hidden="false" Title="params" Collapsible="true" > <Items> <ext:TextField ID="txt_rpt_id" runat="server" AllowBlank="true" FieldLabel="rpt_id" LabelWidth="100" MaxLength="5" EnforceMaxLength="true" MaskRe="[0-9]" MarginSpec="2" Text="1" /> </Items> <BottomBar> <ext:Toolbar ID="tlb_param" runat="server"> <Items> <ext:ToolbarFill runat="server" /> <ext:Button ID="btn_rpt_reload" runat="server" Text="Execute" > <Listeners> <Click Fn="reload_rpt" /> </Listeners> </ext:Button> </Items> </ext:Toolbar> </BottomBar> </ext:FormPanel> <ext:Panel ID="pnl_rpt" runat="server" AutoScroll="true" Flex="1"> <Content> <asp:UpdatePanel runat="server"> <ContentTemplate> <rsweb:ReportViewer runat="server" ID="RptViewer1" Font-Names="Verdana" Width="100%" Height="100%" ShowPrintButton="false" ShowFindControls="false" Font-Size="10pt" ProcessingMode="Remote" WaitMessageFont-Names="Verdana" WaitMessageFont-Size="12pt" > <ServerReport ReportPath="" ReportServerUrl="http://*.*.*.*/ReportServer" /> </rsweb:ReportViewer> </ContentTemplate> </asp:UpdatePanel> </Content> </ext:Panel> </Items> </ext:Panel> </Items> </ext:Viewport> </form> </body> </html>

I hope that this helps clarify things.

You can close the thread if you like. I would also like to test the iframe scenario but I am currently under a deadline so that will have to wait.

Regards,
AnFil.

P.S. I can send you the URL of a test production server plus relevant source code files in order to see the user experience client-side and possibly debug the Server Response and also check if any errors are raised in the browsers' JS execution. If you think that such a thing would be helpful please send an e-mail address to my e-mail so i can forward you the relevant information.

Thank you for sharing all the details! And it is great to hear all is working for you.

As for sending the files via email, we would really prefer to keep all the discussion publicly if possible. If it is absolutely not possible to keep it public, then we could consider email. Well, if all works for you, then, personally, I am okay just to close the thread right away. If any the problem re-appear or something else, you can post a follow-up or create a new thread referencing the current one and we'll investigate.

Hello Daniil,

- you can close the thread.
- Thank you very much for your help.

Regards,
AnFil