After upgrading to DNN 6.0.1, my "Install Extension Wizard" seems to be broken.  Doesn't matter whether I try the wizard from either the Admin or Host menus.  Here's what's in my Event Log:

ModuleId: -1

ModuleDefId: -1

FriendlyName:

ModuleControlSource: DesktopModules/Admin/Extensions/Install.ascx

AssemblyVersion: 6.0.1

PortalID: 0

PortalName: Scarborough Chess Club

UserID: 3

UserName: karpiks

ActiveTabID: 46

ActiveTabName: Extensions

RawURL: /Admin/Extensions/tabid/46/ctl/Install/rtab/46/Default.aspx?popUp=true

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: http://www.scarboroughchessclub.ca/Admin/Extensions.aspx

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

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: b8820255-c34c-4ee3-8cae-14fedd0992ee

InnerException: Object reference not set to an instance of an object.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: DotNetNuke.Common.Utilities.Config.GetMaxUploadSize

StackTrace:

Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Common.Utilities.Config.GetMaxUploadSize() at DotNetNuke.Modules.Admin.Extensions.Install.OnLoad(EventArgs e) --- End of inner exception stack trace ---

Source:

Server Name: WSH-009

Can anyone suggest what might be wrong?  I can install extensions by dropping the modules in the /install folder and running a bulk extension installation, there's nothing wrong with my sites ability to ingest new extensions.  It just can't do it through the wizard.

Any and all advice gratefully received.

Thanks for your reply.  After much head scratching (and a bit of luck), I came up with the same answer as you.  I had forgotten that my ISP locks the httpRuntime setting.  See this short note:  https://support.isqsolutions.com/arti...  I dealt with this issue several years ago by commenting out the line:

<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" requestLengthDiskThreshold="8192" />

in my web.config but I had long since forgotten doing so.

Is there anything that I can change in my DNN setup get around this?  I've sent a question to my ISP about this limitation but I doubt they will bend on this (but I've got my fingers crossed).

Is this a problem that would have just come up with DNN6 or has it been a long time since I've tried to upload a new skin to my site and I just haven't stumbled upon this problem?

Right now it is a bit awkward with losing the ability to upload modules or skins.  I can just stick with doing bulk installs but it would be nice to deal with the problem directly.

the problem here is that DotNetNuke tries to read the value based on the existance of the attribute - and if it's missing there is a problem. We could make this code more defensive to ensure that it works in cases such as this -please log a bug at support.dotnetnuke.com (and make sure and reference this forum thread) so we can fix it in a future release.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US