Hans
Nuker
Posts:11
 |
| 10/08/2007 4:37 AM |
|
I have performed an update from 4.4.1 to 4.6.2. After copuing the files the installation goes of at approaching the site. After all files have been upgraded I receive the following error message:
Value cannot be null.
Parameter name: type 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:
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) +2796515
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
| I haven't got any idea what it means and how to handle it. Does anyone recognize this issue? How should I proceed? |
|
|
|
|
David Sjolin
Nuke Newbie
Posts:1
|
| 10/08/2007 7:16 AM |
|
I had the same error when upgrading from DNN 4.5.3 to 4.6.2. I managed to get the site running again by restoring the old web.config file and being very carefull when merging it with the new file. In fact, I think I only merged the SQL connection strings, machine key and object qualifier.
I am having trouble with the upgraded site not using previous code changes I added to signing.aspx.vb but everything else appears to be working well.
|
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/08/2007 8:20 AM |
|
The error message refers to the membership provider. I'd guess, as broctune mentioned, that you didn't get your web.config file updated correctly.
The best approach is to start with the NEW web.config and add in any changes that you have made. You must use the correct connection string (two places) and you MUST use the machine keysettings. Other custom settings that you have added must be there, too. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/08/2007 8:22 AM |
|
I am having trouble with the upgraded site not using previous code changes I added to signing.aspx.vb but everything else appears to be working well.
One of the hazards of changing the core code is that you are vulnerable to things like this. I'm in the process of upgrading, and have a couple of things to track down and fix.
|
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Hans
Nuker
Posts:11
|
| 10/10/2007 2:27 AM |
|
Things have gotten worse since my first message. I have tried to restore the backup that I had made. Of course this was only the files and not the database I have learned afterwards... This caused all kinds of interesting errors. Now I have asked the provider to restore the most recent complete backup that he had made. Is there any good tips and tricks on how to perform an update? I would like to do some testing, but I don't know how to get a testing environment running with the current live website. How can I make a local copy of files and database? Is this a standard function in DNN? |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/10/2007 8:38 AM |
|
You've discovered that part of the upgrade procedure makes changes to your database, and that these are difficult to "undo." ALWAYS make a backup of your database and your web directory before starting major work on your site. The web.config file is the key to a successful upgrade. Save your old web.config, then use it's contents to modify the new web.config supplied with the upgrade. As a minimum there are connection strings and machine key settings that MUST be transferred. You may have other custom settings. Also, if you have made changes to the core code, you'll have to track them down and do them again. Generally, you DON'T want to simply copy over modified files, because it's possible that other changes may have been made. This is certainly the case going from 4.4.x to 4.6.x. You might find these tutorials helpful: Even though the refer to earlier versions of DotNetNuke, the procedures remain the same. Mitchel Sellers blog contains some good entries on upgrading. I'd recommend that you look there, too. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Lee Sykes
DNN Creative Staff
Nuke Master VI
Posts:4945
|
|
Hans
Nuker
Posts:11
|
| 10/11/2007 9:47 AM |
|
Things are looking worse than ever. The provider has restored both the database and the files from before the changes and now I see the following error message:
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: BC30560: 'DataProvider' is ambiguous in the namespace 'DotNetNuke.Modules.HTML'.
Source Error:
Line 40:
Line 41: ' singleton reference to the instantiated object
Line 42: Private Shared objProvider As DataProvider = Nothing
Line 43:
Line 44: ' constructor
Source File: D:\www\i\n\d\indusys.eu\public_html\App_Code\HTML\DataProvider.vb Line: 42
Again I haven't got any idea what it means or how what could cause this situation. I would really appreciate any help in this case because I am already looking at allocation of time to design an entirely new site... |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/11/2007 11:30 AM |
|
You might want to have your provided empty the directory and reinstall your DotNetNuke files. You will want to preserve a copy of your web.config file,too, just in case ...
If, after the reinstall you still have problems, I would try copying the appropriate DotNetNuke "install" package over the reinstalled directory. Use the install package that matches the version that you have, not the upgraded one. This is where your web.config comes in -- after copying the install file, copy your old web.config over what is there.
And, if that doesn't work, give us the step by step details of what was done.
But, assuming that you've reinstalled the datbase and directory from before to the state that they were in, the site should work "as before." If it doesn't, I'd try the restore again. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Hans
Nuker
Posts:11
|
| 10/11/2007 1:50 PM |
|
OK! What turned out to be the issue is, that not ONLY the restored files were there. Probably some leftovers from the upgrade were there as well and those caused the trouble. What I have done now is cleaning out the entire site and restoring only the backup. Now, besides a couple of broken links to downloadable files, it seems to work again. Thank you for your help!!!! BR Hans Waldram |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/11/2007 3:28 PM |
|
Yep, those left over files can be a nightmare! |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|