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 ...Installing 4.3 Upgrade Installing 4.3 Upgrade
Previous
 
Next
New Post
6/19/2006 5:48 AM
 

had the same problem i fix it by adding the MachineValidationKey en the MachineDecryptionKey

from the original web.config to the new web.config or release.config

hope this helps,Sander

 
New Post
6/19/2006 8:14 AM
 

Thanks for the suggestion to copy the Validation and Decryption Keys from the original web.config file into the new release.config (later to be renamed to web.config before the upgrade).  But unfortunately, this did not fix the problem for me as it did for you, Sander.  Is there a possibility you did something else, too?

I notice one other strange thing happen; maybe this could help someone who knows DNN better than I do?  When I click on the <Send Password> button, the screen I see has only a Username on it.  It does not have the normal warning message: ! Please Enter Your Username - and the Password field and <Login> button are missing, too. I only see the Username field, with a small graphic-looking symbol under the Username filed - that's all.

 


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/19/2006 10:31 AM
 

the only thing else i did was copy the lines of code where my database is registerd

<add name="SiteSqlServer" connectionString="Server=server;Database=database;uid=user;pwd=password;" providerName="System.Data.SqlClient"/>

from my old webconfig

but there is something else you could try.

try adding the objectqualifier from this post http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/45348/scope/posts/Default.aspx

  <data defaultProvider="SqlDataProvider">
      <providers>
        <clear />
        <add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="" databaseOwner="dbo" />
      </providers>
    </data>

hope this helps

Sander

 
New Post
6/19/2006 3:00 PM
 

Sander: thank you for checking what else you may have changed in your web.config file, and sharing that with me.  Unfortunately, I am still having the same error attempting to Login.  I made the changes you had suggested with my already configured web.config file, then I tried rolling back my DNN installation to 4.0.3, made the changes to web.config that worked for you BEFORE starting the upgrade.  Once again, the upgrade appears to complete OK, but I when attempt to login I get the error:

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

... and I'm sitting at the homepage, with all panes displaying, but login failed.  For now, I'm going to rollback to 4.0.3 and wait to upgrade to 4.3.0 another time.  Thanks again.


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/19/2006 4:36 PM
 

[Note Added Later: Please see my next post below before using these instructions. - Tikkune]

Sander: thanks for pointing me to the Shaun Walker post:

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/45348/scope/posts/Default.aspx

because after having the UPGRADE package fail again, and after reading Shaun's post, I decided to do a brand new INSTALL of 4.3.0, rather than upgrade (Shaun mentions this option).  Here's exactly what worked for me:

1) copied the full file/folder contents of my existing DNN 4.0.3 application to a temp/backup folder;
2) deleted everything in my DNN 4.0.3 application folder;
3) extracted the contents of the 4.3.0 INSTALL package into my (now empty) application folder;
4) * reset the ACL permissions on the DNN application folder/subfolders (and all child entries...);
5) browsed to the location of my DNN application (localhost/dnn) to start the 4.3.0 installation;
6) fresh installation of 4.3.0 completed successfully; closed the browser immediately (did not access portal);
7) opened the 4.0.3 web.config file (temp folder) and copied to paste buffer the Validation and Decryption KEYS;
8) opened the 4.3.0 web.config file and pasted my Validation and Decryption KEYS over the default KEYS;
9) copied the contents of my existing \App_Data\ folder (the DNN database) over the 4.3.0 default database;
10) * reset the ACL permissions on the DNN application folder/subfolders (and all child entries...)
11) browsed to my DNN application,and UPGRADE started automatically;
12) upgrade completed successfully.

I could now login without errors, and I had upgraded from 4.0.3 to 4.3.0 successfully. :)

* (highlight your /dotnetnuke application folder, and right-click) > Sharing and Security... > Security [tab] >Advanced [button] > [x] Replace permission entries on all child objects with entries shown here that apply to child objects > Apply [button] > OK [button]


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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing 4.3 Upgrade Installing 4.3 Upgrade


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