Hello,

I have a "secondary" DNN site that I have neglected for some months.  I went to start working on it and ran into some problems.  First off, my site is running DNN 4.03.05.  (Yes I know this is quite old).  

Here is the problem.  When I try to edit text with the simple HTML editor that comes with DNN I get a long error message.  I am planning on asking my ISP to upgrade my site to 4.9.5.  Should we solve this HTML/Text editor problems first, or do the upgrade?

Below is the details of the error, with my domain removed.  Thanks for your suggestions!

Chip

Error Text


ModuleId: 388
ModuleDefId: 99
FriendlyName: Edit Text/HTML
ModuleControlSource: DesktopModules/HTML/EditHTML.ascx
AssemblyVersion: 04.03.05
PortalID: 0
PortalName: XXXXXXXXXXXX
UserID: 1
UserName: host
ActiveTabID: 65
ActiveTabName: Account
RawURL: /Account/tabid/65/ctl/Edit/mid/388/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.XXXXXXX.com/Account/tabi...fault.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: a1a9d336-3afd-454b-9082-416287a6f9be
InnerException: The runat attribute must have the value Server.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.TemplateParser.ProcessError
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The runat attribute must have the value Server. ---> System.Web.HttpParseException: The runat attribute must have the value Server. ---> System.Web.HttpParseException: The runat attribute must have the value Server. ---> System.Web.HttpException: The runat attribute must have the value Server. at System.Web.UI.TemplateParser.ProcessError(String message) at System.Web.UI.TemplateParser.ProcessAttributes(Match match, ParsedAttributeCollection& attribs, Boolean fDirective, String& duplicateAttribute) 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.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.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 ---

I would create a backup of your website and install it on your local computer. From there you can try a test upgrade and see if that fixes the problem without potentially causing any problems on your live website:

How to backup a live hosted DotNetNuke website and restore it to a localhost installation

Hi Lee,

Thanks for the suggestion. It would be a bit difficult for me to install locally due to the configurations/applications of my desktops.

My site's traffic has dropped quite a bit (possibly because other things may be broken too). Based on the error code above, do you think the upgrade could fix it?

Here are my thoughts. Since the site's traffic has dropped, have the ISP upgrade me to 4.9.5 after a complete backup. If the site does not work (which I can tell in an hour or less), have them restore the old version. It would probably take me 4-6 hours to get a PC configured correctly for a local test. If the ISP can undo the upgrade, I could do a "live" test in much less time. What do you think?

it's hard to know if an upgrade would fix the problem, however as long as your hosting provider creates a full backup there is no reason why you cannot test it on your live website.

I just don't like testing things out on a live website incase things go wrong.

For the future I think it will be worth setting up a virtual PC on your computer and from there you can configure a local DotNetNuke installation without it affecting any configurations or applications on your desktop, have a look here:
How to setup and use Microsoft Virtual PC 2007

From the error message, the problem appears to be with the file DesktopModules/HTML/EditHTML.ascx. 

The error message refers to a runat attribute.

So ... you might want to look into the file for runat and look for instances that are not of the forum:

       runat = "server"

If you find something like that, you could try replacing the file with a fresh copy from an install package of 4.3.5. 


Now, I have no idea how this might have happened and not been noticed before.  But if something has happened to that file, that would explain the problem.