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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How do I move my complete setupHow do I move my complete setup
Previous
 
Next
New Post
6/22/2006 4:52 PM
 

 

First, thanks for replying with detail. :)  I first migrated/moved my 4.0.3 installation from one server to another.  That was why I first jumped into this thread earlier (Posted: 15 Jun 06 4:17 PM).  Once I got that DNN 4.0.3 move in place and everything working OK, then I attempted to upgrade from 4.0.3 to 4.3.0 (and today I tried 4.3.1 upgrade, but still getting the same error: cannot Login after upgrade).  Basically, once I either follow DNN directions to UPGRADE or INSTALL then UPGRADE, I cannot Login (as Admin/Host, my only two users...) and I get the message:

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

The UPGRADE directions suggest you simply copy the upgrade files over the existing installation.  That seems a little likely to fail to me, but what do I know?  (very little, but learning).  I have seen posts where people make reference to doing a clean INSTALL, then importing the tables/data from an existing installation.  I'd like to try that, but I don't understand how to SQL export tables/data so I can import them (which also I'm clueless about).  So if you knew anything about that process, I was hoping you might help.  Any suggestions are welcome, and I thank you too for what you have provided already.

 


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 10:36 PM
 

I know it is probably a redundant question, but did you perform the recursive security step on your DotNetNuke directory?  I suppose you did since you SEE the login screen - right?  If it was a security issue I would think that you would not even see the main page (Default.aspx)  - it sounds like you get that far - am I right?.   I am throwing darts at this point - here is my experience at work...ObjectNot Set means that it (DNN) tried to get something (probably from a table in the backend) and nothing (a null) was returned for that user/password and the null value wasn't caught in the DNN VB code.  Or a redirection or ASCX reference was returned that doesn't exist.  You are at wits end because your superuser is messed up somehow...My guess would be that something changed in the encryption of the password such that DNN is getting a bad value back (between versions)...at this point I would check with the developers of the login module and see if they know anything you can do to debug it or somehow hammer in some userid/pw that will work. 

OK I am still rambling but after reading your post, did you change database server as well?  Or just the DNN (IIS) host?  IFF you changed the database server I assume you updated the web.config?  Of course this goes back to the fact that you are having LOGIN issues and not issues seeing the main page (Default.aspx).

I know this probably won't help, but....

-Daryl

 
New Post
6/23/2006 7:54 AM
 

Thanks. Your reply was helpful, really - not rambling at all.  Maybe I don't understand everything you mention - exactly - but I think you've got some good ideas in there.  Maybe the more I do learn about DNN, the more it will make sense.  I appreciate your understand of Object reference not set to an instance of an object because I can use the info your provided in other DNN, ASP.NET and Google searches.  Maybe it will lead to something more.  Maybe it will lead to a post where someone describes my exact error and a solution for it.  For now, I'm going to stay at DNN 4.0.3 - the version I migrated/moved between servers.  It's running beautifully, after taking the migrating/move steps above in earlier posts in this thread.

And since this was orginally a post thread about Moving/Migrating DotNetNuke 4.0.3, I think I should stop yakking about the trouble I'm having with Login after an Upgrade to 4.3.0.  Thanks - Daryl - for your pointers.  I'll let you know if... I mean 'when' I come upon a solution. ;)

 


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
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How do I move my complete setupHow do I move my complete setup


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