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
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsDocumentsDocumentsError after upgrading Documents V5 to V6.01Error after upgrading Documents V5 to V6.01
Previous
 
Next
New Post
3/21/2014 8:48 AM
 
Frank Davis


Joined: 5/2/2007
Posts: 49
Hi - I have a DNN 5.4.4 instance that was running the Documents module 4.01 which I updated to 5.0 and it ran as normal. However when I upgraded from 5.0 to 6.0.1, the following error is created when loading the module:


ModuleId: 4055
ModuleDefId: 100
FriendlyName: JMS Company Documents
ModuleControlSource: DesktopModules/Documents/Document.ascx
AssemblyVersion: 5.4.4
PortalID: 61
PortalName: DX-Portal for JMS
UserID: 1
UserName: host
ActiveTabID: 2856
ActiveTabName: Company Documents
RawURL: /jms/CompanyDocuments/tabid/2856/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: 
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MDDC; .NET4.0C; .NET4.0E; McAfee; InfoPath.3)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: b69d0a62-93af-4432-8eb1-f5b4f9aae413
InnerException: C:\Inetpub\vhosts\dx-portals.com\httpdocs\DesktopModules\Documents\Document.ascx(14): error BC30451: Name 'IsEditable' is not declared.
FileName: 
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Compilation.BuildManager.CompileWebFile
StackTrace: 
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: C:\Inetpub\vhosts\dx-portals.com\httpdocs\DesktopModules\Documents\Document.ascx(14): error BC30451: Name 'IsEditable' is not declared. ---> System.Web.HttpCompileException: C:\Inetpub\vhosts\dx-portals.com\httpdocs\DesktopModules\Documents\Document.ascx(14): error BC30451: Name 'IsEditable' is not declared. 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: VPS067

Any help would be greatly appreciated!

Frank
 
New Post
3/22/2014 7:16 PM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676
I suspect your issue is simply that your DNN version is too old i.e. IsEditable was introduced later than 5.4.4. Typically a module would declare it's minimum version so that users cannot install it on older unsupported DNN versions, but I had a look in it's manifest file and it seems that documents does not. I see you logged an issue at their codeplex site - but realistically you should look to upgrade - 5.4.4 is very old and suffers from known security issues.
Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/27/2014 9:29 AM
 
Frank Davis


Joined: 5/2/2007
Posts: 49

Thanks for the explanation Cathal but upgrading is not an option presently. I plan to move to 7.X at some point but now I have a broken module that many users have entered a lot of documents in that cannot be accessed now.

Is there a way to roll-back to 5.0 by making changes to the config file, database or some other method that will not destroy the file links already entered?

Thanks so much for your help!

Frank
 
New Post
3/27/2014 4:09 PM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676

no experience of doing so I'm afraid - generally speaking rolling back modules is very tricky as the module may have updated data as well as schema during installation (which is why you should always back up your website and database before doing upgrades). If I was to attempt something such as that I would first back everything up, and then copy the old (5.0 documents) code over - next I would look at the database changes applied in the 6.0.1 release and attempt to reverse them e.g. https://dnndocuments.codeplex.com/Sou... is the database changes that are applied

Based on that the main reason for 6.0.1 was to add the forcedownload column, so I would drop that column and then modify the other stored procedures to stop referencing that column, and hope that resolved things

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
 Page 1 of 1
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsDocumentsDocumentsError after upgrading Documents V5 to V6.01Error after upgrading Documents V5 to V6.01


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