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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke.Security.Membership.AspNetMembershipProvider Threw An Exception After Upgrade to 4.6.2DotNetNuke.Security.Membership.AspNetMembershipProvider Threw An Exception After Upgrade to 4.6.2
Previous
 
Next
New Post
3/25/2008 12:13 AM
 

I have a working DNN portal that I have upgraded several times over the past 3 years.  When I look at the Host Setting page, I see that my current version is 04.04.01.  Two weeks ago, I copied that portal to an external hosting site and successfully got it operational.  This is currently a test site as my real site is still running on another dedicated server.

Tonight I tried to upgrade to v 4.6.2 and came across a couple of errors after backing up my database and overlaying my source code with the contents of the install zip file.

The first error was a permissions issue on \\DotNetNuke.config.  After reading severa lforum posts, I copied \config\DotNetNuke.config to my root directory, which resulted in the second error:

[ArgumentNullException: Value cannot be null.
Parameter name: type]
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +2843963
   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) +268
   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) +2874
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Right now I don't know where I stand, as I could have screwed up one or more of the following:
   1 - my web.config file
   2 - FTPing the upgrade source files
   3 - my database
   4 - or anything else

If anyone has any insight, I would appreciate it.  Currently, this is a test site, so I have the liberty of restoring this from my production site and re-trying the upgrade.

Thanks!

 
New Post
3/25/2008 2:31 PM
 

Hi Brad,

DNN is having trouble loading the dataprovider for your membership provider.  Typically, I believe would be DotNetNuke.Membership.Dataprovider.dll.  Is this file missing from your bin directory?  Is this file and your DotNetNuke.Provider.AspNetProvider.dll both up to date?

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
3/25/2008 3:22 PM
 

It appears that since the upgrade did not complete properly several obsolete dll files were left in the /bin folder. See my reply to this thread:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/193052/scope/posts/Default.aspx

It looks like you also have the old AspNetMembershipProvider dll there as well which can be deleted. This was not on my list.  I would suggest that you compare the dll files in the /bin folder of your upgraded site with those in the /bin folder of the v 4.6.2 install to see which ones may be obsolete. Be careful not to delete any module related dll's which are necessary to your presently installed modules.  As this was a test upgrade, you may wish to restore to your backup and try again now that the permissions issue has been taken care of.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
4/1/2008 12:03 AM
 

THANK YOU for the solution to my problem! 

I just got back on this tonight.  Just to be safe, I restored the most recent version of my site to a separate IIS Server test directory and SQL 2005 database.  I verified that the old version came up correctly on the test website.  I unzipped the DNN 4.07.00 Upgrade zip file into my new test directory and verified that the upgraded version failed with the same error as before.

After reading your post in the link you supplied, I deleted the modules you suggested.  VOILA!  My site came up clean!!!!  I will do some more testing this week and if all looks ok, I will cutover the upgraded directory to my hosting site.'

Thanks again!  Brad

 
New Post
4/28/2008 8:13 AM
 

William Severance wrote

It appears that since the upgrade did not complete properly several obsolete dll files were left in the /bin folder. See my reply to this thread:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/193052/scope/posts/Default.aspx

It looks like you also have the old AspNetMembershipProvider dll there as well which can be deleted. This was not on my list.  I would suggest that you compare the dll files in the /bin folder of your upgraded site with those in the /bin folder of the v 4.6.2 install to see which ones may be obsolete. Be careful not to delete any module related dll's which are necessary to your presently installed modules.  As this was a test upgrade, you may wish to restore to your backup and try again now that the permissions issue has been taken care of.

From 4.4.1 To 4.6.0

I delete:

AuthenticationSettings.ascx and the associated code behind file
loggoff.aspx and the associated code behind file
signin.ascx and the associated code behind file
WindowsSignin.aspx and the associated code behind file

DotNetNuke.Authentication.ADSI.dll
    DotNetNuke.Authentication.ADSIProvider.dll
    DotNetNuke.DNNScheduler.SqlDataProvider.dll
    DotNetNuke.Ftb3HtmlEditorProvider.dll
    DotNetNuke.HttpModules.Authentication.dll
    DotNetNuke.HttpModules.Compression.dll
    DotNetNuke.HttpModules.DNNMembership.dll
    DotNetNuke.HttpModules.Exception.dll
    DotNetNuke.HttpModules.Personalization.dll
    DotNetNuke.HttpModules.UrlRewrite.dll
    DotNetNuke.HttpModules.UsersOnline.dll
    DotNetNuke.Provider.DBLoggingProvider.SqlDataProvider.dll
    DotNetNuke.Provider.Membership.SqlDataProvider.dll
    FreeTextBox.dll

TFB3htmlEditorProvider folder

See if this can help. Thank you all

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke.Security.Membership.AspNetMembershipProvider Threw An Exception After Upgrade to 4.6.2DotNetNuke.Security.Membership.AspNetMembershipProvider Threw An Exception After Upgrade to 4.6.2


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