Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Er

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

Home All Forums

Home

Getting Started

Installing DNN ...

Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...

9/18/2007 9:49 PM

Christopher

Joined: 6/27/2006

Posts: 198

Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...

Hello,

When upgrading from Dotnetnuke version 4.5.3 to 4.6.0 the error message below is produced. I have triple-checked my config file and all is well there. I also checked the permissions set on the files and all is OK there as well (with NETWORK_SERVICE having the appropriate permissions). Any ideas?

Thank you for your time.

Regards,

Christopher Koeber

Error Message:

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: type

Source Error:

Server Error in '/' Application.

Value cannot be null.
Parameter name: type

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


            [ArgumentNullException: Value cannot be null.
            Parameter name: type]
            System.Activator.CreateInstance(Type type, Boolean nonPublic) +2768503
            DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +582
            DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectNamespace, String ObjectAssemblyName) +17
            DotNetNuke.Security.Membership.Data.DataProvider.CreateProvider() +38
            DotNetNuke.Security.Membership.Data.DataProvider..cctor() +13
            [TypeInitializationException: The type initializer for 'DotNetNuke.Security.Membership.Data.DataProvider' threw an exception.]
            DotNetNuke.Security.Membership.Data.DataProvider.Instance() +0
            DotNetNuke.Security.Membership.AspNetMembershipProvider..cctor() +5
            [TypeInitializationException: The type initializer for 'DotNetNuke.Security.Membership.AspNetMembershipProvider' threw an exception.]
            [TargetInvocationException: Exception has been thrown by the target of an invocation.]
            System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
            System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +103
            System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +261
            System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
            DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +582
            DotNetNuke.Security.Membership.MembershipProvider.CreateProvider() +38
            DotNetNuke.Security.Membership.MembershipProvider..cctor() +13
            [TypeInitializationException: The type initializer for 'DotNetNuke.Security.Membership.MembershipProvider' threw an exception.]
            DotNetNuke.Security.Membership.MembershipProvider.Instance() +0
            DotNetNuke.Entities.Users.UserController..cctor() +5
            [TypeInitializationException: The type initializer for 'DotNetNuke.Entities.Users.UserController' threw an exception.]
            DotNetNuke.Entities.Users.UserController.GetUserCountByPortal(Int32 portalId) +0
            DotNetNuke.Entities.Portals.PortalInfo.get_Users() +17
            DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +1302
            DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +83
            DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2848
            System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
            System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832

Regards,
Christopher Koeber

9/19/2007 11:36 AM

Mitchel Sellers

www.mitchelsellers.com
Joined: 1/24/2007

Posts: 7846

Re: Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...

Did you merge all configuration elements into the new 4.6.0 web.config file?

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

9/19/2007 12:01 PM

Chris Howell

nwds-ak.com
Joined: 5/22/2003

Posts: 7

Re: Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...

We have the same problem on our installations. I imagine many are.

Here is my workaround I just discovered. Make a backup. Always a good idea before playing Russian Roulette with DNN.

Delete the ENTIRE bin directory. Upgrade your files by copying over the upgrade files. Copy & rename release.config to web.config. Copy your connection strings, machine keys and any other customized settings you may have in your old web.config into the new one.

This should get you running. You may have modules that won't appear. Go to your backup and copy the DotNetNuke.Modules.* dll files into your bin directory.

This works for me.

9/24/2007 12:14 PM

Johan Asp

Joined: 8/20/2003

Posts: 24

Re: Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...

Hi,

Did you find any solution? I got the same error message

9/24/2007 7:04 PM

Dylan (www.innosoftware.net)

Joined: 8/13/2006

Posts: 19

Re: Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...

Hey ManInTights28 (Robin Hood fan?)

Thanks for the tip, as a Developer I have nothing against extra steps but I certainly get my panties in a knot when there are no special instructions provided with software upgrades. Open Source or not, I feel DNN may have room for growth in this area.

My DNN install was only 1 version down and had only a couple DataSprings modules plus a custom one I wrote in it. Doing the upgrade as per the instructions produced an "Object not set to the instance of an object" on a Response.Redirect to "/install/install.aspx?mode=upgrade" in the globals.asax.vb code-behind. If this basic configuration fails to upgrade then surely countless others are seeing the same thing.

DNN contributors, I hope you're taking this as constructive critical feedback. :)

Thanks again,

Dylan

P.S. I'm looking at my login screen now and it doesn't seem to like my password. God I hope it hasn't become broken from the upgrade process.

Dylan Lopez - Solution Developer, INNO Software Inc. E: http://www.innosoftware.net/contact.aspx P: 1-888-INNO-001 / 604-628-4467 W: http://www.innosoftware.net

Page 1 of 2

Home

Getting Started

Installing DNN ...

Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' 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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)