I am currently using NetAdvantage 10.3 ASP.NET, recently upgraded. This issue started happening when we upgraded.
If the site is on our test server the WebDataMenu does not display, you have to hit refresh in order for it to show up, side note: there is however a image next to the WDM that does show. If the site is run from Visual Studio then the WDM does not display and a javascript error prompt appears. There are two prompts that show, one when the page first loads and the second when you hit refresh. The two errors that show are:
Error: Sys.ArgumentUndefinedException: Value cannot be undefined.Parameter name: element
Error: Sys.ArgumentUndefinedException: Value cannot be undefined.Parameter name: handler
If I choose to debug them the following screenshot shows the error. If I debug the second error It shows the same bit of code but in a different place.
There does not seem to be a pattern to when the error occurs. It can happen when the opening page loads or it can happen when navigating through the site. Sometimes it works fine for awhile with out error and then sometimes it does it over and over for 4-5 times.
Any help or advice is highly appreciated. Let me know if i can provide any more information
Thank you
hello:
I have an ASP.NET application, which was upgraded from VS 2005 to VS 2008.
Infragistics NetAdvantage ASP.NET 2010.3
My page is using the WebDataGrid. I get a JavaScript error, only on IE 8. It was working all fine when my system had IE7.
I have created a new project using VS 2008 and copied the contents of this page, containing the infragistics grid control. Surprisingly this page loads perfectly fine.
Why is it that my existing project giving the script error? My web.config has the <xhtmlConformance mode="Transitional"/>
Please give suggestions as to what is missing.
Thank you,
Sushma
Thanks everyone for their help and time. Still have not seen th error so I'm going to go ahead and verify the answer for other users.
If you are having issues with javascript errors, double check your web.config file for:
<xhtmlConformance mode="Legacy"/>
and change it to <xhtmlConformance mode="Transitional"/>or<xhtmlConformance mode="Strict"/>Here is a article explaing why:
https://weblogs.asp.net/scottgu/gotcha-don-t-use-xhtmlconformance-mode-legacy-with-asp-net-ajax
Hi,
i think you find the solution :). You may check this article:
Our Aikido controls are dependent on MS AJAX so this may be causing the same issues. Anyway you should never use this Legacy mode. Let me know if issue persists even after this fix.
Thanks,
Lubomir
I think I may have figured out the issue. I continued to delete and remove stuff from the project I posted earlier until I had just the essential files remaining. I then ended up comparing a new project web.config file to our existing web.config file and found a difference. In the web.config file the setting:
<
xhtmlConformance mode="Legacy"/>
This appears to be causing the problem, when I change it to
<xhtmlConformance mode="Strict"/> or <xhtmlConformance mode="Transitional"/>
Then the error does not show or I haven't been able to get it to show. I will wait to make sure the error does not pop up anymore but would like to see what you guys find also. I will post back if this ends up being the fix. I'm not sure why or how this changed when we did the upgrade to 10.3 or why the Infragistic controls seem to be effected by it.
I put together a project consisting only a few files from the actual project that reproduces the error. It took me anywhere from 1 or 2 page refreshes to get the error to show to as much as 50+ refreshes for it to show so your experience may vary. The pages are very stripped down compared to what they normally are the wdm is populated by a couple listarrays defined in the codebehind instead of listarrays created from our database. The error still occurs though so I think this should help.