We have the following structure
Splitter
Pane
Splitter
Pane
SlidingZone
SlidingPane
Button initiating
SlidingPane
SlidingPane
Spiltbar
Pane
Panel Updating
Splitbar
Pane
Splitbar
Pane
SlidingZone
SlidingPane
Sliding Pane
When we click the button it performs the ajax request and completes correctly but then a JavaScript error occurs:
Sys.ScriptLoadFailedException. The script ScriptResource.axd?{BLAH} contains multiple calls to Sys.Application.notifyScriptLoaded(). Only one is allowed.
As such no more JavaScript executes.
This is an asp:content control with the asp:ScriptManagerProxy and telerik:RadAjaxManagerProxy in the same control.
Why is this error occuring? What can we do to sort it out?
Splitter
Pane
Splitter
Pane
SlidingZone
SlidingPane
Button initiating
SlidingPane
SlidingPane
Spiltbar
Pane
Panel Updating
Splitbar
Pane
Splitbar
Pane
SlidingZone
SlidingPane
Sliding Pane
When we click the button it performs the ajax request and completes correctly but then a JavaScript error occurs:
Sys.ScriptLoadFailedException. The script ScriptResource.axd?{BLAH} contains multiple calls to Sys.Application.notifyScriptLoaded(). Only one is allowed.
As such no more JavaScript executes.
This is an asp:content control with the asp:ScriptManagerProxy and telerik:RadAjaxManagerProxy in the same control.
Why is this error occuring? What can we do to sort it out?
2 Answers, 1 is accepted
0
Hi RyanBoud,
I tried to reproduce the problem you describe but to no avail. Could you please open a new support ticket and send us a simple running project with which we can reproduce the problem?
Best wishes,
Tsvetie
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I tried to reproduce the problem you describe but to no avail. Could you please open a new support ticket and send us a simple running project with which we can reproduce the problem?
Best wishes,
Tsvetie
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
David
Top achievements
Rank 1
Rank 1
answered on 29 Aug 2008, 07:46 PM
Hi all, I ran into this problem this morning as well.
Even though it is currently August 29th, 2008, my team and I (even though it is embarassing) are still using the RadControls Q1 2007, lol. Anyway, we have about every version of the rad controls toolkits, including the one that was just released a few days ago, Q2 2008, but our project is massive and upgrading the controls is a real chore, hence it hasn't been done in a long time. Well, since the release of Firefox 3.0.1, we discovered that this version of Firefox does not like the Q1 2007 Ajax manager at all, and it would cause really vague server-side errors on post back, mainly, "Input string was not in the correct format". We finally discovered it was due to the ajax manager/ajax panels we were using in Q1 2007. So, I upgraded the ajax manager to the Prometheus Q3 2007 (we were using this ajax manager elsewhere and it seems to work ok with this version of Firefox and it allowed me to not have to change a whole lot of code).
Turns out, when I ran the new code with the new ajax manager and the new script manager I had to put on the page, I got the above error at run time. The error was thrown and all javascript stopped functioning after that. Anyway, I stumbled upon this ASP.NET forum post and it got the wheels in my head turning:
http://forums.asp.net/t/1066053.aspx
On the same page that was resulting in the Javascript runtime error we are utilizing the RadPanelBar control from Q1 2007. I looked up the RadPanelbar.js file that it utilizes and sure enough, at the very bottom of the .js file was the following line of code:
//BEGIN_ATLAS_NOTIFY
if (typeof(Sys) != "undefined"){if (Sys.Application != null && Sys.Application.notifyScriptLoaded != null){Sys.Application.notifyScriptLoaded();}}
//END_ATLAS_NOTIFY
I commented out the if statement, saved it, ran it, and no more error.
I know that we are probably the only company in the world that uses these controls still, but just in case I thought I'd post this little tid bit for the public.
Maybe it will help someone who is as crazy as we are for using such outdated controls :)
Even though it is currently August 29th, 2008, my team and I (even though it is embarassing) are still using the RadControls Q1 2007, lol. Anyway, we have about every version of the rad controls toolkits, including the one that was just released a few days ago, Q2 2008, but our project is massive and upgrading the controls is a real chore, hence it hasn't been done in a long time. Well, since the release of Firefox 3.0.1, we discovered that this version of Firefox does not like the Q1 2007 Ajax manager at all, and it would cause really vague server-side errors on post back, mainly, "Input string was not in the correct format". We finally discovered it was due to the ajax manager/ajax panels we were using in Q1 2007. So, I upgraded the ajax manager to the Prometheus Q3 2007 (we were using this ajax manager elsewhere and it seems to work ok with this version of Firefox and it allowed me to not have to change a whole lot of code).
Turns out, when I ran the new code with the new ajax manager and the new script manager I had to put on the page, I got the above error at run time. The error was thrown and all javascript stopped functioning after that. Anyway, I stumbled upon this ASP.NET forum post and it got the wheels in my head turning:
http://forums.asp.net/t/1066053.aspx
On the same page that was resulting in the Javascript runtime error we are utilizing the RadPanelBar control from Q1 2007. I looked up the RadPanelbar.js file that it utilizes and sure enough, at the very bottom of the .js file was the following line of code:
//BEGIN_ATLAS_NOTIFY
if (typeof(Sys) != "undefined"){if (Sys.Application != null && Sys.Application.notifyScriptLoaded != null){Sys.Application.notifyScriptLoaded();}}
//END_ATLAS_NOTIFY
I commented out the if statement, saved it, ran it, and no more error.
I know that we are probably the only company in the world that uses these controls still, but just in case I thought I'd post this little tid bit for the public.
Maybe it will help someone who is as crazy as we are for using such outdated controls :)