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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Upgrade from 4.0 to 4.3.3 problemsUpgrade from 4.0 to 4.3.3 problems
Previous
 
Next
New Post
7/25/2006 5:58 PM
 

I wonder if someone had similar issues I am dealing with right now and will be able to give me a helpful hint.

I am currently using DNN4.0. I tried to upgrade to 4.3.3. I Downloaded DotNetNuke_4.3.3_Upgrade.zip and unzipped it into a temp folder. I backed up the content of my dotnetnuke folder and pasted the content of the newly downloaded folder over Website directory. Then I opened release.config and development.config and changed: connection string, machine key, validation key, and namespaces sections based on my old web.config file. I restarted IIS and deleted all temp internet files just to be safe. Then I navigated to http://localhost/dotnetnuke and was excited to see all the successful upgrade messages on my screen. I then clicked on the link to access my portal and was redirected to a custom login page. When I provide user name and psw I get 'Object reference not set to an instance of an object' message.

I tried to roll back to the prev version of DNN. It is working but each time I compile a module, site, or solution the system shows me assembly versions of a db and a DNN. Then it says that the system is being upgraded and shows me a link to navigate to my portal. My guess is some changes were made to the DNN db when I attempted to upgrade and now even though i downgraded to 4.0 still has new settings.

 

Any input will be appreciated.

 
New Post
7/26/2006 10:39 PM
 

There's a couple of things to be aware of....

1) Ensure the objectqualifier is set as the same from the old web.config to the new web.config file

2) If you are using SQL Server 2005, ensure named pipe is enabled

3) I also found somehow in the appSetting there is an additional key "connectionStringName" which is missing from the new web.config file.

Hope this helps....

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Upgrade from 4.0 to 4.3.3 problemsUpgrade from 4.0 to 4.3.3 problems


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