Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...4.7 Upgrade Issue4.7 Upgrade Issue
Previous
 
Next
New Post
11/18/2007 6:27 PM
 
Cliff Hammock


www.theforerunnernetwork.com
Joined: 1/9/2004
Posts: 653

I just did two DNN 455 to 470 upgrades and I am getting this error spuriously on the sites. Other than this the sites seem to be working.

I have seen this error in both public and admin mode.

A critical error has occurred.
Multiple controls with the same ID 'ScriptManager' were found. FindControl requires that controls have unique IDs.

Here are the error details.

AssemblyVersion: 04.07.00
PortalID: 28
PortalName: Mabel White Websites
UserID: 1
UserName: host
ActiveTabID: 18
ActiveTabName: Module Definitions
RawURL: /Host/Module Definitions/tabid/18/portalid/28/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.mabelwhitewebsites.com/Host/Module%20Definitions/tabid/18/portalid/28/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; SU 3.005; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 9a9f5ac2-1da9-4718-ba82-0618cf423f00
InnerException: Multiple controls with the same ID 'ScriptManager' were found. FindControl requires that controls have unique IDs.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.Control.FillNamedControlsTable
StackTrace:
Message: 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 ---

Forerunner Communications, LLC
DotNetNuke Integration Specialists
 
New Post
11/19/2007 3:51 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

how did you perform your upgrade, please compare your steps with this check list: http://www.deutschnetnuke.de/tabid/186/Default.aspx

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/19/2007 12:34 PM
 
Jon Ivar Kleveland


www.excalibur.no
Joined: 4/6/2005
Posts: 35

 

Hi,

 

I have the same problem. Have you fonund any solutions???

 

Jon

 

JI
 
New Post
11/19/2007 3:39 PM
 
Cliff Hammock


www.theforerunnernetwork.com
Joined: 1/9/2004
Posts: 653

Sebastian:

Here are my comments. I have removed your items about which there are no differences. Also note that I used two slightly different procedures in the upgrade as it relates to the new module versions.

  • Upgrade = core framework without source or module packages <<I used the Upgrade package>>
  • Check the forums at www.DotNetNuke.com for issues reported <<I did this looking for known issues. Did not see a lot of 4.7 problems so I decided to upgrade.>>
  • Stop your web site  in IIS <<I typically don't stop the website in IIS. I work directly on my dedicated server and create an upgrade folder and update my web config in there and then just copy all files to the website folder and browse the website. The entire process typically only takes a few seconds. I could stop the website in the future, but in this case I did not. And for the last several years of DNN upgrades I have not done that. So it did not seem to be an issue.>>
  • check folder /install/modules for module packages, you do not want to install/upgrade. Since DotNetNuke 4.4.0, modules with appendix .resources don't get installed, but are made available for quick installation via menu item Host :: Module Definitions.<<This is the one that I don't really understand fully what you mean by "you do not want to install/upgrade" . And I used two slightly different procedures here. But I started with the Upgrade files. For the first site upgrade there was nothing in the  Install / Modules folder. After I installed the upgrade, I copied the files from the Install package (install/modules folder) to the website and then ran the module updates from the Module Defnitions page. Then before the next upgrade, I actually copied the files from the Install version (install/modules folder) so that they would be available for install via the Host / Module Definitions menu after the site was upgraded. On the first upgrade, I did not get any errors until after I had upgraded some of the modules using the Module Definitions page. On the second upgrade, I got the aforementioned error immediately upon browsing the site after the upgrade. Then it went away after I went to some other pages and then came back to my home page. >>
  •  
  • call your web site in your browser, this will start upgrade process and module installation <<I did this with successful upgrade. Then later I was getting the errors mentioned.>>
  • install additional or updated modules either using menu item Module Definitions <<I used the Host menu Module Definitions to install the available modules>> or copy the packages to /install/module and call "/install/install.aspx?mode=installResources"

So if you can understand what I did and if my approach might have caused issues, then let me know.

Thanks.

Forerunner Communications, LLC
DotNetNuke Integration Specialists
 
New Post
11/20/2007 1:03 AM
 
ROB AX

Joined: 9/3/2004
Posts: 2185

I have been wanting to make a post about this error, but have been unable to because the Dotnetnuke forum is broken and I can only reply to existing posts... thankfully someone has now posted about this same error.

I have been upgrading my portals for years now and know the procedure well. The upgrade from 4.6.2 to 4.7 went fine apart from this error about the scriptmanager that appears randomly.. even on pages that have no modules installed.

I'll run down the checklist:

  • If you use 3rd party modules, check the developers site for compatibility and necessary updates.  - yep
  • Backup your DotNetNuke database and installation folder in file system, where DotNetNuke resides   - yep
  • create a copy of your web.config file   - yep
  • download the appropriate package from www.DotNetNuke.com
    • Upgrade = core framework without source or module packages   - yep, upgrade version
  • Check the forums at www.DotNetNuke.com for issues reported   - yep, waited a week, reading every day
  • Stop your web site  in IIS - used app_offline.htm method
  • Unzip the package into the installation directory, make sure, that existing files with same name get replaces (pay attention: source version of DNN 4 has an addition root level with library and website folders, website constains the runtime files. - uploaded and overwrote files
  • from previously used web.config copy the following entried into the new web.config - yep all fine
  • check folder /install/modules for module packages, you do not want to install/upgrade. - installed new text/html module after upgrade
  • start your web site in IIS 
  • etc... the site upgrade went flawlessly.

 Anyhow.. I've done this many times and the upgrade went fine.

 I havent' been able to pin the error down on any event.. it just shows randomly in the event viewer and I have seen it once on a page I was browsing.

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 9fdbe601-f0d5-4d4c-add4-cd199d23855d
InnerException: Multiple controls with the same ID 'ScriptManager' were found. FindControl requires that controls have unique IDs.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.Control.FillNamedControlsTable
StackTrace:
Message: 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 ---

Regards,
Rob

P.s Please get someone to fix the forum here on Dotnetnuke.com
http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6732&PROJID=23
 
 Page 1 of 4
1234Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...4.7 Upgrade Issue4.7 Upgrade Issue


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, 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 DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out