I have been trying unsuccessfully to upgrade my 2.1.2 to 3.3.4. I tried using the install version and then the source version both with the same problems. Basically, this is what I get:

1) I modified the release.config so it points to my database and renamed it to web.config

2) I didn't know what to do with the new keys for the "Machine...". I had read if they don't exist then they will be created for you, so I take it that if you are coming from 2.1.2 , you should in web.config

   A) Comment these keys out

   B) Leave these keys in there and a new value will replace the one in the web.config file

   C) Add the keys but make the value blank - value = ""

  <add key="MachineValidationKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902" />
  <add key="MachineDecryptionKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC" />
  <add key="MachineValidationMode" value="SHA1" />

3) When the install hits the modules section it gives an error that they are already installed. So, being the sly one I simply commented each one out as it popped up. After commenting these out, the install went on its merry way and when it said to click here to goto default site I got the error of object not found.

  <httpModules>
   <add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules.UrlRewrite" />
   <add name="Exception" type="DotNetNuke.HttpModules.ExceptionModule, DotNetNuke.HttpModules.Exception" />
   <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
   <add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnlineModule, DotNetNuke.HttpModules.UsersOnline" />
   <add name="ProfilePrototype" type="Microsoft.ScalableHosting.Profile.ProfileModule, MemberRole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b7c773fb104e7562" />
   <add name="AnonymousIdentificationPrototype" type="Microsoft.ScalableHosting.Security.AnonymousIdentificationModule, MemberRole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b7c773fb104e7562" />
   <add name="RoleManagerPrototype" type="Microsoft.ScalableHosting.Security.RoleManagerModule, MemberRole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b7c773fb104e7562" />
   <add name="DNNMembership" type="DotNetNuke.HttpModules.DNNMembershipModule, DotNetNuke.HttpModules.DNNMembership" />
   <add name="Personalization" type="DotNetNuke.HttpModules.PersonalizationModule, DotNetNuke.HttpModules.Personalization" />
  </httpModules>

4) When I try to restart naturally I get the object not found reference because I got the error above that they already existed!

5) I have been on all the forums searching for answers and have had no luck. I have about 10 portals so installing fresh and then somehow copying the data is not an option I would like to persue.

Any help would be appreciated.

Also, on most of the forums, why are all the messages showing up duplicates. I have noticed this on just about everyone. I read a message and then someone answers, then the same message appears with the same answer following it (not a request or copied text but the same question and answer.) That is kind of confusing. I have enjoyed DNN 2.1.2 and I want the new features in 3.3.4 but I CAN'T GET THERE!

Thanks

 

 

No, I was told "this is exactly the kind of feedback we want to hear", but nothing has been posted as to what it means to those of us wanting to goto 3.3.4 without loosing our existing portals or worse to port each one seperately given the portal owners are the one's responsible for content. I wish someone would give some direction given how many times the post has been hit.

I've got the same predicament, but a lot of custom modules that I also need to take care of - not fun.

Anyways, for the user thing and keys, I had a problem in a different upgrade (3.2.2 to 4.3.4) where all the users got locked out. I created a new user and used it's aspnet_[tableName] ApplicationId to fix things like this:

UPDATE aspnet_Membership
Set ApplicationId='NEW ID FROM NEWLY CREATED USER'
where ApplicationId='OLD ID FROM OLD REGULAR USERS'
GO
UPDATE aspnet_users
Set ApplicationId='NEW ID FROM NEWLY CREATED USER'
where ApplicationId='OLD ID FROM OLD REGULAR USERS'
GO
UPDATE aspnet_Roles
Set ApplicationId='NEW ID FROM NEWLY CREATED USER'
where ApplicationId='OLD ID FROM OLD REGULAR USERS'
GO
UPDATE aspnet_Membership
Set ApplicationId='NEW ID FROM NEWLY CREATED USER'
where ApplicationId='OLD ID FROM OLD ADMIN/HOST USERS'
GO
UPDATE aspnet_users
Set ApplicationId='NEW ID FROM NEWLY CREATED USER'
where ApplicationId='OLD ID FROM OLD ADMIN/HOST USERS'
GO
UPDATE aspnet_Roles
Set ApplicationId='NEW ID FROM NEWLY CREATED USER'
where ApplicationId='OLD ID FROM OLD ADMIN/HOST USERS'
GO

Hope that helps out some people.

Cheers,

Ryan