An inexplicable error occurred today: cocould not load the Assembly 'dotnetnuke. Authentication. liveid'. Make sure that it is compiled before. I found the following explanation on the Internet:
My understanding and perhaps a core member wocould be willing to correct me if I'm wrong .....
Back in the day when there was just one package and one package only quite often people woshould 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:
- I use a program called winmerge that will show the differences in a file and compare my web. config against the release. config. I
- In winmerge I copy the connection string and machine keys over to the release. config along with any other custom changes I 've made.
- Save the changed release. config and close winmerge
- Rename the Web. config do something different and rename release. config to Web. confg
- 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.
(Original in http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/179053/scope/posts/threadpage/1/Default.aspx)
But cannot solve the problem, below is another article (Original: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/-1/threadid/193000/scope/posts/Default.aspx)
There shoshould be a providers folder in your bin directory. if you look the install files you downloaded you shoshould find. ZIP files for both in the install/package directory. it sounds like they failed when they went to install but you can still install them manually if you want to use them under host-> host settings-> authentication services. are you using an objectqualifier or running the databas E as the user account instead of. DBO? I know there was a problem with one of the SQL procedures with 4.6.0 and 4.6.2 but I thought it had been fixed for 4.7.0 and 4.8.0.
But I use 4.7.0. Why is there a problem? Release in 4.8.0. After downloading the upgrade package, press.