Products

Solutions

Resources

Partners

Community

Blog

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryRepository suddenly stopped workingRepository suddenly stopped working
Previous
 
Next
New Post
9/4/2010 4:04 PM
 
My repository has suddenly stopped working.  I'm not certain exactly when it happened.  I tried upgrading to dnn 5.5 to fix it but that didn't help.  Here is the error from the event viewer:

ModuleId: 380
ModuleDefId: 128
FriendlyName: Downloads
ModuleControlSource: DesktopModules/Repository/Repository.ascx
AssemblyVersion: 5.5.0
PortalID: 0
PortalName: The Dragon's Lair
UserID: 1
UserName: root
ActiveTabID: 59
ActiveTabName: Downloads
RawURL: /Downloads.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 GTB7.1 ( .NET CLR 3.5.30729; .NET4.0E)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 2bcad1d0-6e28-4c23-9870-d3ab5ef3ad4a
InnerException: The server tag is not well formed.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.TemplateParser.ProcessError
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The server tag is not well formed. ---> System.Web.HttpParseException: The server tag is not well formed. ---> System.Web.HttpException: The server tag is not well formed.at System.Web.UI.TemplateParser.ProcessError(String message)at System.Web.UI.TemplateParser.DetectSpecialServerTagError(String text, Int32 textPos)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.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.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc)at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl()--- End of inner exception stack trace ---
Source:
Server Name: SMARTLINK-01

Unfortunately the error doesn't, at least not that I can determine, say which file has the server tag that is "not well formed."  Anyone else ever have this problem?  I'd really hate to have to remove the module and redo all of the items.  Perhaps there is a way to remove the module, re-add it and then move the items from the old copy to the new one?

Bryan Johns
K4GDW

"There are 10 types of people. Those who understand binary and those who do not."
 
New Post
9/5/2010 11:51 PM
 
What version of the module are you using? Did you recently run Windows Updates? I don't recall the repository having this issue, but in the past some modules have failed when Windows Updates ran because of a funky QUOTE symbol in their code, deleting that symbol and adding a new quote generally fixes it.

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
9/6/2010 7:15 AM
 
Thanks for your help.

I'm using version 3.1.15.  As far as windows updates, I'm not sure about that.  I run those on my local machines all the time.  However, my web site is hosted. by a hosting company so my running windows updates wouldn't impact it.  However, the hosting company could run windows updates.  Even so, it doesn't make any since that a windows update would mess with the dnn as?x or dll files.  If that happened it would likely break a lot more than just the repository module and it would be a wide-spread problem.  Precisely which quote character are you talking about?  I could easily pull up the repository.ascx file and search for it.

Bryan Johns
K4GDW

"There are 10 types of people. Those who understand binary and those who do not."
 
New Post
9/6/2010 8:14 AM
 
are you using a custom repository template? or one of the packaged ones? If using a custom one, does the problem still occur if you switch to the default template?Any chance you  uploaded a file with a special character in the filename, like a single quote character? or angle bracket?  Try creating a temporary page and drop a new repository module on it to see if it also fails (which would indicate a problem with the module) or if it works (which would indicate a problem with the data)
 
New Post
9/6/2010 8:21 AM
 
No custom template, no new uploads since the last time it was working.  I did as you suggested and added a temp page with another repository instance.  It gives me the same error.

Bryan Johns
K4GDW

"There are 10 types of people. Those who understand binary and those who do not."
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryRepository suddenly stopped workingRepository suddenly stopped working


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