Hello,

I have read almost all threads about my problem but i have still found an anserv,

My config.

Windows 2003 R2 + ASP.Net + Framework 2.0 + sql 2005

I have tried download and installing the whole pakage the just the upgrade pakage bur stille the same problem.

I have put in the DataQualifyer + validationKey and decryptionKey

but sill i get the same error:

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

When i login ?

I can see all my sites correct, it is only when I try to login.

I have tried allmost everything please help.

Kind regards Gert

Hello,

I have solved my problem by restoring the Database and the Dotnet web site,

Then Exported all Sub sites with contens.

Deleted everything and yust done a new install, then imported everything again.

King Regards Gert

I had "pretty" good success in upgrading from 4.0.3 to 4.3.  The few issues I ran into were of my own doing or were easy to correct.

Preparation:
I first backed up my website and my database.  For me backing up my remote database requires that I open a support ticket with my hosting provider since I cannot find a way to backup my SQL Server 2005 using SSIS.

Update:
I took advantage of the Core Team's release of DotNetNuke_4.3.0_Upgrade and unzipped this over my local copy of DNN 4.0.3 and FTP'd the files to my remote site.

This should have done the trick but when I went to my website to begin the upgrade, I ran into an issue so had to modify the "RemoteOnly" setting changing this to "Off". 

• The first error shown was that it did not like <trust level="Medium" originUrl="http://localhost/.*" /> in the web.config, and since I cannot override machine.config I just commented this out - actually, this is where I made my first mistake and for some reason copied my "old" DNN web.config file over the new config file for 4.3. 
• The next error I received pointed to my \App_Code directory and it noted a conflict between AssemblyInfo.vb and Global.asax.vb files with C# code in the sub-directory.  I did not recall using the \App_Code directory, so I deleted it.  A related error message was thrown indicating I need the two vb files in \App_Code, so I simply added the directory and two files back.
• The next error I receive pointed back to the web.config file, which I immediately recognized was the "old" web.config file I used for DNN 4.0.3.  I simply copied the new web.config file to my remote site after modifying the connection string settings.
• The site then began to update and I received that warm message that "my" site had been updated and is ready to use.
• When I tried to login I received an invalid password error message for host, admin, and user accounts.  I recalled from a previous release that it was important to keep the machine keys the same, so I copied the <machineKey> element from my DNN 4.0.3 web.config file and the login issue was resolved.

After testing out my sites and adding some test pages with test modules, everything look great!  I know that you need to use the new web.config file and update the connection strings and keep the machine keys the same from the previous web.config.

I hope this helps!

John