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 ...Could not load the assembly Could not load the assembly 'DotNetNuke.Authentication.LiveID'. Make sure that it is compiled before
Previous
 
Next
New Post
10/24/2007 1:44 PM
 

I upgraded from 4.5.3 to 4.6.2 and now I get this error when trying to login.

Could not load the assembly 'DotNetNuke.Authentication.LiveID'. Make sure that it is compiled before accessing the page.

Any ideas?

 
New Post
10/24/2007 2:07 PM
 

You should use the INSTALL package, not the Upgrade package. Try copying the files from the Install package over, also be sure to setup your web.config file again (connection strings, objectqualifier, machinekeys)

Backup first


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
10/24/2007 2:55 PM
 

Chris Hammond wrote

You should use the INSTALL package, not the Upgrade package. Try copying the files from the Install package over, also be sure to setup your web.config file again (connection strings, objectqualifier, machinekeys)

Backup first

 

That did it! Thanks!

 
New Post
10/31/2007 11:48 PM
 

OK, here is my impression - the Install pack has web.config in it - that needs to be edited... So that is why the Upgrade is not adequate. If there were changes in the web.config that should have been handled in the installer...! So it seems that the Upgrade was not packaged properly...

 

I had the same problem, and solved it in the same way - using the Install package over the Upgrade - BUT editing the new web.config with connnection info and Machine Keys.

 
New Post
10/31/2007 11:58 PM
 

My understanding and perhaps a core member would be willing to correct me if I'm wrong but.....

Back in the day when there was just one package and one package only quite often people would accidently overwrite their web.config not realizing that they needed information like the connection string and machine keys (and other custom settings). The upgrade package prevents that from happening.

Below are my steps when upgrading a site:

  1. I use a program called WinMerge that will show the differences in a file and compare my web.config against the release.config. I
  2. In WinMerge I copy the connection string and machine keys over to the release.config along with any other custom changes I've made.
  3. Save the changed release.config and close WinMerge
  4. Rename the web.config do something different and rename release.config to web.confg
  5. Hit the site and let the upgrade run.

This way I've caught any changes that might not necesarily be able to be programmed into the web.config when the site is running.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Could not load the assembly Could not load the assembly 'DotNetNuke.Authentication.LiveID'. Make sure that it is compiled before


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