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 ...Problem upgrading fraom 4.0.3 -> 4.3.0Problem upgrading fraom 4.0.3 -> 4.3.0
Previous
 
Next
New Post
6/19/2006 5:57 AM
 

 Hi,

Thanks for all the helpful responses. Unfortunately none of them have helped in my situation. I've tried it multiple times now, I extract the install files over the top of my site, I rename release.config to web.config then I merge in any specific changes from my old web.config (as detailed in my earl;iers post) and I get a Critical Error when I try and login. What could be causing a critical error? And is there any way to find out what the error is when I can't login to access the logs.

Any help appreciated as this is currently a show-stopper.

Thanks,

Dale


www.creative-dreaming.com
 
New Post
6/20/2006 5:37 PM
 

OK - its nearly working after a lot of pain.

Firstly the critical error was due to the invalid username/password --> but surely that should not give a critical error? It only seems to happen if the user exists in a different application and I guess in theory there should only ever be one application so maybe this is unlikely to happen.

Anyway the problem was because in DNN (4.0.2) the application name for AspNetSqlMembershipProvider was hardcoded, so despite having an application name of ‘/’ in the web.config of 4.0.2 actually ‘DotNetNuke’ was used. So with the latest upgrade it was read from web.config like it should be and therefore when I merged my web.config in I copied my application name across being ‘/’ which didn’t match ‘DotNetNuke’. Once I changed that (or rather left that!) I was able to login!

 

Hope that saves someone else from having to spend as many hours as I did to find this.


www.creative-dreaming.com
 
New Post
6/22/2006 7:59 AM
 

A critical error has occurred.
Object reference not set to an instance of an object

I'm stuck on this error, too; it's coming up right after Login.  Error shows at the top of ContentPane, on the portal homepage.  The page displays OK, but Login fails.  I only have two users (Host/Admin) in this beta portal, and only one portal on this system.  I don't think duplicate usernames between applications is happening for me.  I did copy MachineValidationKey and MachineDecryptionKey from 4.0.3 web.config to 4.3.0 web.config, too.


I don't exactly understand your solution above.  Did you edit the web.config file:

Search:
applicationName="/"

Replace:
applicationName="DotNetNuke"

Is that the change you made?

 


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
New Post
6/22/2006 8:20 AM
 

That is one of the changes I made... my original web.config had applicationName="/" in the DNNSQLMembershipProvider tag. I merged this change into the new web.config along which my machine keys and a couple of other specific settings. That caused me to get the error so then I changed applicationName="DotNetNuke" (which is now in the AspNetSqlMembershipProvider tag) and then the error went away. 

Tikkune wrote
Search:
applicationName="/"

Replace:
applicationName="DotNetNuke"

Is that the change you made?


www.creative-dreaming.com
 
New Post
6/22/2006 8:53 AM
 

Is the web.config applicationName= the same Application Name referenced in IIS?  I mean, should they be the same?  If so, I may have made an App Name (and alias name) change sometime since my first 4.0.3 install, and maybe this is leading to my trouble with the upgrade to 4.3.0 ...

 


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem upgrading fraom 4.0.3 -> 4.3.0Problem upgrading fraom 4.0.3 -> 4.3.0


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