I have two applications that use Ajax Controls. The first uses a modal popup to look-up some information. The second uses an update panel with a nested multiview to navigate through a setup. The second page also has a JavaScript alert when a button is clicked. When the modal popup is instantiated, or the JavaScript alert is called, I am getting the following message:
Message: Sys.InvalidOperationException: Type AjaxControlToolkit.BoxSide has already been registered. The type may be defined multiple times or the script file that defines it may have already been loaded. A possible cause is a change of settings during a partial update.
This error is only happening in our TEST and PROD environments. This does not happen in our DEV environment. TEST and PROD both have two servers; DEV has one. The error is not happening locally either.
We have checked to make sure the two servers in TEST are identical: same folder structure, same Metabase.xml files (including case), same GAC entries, etc.
Has anyone experienced this issue before, and if so, is there a solution?
Comments: I had the same issue... As a result of a Security Patch for Sharepoint. Here's a link that describes a problem similar to yours: http://social.msdn.microsoft.com/Forums/en-MY/sharepoint2010general/thread/6ea58966-7cd6-4e28-bfa1-e910f14e0722 And here's the solution that worked for me: http://forums.asp.net/post/2706576.aspx Hope this helps.
Message: Sys.InvalidOperationException: Type AjaxControlToolkit.BoxSide has already been registered. The type may be defined multiple times or the script file that defines it may have already been loaded. A possible cause is a change of settings during a partial update.
This error is only happening in our TEST and PROD environments. This does not happen in our DEV environment. TEST and PROD both have two servers; DEV has one. The error is not happening locally either.
We have checked to make sure the two servers in TEST are identical: same folder structure, same Metabase.xml files (including case), same GAC entries, etc.
Has anyone experienced this issue before, and if so, is there a solution?
Comments: I had the same issue... As a result of a Security Patch for Sharepoint. Here's a link that describes a problem similar to yours: http://social.msdn.microsoft.com/Forums/en-MY/sharepoint2010general/thread/6ea58966-7cd6-4e28-bfa1-e910f14e0722 And here's the solution that worked for me: http://forums.asp.net/post/2706576.aspx Hope this helps.