Register | Log In
Store Download Support Blogs Forums Contact
Resources > Forums
HomeHomeGetting StartedGetting StartedInstalling DotN...Installing DotN...Multiple controls with the same ID Multiple controls with the same ID 'ScriptManager' were found
Previous
 
Next
New Post
12/6/2007 3:41 AM
 
User is offline Shane Miller

www.callcenters24x7.com
Joined: 4/2/2005
Posts: 520

On upgrade from 4.6.2 to 4.7, I got the error pasted below.  Despite the error, everything seems to be working fine after the upgrade.

Stack Trace: 

[HttpException (0x80004005): Multiple controls with the same ID 'ScriptManager' were found. FindControl requires that controls have unique IDs.]
   System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +220
   System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +280
   System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +280
   System.Web.UI.Control.EnsureNamedControlsTable() +57
   System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +106
   System.Web.UI.Page.FindControl(String id) +40
   DotNetNuke.Framework.DefaultPage.SetSkinDoctype(String SkinPath) +540
   DotNetNuke.Framework.DefaultPage.LoadSkin(String SkinPath) +633
   DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) +938
   System.Web.UI.Control.OnInit(EventArgs e) +2117356
   System.Web.UI.Page.OnInit(EventArgs e) +9
   DotNetNuke.Framework.PageBase.OnInit(EventArgs e) +118
   System.Web.UI.Control.InitRecursive(Control namingContainer) +321
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +692

[PageLoadException: Multiple controls with the same ID 'ScriptManager' were found. FindControl requires that controls have unique IDs.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +363
   DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +485
   System.Web.UI.TemplateControl.OnError(EventArgs e) +105
   System.Web.UI.Page.HandleError(Exception e) +73
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6969
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
   System.Web.UI.Page.ProcessRequest() +86
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +303
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
This is the entry from the DNN log viewer:
 
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; WOW64; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.04506.30)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: c9d47bd0-313d-4c72-90f7-908c26537737
InnerException: Unhandled Error: 
FileName: 
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.Control.FillNamedControlsTable
StackTrace: 
Message: System.Exception: Unhandled Error: ---> DotNetNuke.Services.Exceptions.PageLoadException: Multiple controls with the same ID 'ScriptManager' were found. FindControl requires that controls have unique IDs. ---> System.Web.HttpException: Multiple controls with the same ID 'ScriptManager' were found. FindControl requires that controls have unique IDs. at System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) at System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) at System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) at System.Web.UI.Control.EnsureNamedControlsTable() at System.Web.UI.Control.FindControl(String id, Int32 pathOffset) at System.Web.UI.Page.FindControl(String id) at DotNetNuke.Framework.DefaultPage.SetSkinDoctype(String SkinPath) at DotNetNuke.Framework.DefaultPage.LoadSkin(String SkinPath) at DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at DotNetNuke.Framework.PageBase.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) at DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) at System.Web.UI.TemplateControl.OnError(EventArgs e) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.default_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---


Shane Miller
Call Centers 24x7
 
New Post
12/6/2007 11:22 PM
 
User is offline jaime weise

Joined: 11/5/2005
Posts: 5

If you are a developer this should make sense to you if you have touched AJAX.NET. Using ajax.net required that the first control on the form is the <asp:scriptmanager... />.

I am new to dotnetnuke but it would seem feasible to me that there are one of a few things going on.

1.There is a module installed that uses ajax incorrectly (ie not the first control on the form.)

2 There have multiple instances of a module that puts a scriptmanager on the form.

3 More than one scriptmanager controls are on the page.

Also it would seem plausible that the scriptmanager wouldn't work properly in a module for the previously stated reasons and therefore I would look to implement it somewhere globally as the first line in the form.
That way you won't have to declare it in any other modules or webpages.

 

 
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DotN...Installing DotN...Multiple controls with the same ID Multiple controls with the same ID 'ScriptManager' were found


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:

1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
Attend A Webinar
Free Demo Site
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

DotNetNuke Scoop!

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft .NET. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates the DotNetNuke Store where users purchase third party apps for the platform.
Copyright © 2002-2012 DotNetNuke Corp. / Terms of Use / Privacy
Hosted by MaximumASP