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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Useless error messages - need more infoUseless error messages - need more info
Previous
 
Next
New Post
1/23/2014 11:04 AM
 
the default version of it is stored in the config folder - during install we copy this and drop it into the root folder and that's the one that controls the settings. Again, if you're doing an install (of any version from dnn 6.0 or above) and not seeing this happening it suggests a failure to copy the file which would be a permissions issue. If you're doing an install/upgrade from a version prior to dnn 6.0, I would not expect to see the file created until it got to dnn 6.0

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/23/2014 11:09 AM
 
Floyd Shadwick wrote:
Okay, I've done all of these, literally set perms on a folder by folder basis just before the upgrade and I'm still not getting the log files. I am getting a fail on 5.3.0 and I noticed the Wiki said: The log4net assembly (version 1.2.10) has been added to all editions of the DotNetNuke framework in 6.0.  If there is a connection between version 5 and framework (which I would think was version) 6. I really appreciate the help by the way.

 That would make sense with the problem being in the upgrade to 5.3.0. Any way to pin down the problem in framework 5?

 
New Post
1/23/2014 4:56 PM
 
I'm afraid not, as the config file is only copied at that stage. Typically those type of errors are permissions (e.g. the site is using add/delete permission, and not modify so DNN cannot modify the web.config - I recommend you check this), or that the web.config file has the readonly bit set on it. On occasion they're caused by 2 different location tags in the web.config (a known issue for older releases) -the workaround for which is to temporarily remove the location tag.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/27/2014 8:42 AM
 
I am resetting perms and the read only flag just before upgrade invocation. Where/what are the location entries you mentioned please?
 
New Post
1/27/2014 12:06 PM
 
within web.config http://msdn.microsoft.com/en-us/libra...(v=vs.85).aspx

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Useless error messages - need more infoUseless error messages - need more info


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