|
|
 | |  |
 | |  |
 | |  |
 | |  |
 | |  |
 |
|
|
 |
Joined: 12/13/2006
Posts: 0
|
|
|
The following error occurs when trying to examine the Settings of the Report Grid. This may be related to the recent Win2003 updates:
- Update for Windows Server 2003 (KB936357)
- Security Update for Windows Server 2003 (KB926122)
- Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)
 |
Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.Exception: The Runat attribute must have the value Server. ---> System.Web.HttpParseException: The Runat attribute must have the value Server. ---> System.Exception: 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.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.BaseTemplateParser.GetReferencedType(VirtualPath virtualPath, Boolean allowNoCompile) at System.Web.UI.BaseTemplateParser.GetUserControlType(VirtualPath virtualPath) at System.Web.UI.MainTagNameToTypeMapper.ProcessUserControlRegistration(UserControlRegisterEntry ucRegisterEntry) at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive) 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) 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 System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) in D:\Software\WebASP\DotNetNuke\Library\Components\Skins\Skin.vb:line 558 --- End of inner exception stack trace --- |
|
|
|
|
 |  |
|
|
 |
Joined: 11/2/2006
Posts: 0
|
|
|
Hi! Thanks for your question and sorry for the inconvenience.
The description of the error suggest that inside the file "Settings.ascx" a tag is missing the attribute runat="server". We already checked that at least one was forgotten . While waiting for a new patch to be released, a fast way to fix it is the following:
1. Open with a text editor the file Settings.ascx inside root/DesktopModules/ReportGrid
2. Search for every tag with an ID (search pattern "ID=")
3. Check for the tag to include the attribute runat="server"
4. Add it when it's missing
Thanks for your patience,
Kind Regards,
Dnaxp.Net Support
|
|
|
|
 |  |
|
|
 |
Joined: 12/13/2006
Posts: 0
|
|
|
Sorry, but that did not help. Even when I remove everything and leave the lines below in the Settings.ascx file, I still have the same error. I've checked the 3 ascx files on the last 3 rows and they seem to have the correct Runat setting. Is it something in the control that is missing?
<%@ Control Language="vb" CodeBehind="Settings.ascx.vb" Inherits="Dna2.Modules.ReportGrid.Settings" AutoEventWireup="false" Explicit="True" %> <%@ Register Src="../../controls/sectionheadcontrol.ascx" TagName="sectionheadcontrol" TagPrefix="dnn" %> <%@ Register Src="../../controls/texteditor.ascx" TagName="texteditor" TagPrefix="dnn" %> <%@ Register TagPrefix="dnn" TagName="Label" Src="~/controls/LabelControl.ascx" %>
|
|
|
|
 |  |
|
|
 |
Joined: 12/13/2006
Posts: 0
|
|
|
<%@ Control Language="vb" CodeBehind="Settings.ascx.vb" Inherits="Dna2.Modules.ReportGrid.Settings" AutoEventWireup="false" Explicit="True" %>
<%@ Register Src="../../controls/sectionheadcontrol.ascx" TagName="sectionheadcontrol" TagPrefix="dnn" %>
<%@ Register Src="../../controls/texteditor.ascx" TagName="texteditor" TagPrefix="dnn" %>
<%@ Register TagPrefix="dnn" TagName="Label" Src="~/controls/LabelControl.ascx" %>
|
|
|
|
 |  |
|
|
 |
Joined: 12/13/2006
Posts: 0
|
|
|
It seems the Rich Text Editor is not working...I deleted all by the first 4 lines of the Settings.ascx and have the same problem. If I copy the Settings.ascx from the Links module, the settings (for Links) displays correctly when I view the settings for the Report Grid. Same problem with the Report Chart, BTW.
|
|
|
|
 |  |
|
|
 |
Joined: 11/2/2006
Posts: 0
|
|
|
I'm going to build a test environment for testing it but it'll take a few days.
Kind Regards,
D.
|
|
|
|
 |  |
|
|
 |
Joined: 12/13/2006
Posts: 0
|
|
|
Thank you. Here is a link with a few hints:
http://weblogs.asp.net/christoc/archive/2007/07/11/did-last-night-s-windows-update-kill-your-dnn-sites.aspx#3124076
# re: Did last night's Windows Update kill your DNN sites? Thursday, July 12, 2007 6:59 PM by Stefan The recent Windows Update (WU) release included a number of .NET Framework patches in addition to security related fixes. As part of those patches, there were changes to how strings are parsed/converted when using encoding classes like System.Text.UTF8Encoding.
The behavior you are seeing is because prior to the recent WU release, the 2.0 Framework text encoding types would silently strip out or ignore unrecognizable characters. In the case of ASP.NET parsing a text file, like an .aspx or an .ascx, the text encoders in the unpatched 2.0 framework would silently ignore a character like a smart-quote. With the patch installed though the encoders now convert unrecognized characters into a common value: U+FFFD. This value is intened as a kind of error marker value.
Unfortunately that means formerly innocous syntax errors in ASP.NET pages now result in spurious U+FFFD characters showing up as a result of a page parse. When ASP.NET then attempts to process the resulting text it fails since U+FFFD is not recognized as a valid character in the declarative definition of control tags.
As other folks have noted above, the workaround is to find the .ascx/.aspx/.skin/.master/etc... files that have the bogus characters and change these files to have the correct character.
Leave a Comment
|
|
|
|
 |  |
|
|
 |
Joined: 11/2/2006
Posts: 0
|
|
|
Hi! I just made every WU available on my laptop, but I wasn't able to reproduce it.
A small question... Does every report does it? Does your reports use Parameters?
Thanks in advance,
D.
|
|
|
|
 |  |
|
|
 |
Joined: 12/13/2006
Posts: 0
|
|
|
Hi
I am running Win2003 server with SP2 and the reports worked fine until the 3 WU's mentioned ealier in the thread were installed.
Yes, all the reports are affected (with or without parameters), including Report Chart.
|
|
|
|
 |  |
|
|
 |
Joined: 10/30/2006
Posts: 0
|
|
|
Hi! Looks like this issue is not immediate as just looking for bad characters. Anyway I've made a couple of changes to improve XHTML 1.0 compliance.
Can you please try the attached Settings.ascx?
Thanks in advance,
D.
|
|
|  | Login to download attachment |
|
|
|
|  |
 | |  |
 | |  |
 | |  |
|
|
| |
|
|
|
 |

Full compatibility of ReportGrid & ReportChart with all releases of DNN from 4.0.2 to 5.4.4
The help desk support is always available to help you! Contact us!
Only $64.95 Offer expires on 12/31/2010
|
|
 |
|
|
|
|