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
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Site Settings/Add Page ErrorSite Settings/Add Page Error
Previous
 
Next
New Post
1/16/2012 11:58 AM
 
George Marchewa

Joined: 9/11/2003
Posts: 5

Hi

I am running a legacy DNN site (4.9) and the following error appears when entering site settings or adding page. I'm hoping someone could give me some suggestions on how to corrent this.

Thanks
George

---------------

DotNetNuke.Services.Exceptions.ModuleLoadException: The base class includes the field 'cmdPreview', but its type (DotNetNuke.UI.WebControls.CommandButton) is not compatible with the type of control (System.Web.UI.WebControls.LinkButton). ---> System.Web.HttpParseException: The base class includes the field 'cmdPreview', but its type (DotNetNuke.UI.WebControls.CommandButton) is not compatible with the type of control (System.Web.UI.WebControls.LinkButton). ---> System.Web.HttpParseException: The base class includes the field 'cmdPreview', but its type (DotNetNuke.UI.WebControls.CommandButton) is not compatible with the type of control (System.Web.UI.WebControls.LinkButton). at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildFieldDeclaration(ControlBuilder builder) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.TemplateControlCodeDomTreeGenerator.BuildMiscClassMembers() at System.Web.Compilation.BaseCodeDomTreeGenerator.BuildSourceDataTree() at System.Web.Compilation.BaseCodeDomTreeGenerator.GetCodeDomTree(CodeDomProvider codeDomProvider, StringResourceBuilder stringResourceBuilder, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.GenerateCode(AssemblyBuilder assemblyBuilder) at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseReader(StreamReader reader, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---
 
New Post
1/16/2012 12:20 PM
 
Richard Howells


Richard Howells's Avatar

www.dynamisys.co.uk
Joined: 3/26/2006
Posts: 2001

Looks like the ascx file has been changed so that it does not match the built code in the DLL's.

Did you install anything - or change any files? 

I think the first thing I would try is to restore back to a time when the site was working,

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
1/16/2012 3:54 PM
 
George Marchewa

Joined: 9/11/2003
Posts: 5

No, unfortunately this client has been dormant for a very long time and has now taken interest in the site again. (Thus why its still V 4.9) Any backups are showing the same error.

The only non-core module installed is "Seimple Gallery" I think but that was working fine.  I know there's been some hack attempts over the years with dropping files but dont' think any of the core files were effected.

Because its a custom skin, I've been hesitant to move the project up to a current Version of DNN (and of course the client doesn't want to $$$) but unless I can track down the exact reason for this, it might be the only approach.
 
New Post
1/16/2012 9:12 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253

As Richard indicated it appears that the errors are caused by .ascx files which do not match the compiled code. This might have been caused by a hacking attempt but more likely by a prior failed attempt to upgrade the site to a newer version.

I cannot tell from the partial error message that you posted which .ascx file may be mis-matched with its compiled code-behind file but you should be able to tell from the more complete errors logged in the Admin-->Event Viewer.

I would then try the following procedure:

  1. Download from http://dotnetnuke.codeplex.com/releases (see list to the right for all prior versions of DNN)  the install package for the EXACT same version as the site is now running. You will need to first verify that the site is on 4.09.00 and not 4.09.01, or 4.09.02, etc..
  2. Unblock the download and extract it into a temporary folder on your local system.
  3. If the error is being generated when opening the Admin-->Site Settings page, locate the corresponding .ascx file in the extracted download. In this case it would be SiteSettings.ascx found in the folder Admin/Portal/. Copy/upload via FTP, etc. this file from the extracted install package to the corresonding folder on the live site replacing the .ascx file of the same name.
  4. Browse to the site to see if the error has been resolved.
  5. Continue in a like manner to resolve other similar errors.

I would also suggest making a full backup of the live site's file system AND database before trying the above.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
1/16/2012 9:15 PM
 
Richard Howells


Richard Howells's Avatar

www.dynamisys.co.uk
Joined: 3/26/2006
Posts: 2001

I agree with Bill's suggestions.

Do backup both files AND database BEFORE you do ANYTHING.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Performance and...Performance and...Site Settings/Add Page ErrorSite Settings/Add Page Error


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