Last post Jan 31, 2011 07:40 PM by pwoodsvt
Jan 24, 2011 05:10 PM|pwoodsvt|LINK
I am new to asp.net and I was recently assigned the task of upgrading a web site from VS 2005 to VS 2008. I was able to upgrade all but two web pages. The two pages both have a SSRS report on the page. I have no problem running these pages in my development
environment. However,when I run it from the test server (Windows Server 2003 with .NET Framework 3.5 SP1) I get the error message "The control with ID 'calendarButtonExtender' requires a ScriptManager on the page. The ScriptManager must appear before any
controls that need it." This appears to be an AJAX error. Yet, there is a ScriptManager on the masterpage. Also, I do not get this error on any of the other web pages.
Jan 24, 2011 08:16 PM|cubangt|LINK
You can try the toolkitscriptmanager instead of scriptmanager. I had that same issue after upgrading our dev server with the latest versions of everything to do with Ajax and had to change my scriptmanager to the toolkitscriptmanager
Jan 24, 2011 08:20 PM|dr.maqk|LINK
share your page markup. Is calendarButtonExtender used in masterpage ? Does this page has same masterpage like other working pages ?
Jan 25, 2011 02:55 AM|chetan.sarode|LINK
It means you need put a scriptmanager in the top of page form.
So please add the scriptmanager into your MasterPage, and add a scriptmanagerproxy into content page. Put it before any controls.
the Ajax control renders.
My recommendation is to add the script manager in the CreateChildControls method of your webpart right before you create your Ajax controls.
Here is the microsoft example of this:
http://msdn.microsoft.com/en-us/library/bb862184.aspx. This example is showing the UpdatePanel fix, but the concept is the same - they add the scrip manager programatically right before they add the other controls in the CreateChildControls.
Also, notice their comment in code "//The ScriptManager control must be added first."
Hope this helps.
Jan 31, 2011 07:40 PM|pwoodsvt|LINK
Thanks cuba. I also had to make some changes to the web.config file and remove any reference to System.Web.Extensions.