1

Closed

A ScriptManager control must exist on the current page

description

I am getting this error message on my page even when there is script manager on my page.
Closed Jun 11, 2008 at 3:18 AM by rajbk
fixed in feature branch

comments

mayankparmar2000 wrote May 13, 2008 at 10:37 AM

Server Error in '/ReganCo' Application.

A ScriptManager control must exist on the current page.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: A ScriptManager control must exist on the current page.

Source Error:


Line 132: return sm;
Line 133: }
Line 134: throw new HttpException("A ScriptManager control must exist on the current page.");
Line 135: }
Line 136: }


Source File: E:\Softwares\Flan\FlanAjaxControls-211\Development\FeatureBranch1\Flan.Controls\UpdatePanelPopupExtender\UpdatePanelPopupExtender.cs Line: 134

Stack Trace:


[HttpException (0x80004005): A ScriptManager control must exist on the current page.]
Flan.Controls.UpdatePanelPopupExtender.get_CurrentScriptManager() in E:\Softwares\Flan\FlanAjaxControls-211\Development\FeatureBranch1\Flan.Controls\UpdatePanelPopupExtender\UpdatePanelPopupExtender.cs:134
Flan.Controls.UpdatePanelPopupExtender.OnInit(EventArgs e) in E:\Softwares\Flan\FlanAjaxControls-211\Development\FeatureBranch1\Flan.Controls\UpdatePanelPopupExtender\UpdatePanelPopupExtender.cs:145
System.Web.UI.Control.InitRecursive(Control namingContainer) +321
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Control.InitRecursive(Control namingContainer) +198

System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +834

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

wrote Jun 11, 2008 at 3:08 AM

wrote Jun 11, 2008 at 3:18 AM

rajbk wrote Jun 11, 2008 at 3:36 AM

The issue has been fixed and checked in. Thanks for reporting this.

wrote Feb 13, 2013 at 7:16 PM

wrote May 16, 2013 at 1:59 AM