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...Administration ...Administration ...Bizarre Error in DNN 6.1.2 HTML ModuleBizarre Error in DNN 6.1.2 HTML Module
Previous
 
Next
New Post
1/24/2012 8:09 PM
 
Peter Gray

Joined: 3/2/2007
Posts: 14

Hi All,

Please help solve this issue that is causing a lot of problems for me on a production server - everything tested fine including under load testing till we switched over to production and after 4-5 hours of operations this error started to appear.

Recently, upgraded from DNN 5.2.2 to DNN 6.1.2 - the upgrade went fine but then the HTML module crashes intermittently - I have posted the error below. When I re-install/repair HTML (from the install folder of DNN 6.1.2 install) the error goes away only to return a few hours later! 

This error usually starts on a page that has an instance of the HTML module with some other module(s). However, it does not appear when these modules are first installed on the page. For example, I install an HTML, Documents and Link module on a page and they all work fine. Then after the portal is in operation for a while when I go to that page the error appears! 

ModuleId: 3376
ModuleDefId: 92
ModuleControlSource: DesktopModules/HTML/HtmlModule.ascx
AssemblyVersion: 6.1.2
PortalID: 4
UserID: 1
UserName: host
ActiveTabID: 143
RawURL: /Default.aspx
AbsoluteURL: /Default.aspx
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 05d60307-0479-43af-bbed-ebaf97b68bb9
InnerException: Cannot use 'vb' because another language has been specified earlier in this page (or was implied from a CodeFile attribute).
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.TemplateParser.ProcessError
StackTrace:

Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot use 'vb' because another language has been specified earlier in this page (or was implied from a CodeFile attribute). ---> System.Web.HttpParseException: Cannot use 'vb' because another language has been specified earlier in this page (or was implied from a CodeFile attribute). ---> System.Web.HttpParseException: Cannot use 'vb' because another language has been specified earlier in this page (or was implied from a CodeFile attribute). ---> System.Web.HttpException: Cannot use 'vb' because another language has been specified earlier in this page (or was implied from a CodeFile attribute). at System.Web.UI.TemplateParser.ProcessError(String message) at System.Web.UI.TemplateParser.ProcessScriptTag(Match match, String text, IDictionary attribs, Boolean fSelfClosed) at System.Web.UI.TemplateParser.ProcessBeginTag(Match match, String inputText) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- 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) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) 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.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.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.WebFormsModuleControlFactory.CreateModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

Thanks in advance for your help!

 
New Post
1/24/2012 9:39 PM
 
William Severance


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

That is bizarre - particularly in the way the issue reoccurs, presumably when the application pool restarts following a period of inactivity.

Please check the site's /bin folder for the following assembly file:

DotNetNuke.Modules.Html.dll

What is it's file version? - It should be 6.1.2.98. Note: unless you are working locally on the production server you'll likely need to download the file to check it's version.

Next, check the site's web.config. Is there a <codeSubDirectories> section (not commented out) that includes a reference to the Html module?
If so, that was an artifact from a late 4.9 or early 5.0 version of DotNetNuke that included a dynamically compiled Html module. It can be removed.

Finally, check the DesktopModules/HTML folder. Are there any Visual Basic (.vb extension) files still in this folder. Again, they would be artifiacts left over from late 4.9 or early 5.0 versions of DNN and should be removed.

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/25/2012 6:53 AM
 
Peter Gray

Joined: 3/2/2007
Posts: 14

Thanks for the response, Bill!

I went back and checked the errors immediately preceding this error event. It turns out that the error was being raised because of another module's "remnants". Removed them and everything works fine! 

Still testing it but am pretty sure that is the problem.

So far, DNN 6.1.2 has turned out to be absolutely amazing! All the errors we have faced are due to our upgrade related mistakes/omissions and one due to a caching/distributed DNS service that just did not like DNN - we removed that service and get BETTER performance.  

Again, really appreciate your prompt response and assistance.
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Bizarre Error in DNN 6.1.2 HTML ModuleBizarre Error in DNN 6.1.2 HTML Module


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