Hello,
I'm using the WebScriptManager in Version 10.3.20103.2171 and CRM 2.0.
<form id="form1" runat="server">
<ig:WebScriptManager ID="WebScriptManager1" runat="server"></ig:WebScriptManager>
...
I got the following error:
Runtime error in Microsoft BLOCKED SCRIPT "Sys" is undefined
at:
//<![CDATA[
Sys.WebForms.PageRequestManager._initialize(
));
Sys.WebForms.PageRequestManager.getInstance()._updateControls([], [], [], 90);
//]]>
any ideas?
Hello bodojaeger,
I have reviewed the attachment you have sent. I noticed that you are using GridView.
I suggest using ScriptManager, and see if the issue persists.
Please let me know how this worksout, or if the issue remains.
If you have further questions, please let me know as well.
Hello Vivian,
as you can see, I'm using the WebScriptManager, because I want to use the WebDataGrid.
I'm still using GridView, because the WebScriptManager and the WebDataGrid fails. This is my problem.
By now, the WebScriptManager is the only Infragistic control on the page, and it produce the error, mentioned above.
Bodo
Thank you for the update.
The error on Sys.WebForms.PageRequestManager._inititialize, mean a few things. The main reason is that the browser is not able to load the scripts. The script engines can not find the definition for Sys, Sys.Webforms, Sys.WebFormsPageManager.
As to why the browser is not able to, may be for a number of reasons, such as :
1. The browser fails to load the compressed script.
2. The required configuration for ScriptResourceHandler does not exist for the web.config.
3. The virtual directory for the web is not correctly marked as an application.
4. There may be mis-configuration of the ASP.NET as a whole.
The following documentation discusses these reasons in more depth :
http://weblogs.asp.net/chrisri/archive/2007/02/02/demystifying-sys-is-undefined.aspx
Using ScriptManager instead of the WebScriptManager we may be able to isolate the cause of the issue. If the error does not persist with the ScriptManager, then we may have to dig deeper into the controls. If it does, then we may have to take a look at the above causes.
Please let me know how this works out, or if you have any questions.
using the ScriptManager doesn't solve the problem, but I think it's something with the .Net Version. The error ist under 2.0, and after updating to 3.5 the error is gone.
For now, everything is working.
Thanks
I am glad everything is working at the moment.
If you have have further questions, please let me know.