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 ...Upgrading from 4.5.3 to 4.6.0 Produces Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...
Previous
 
Next
New Post
9/28/2007 1:08 AM
 

I think I know the login one, check your machinekey string and make sure it matches the one from the last working web.config. Passwords are encrypted using the values from this string.

 
New Post
9/28/2007 1:28 AM
 

manintights28 wrote

We have the same problem on our installations.  I imagine many are. 

Here is my workaround I just discovered.  Make a backup.  Always a good idea before playing Russian Roulette with DNN.

Delete the ENTIRE bin directory.  Upgrade your files by copying over the upgrade files.   Copy & rename release.config to web.config.  Copy your connection strings, machine keys and any other customized settings you may have in your old web.config into the new one.

This should get you running.  You may have modules that won't appear.  Go to your backup and copy the DotNetNuke.Modules.* dll files into your bin directory.

This works for me.

 

 

The real question here is what caused it. I had this problem and your solution worked like a charm. Thing is, I had the problem on a clean install - not an upgrade. I also had the problem about 10 days after initial installation. The only major change is that I added a photo gallery, 2-3 days before the problem.

 

Thinking about it I may have compiled the source and selected to sync the site in the early evening, and the site died overnight sometime.


I'm not sure why a recompile of a site that has had nothing changed besied the default skins would cause this sort of problem. I am also remembering seeing a lot of files with a "pdb" extension or some such thing in the bin directory and wasn't sure what those were.

 
New Post
9/28/2007 11:53 AM
 

Like you said check the machinekey...if it is still giving you a problem, make sure your "ApplicationName" is set correctly.  That one got me.  It is defaulted to "DotNetNuke", but I changed it on my first install and didn't know that it uses that for encryption also.

<add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="SiteSqlServer" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="0" requiresUniqueEmail="false" passwordFormat="Encrypted" applicationName="DotNetNuke" description="Stores and retrieves membership data from the local Microsoft SQL Server database" />

If you change that on your first install then make sure you make it the same.  That isn't in any DNN instructions and that gave me SUCH a problem in my last upgrade.

 
New Post
10/16/2007 7:34 AM
 

manintights28 wrote

We have the same problem on our installations.  I imagine many are. 

Here is my workaround I just discovered.  Make a backup.  Always a good idea before playing Russian Roulette with DNN.

Delete the ENTIRE bin directory.  Upgrade your files by copying over the upgrade files.   Copy & rename release.config to web.config.  Copy your connection strings, machine keys and any other customized settings you may have in your old web.config into the new one.

This should get you running.  You may have modules that won't appear.  Go to your backup and copy the DotNetNuke.Modules.* dll files into your bin directory.

This works for me.

 

 

I herewith nominate you for this decade's "life saver award"

Now I can finally get some sleep...

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrading from 4.5.3 to 4.6.0 Produces Upgrading from 4.5.3 to 4.6.0 Produces 'Value cannot be null' Error...


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