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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade Issue - Generic DNN ErrorUpgrade Issue - Generic DNN Error
Previous
 
Next
New Post
6/25/2014 3:28 AM
 
please check Default Container selected in Appearing Section of Site Settings and Page Settings, maybe the setting needs to be updated.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/25/2014 1:24 PM
 
log back in and go to admin->event viewer and see what is logged there (if you can't log in you'll need to access the database and check what was the last issue logged in the EventLog table)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
7/1/2014 8:48 AM
 

Thanks again everyone for the assistance.  I decided to revert back to version 7.1.0.  Once I do this I can load the site.   I want to concentrate on resolving issues first here and then try the upgrade again.    Two things....  I noticed that when I log in  I occasionally get a screen (might be splash screen) that has the same error I would get when I upgraded. (DNN Error)   I checked my settings in Appearance and my splash page says "Not Specified"   Do I need one.  

Also I have a ton of these errors in the event viewer that says whats below.   Any ideas how to get rid of them.

Error:

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID: 76d37fd0-838b-4256-8948-d698ce9d08c4

InnerException: Specified argument was out of the range of valid values. Parameter name: index

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: System.Web.UI.ControlCollection.get_Item

StackTrace:

Message: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: index at System.Web.UI.ControlCollection.get_Item(Int32 index) at DotNetNuke.UI.Containers.Container.GetPortalModuleBase(UserControl control)

 
New Post
7/2/2014 7:27 AM
 
In regards to the splash page, no, you don't need one. That's optional and will only show if one is selected. Ignore it.

Mark
 
New Post
7/3/2014 3:14 PM
 

that's a method that is no longer used in the core since 5.0 - it's implementation looks like this:

 [Obsolete("Deprecated in 5.0. Shouldn't need to be used any more.  ContainerObjects (IContainerControl implementations) have a property ModuleControl.")]

        public static PortalModuleBase GetPortalModuleBase(UserControl control)

        {

            PortalModuleBase moduleControl = null;

            Panel panel;

            if (control is SkinObjectBase)

            {

                panel = (Panel) control.Parent.FindControl("ModuleContent");

            }

            else

            {

                panel = (Panel) control.FindControl("ModuleContent");

            }

            if (panel != null)

            {

                try

                {

                    moduleControl = (PortalModuleBase) panel.Controls[1];

                }

                catch

                {

     //check if it is nested within an UpdatePanel

                    try

                    {

                        moduleControl = (PortalModuleBase) panel.Controls[0].Controls[0].Controls[1];

                    }

                    catch (Exception exc)

                    {

                        Exceptions.LogException(exc);

                    }

                }

            }

            return moduleControl ?? (new PortalModuleBase {ModuleConfiguration = new ModuleInfo()});

        }

As it's not been used in years there is a chance that it has an error that only affects certain sites e.g. sites that have some skin/container/module that explicitly used that's API method - it's hard for me to say and harder still to test - that said it does look like any possible error would come from a container not having "ModuleContent" within it's name - I tested on a local install where I was working with a custom module ("cathaltestinputfilter") and mine does have a server control with that - I recommend you do a view source on the failing page(s) and see if that is the case with your install

<div id="dnn_ctr415_ModuleContent" class="DNNModuleContent ModcathaltestinputfilterC">


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade Issue - Generic DNN ErrorUpgrade Issue - Generic DNN Error


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.