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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationQuick AD Auth run down - What works for meQuick AD Auth run down - What works for me
Previous
 
Next
New Post
11/30/2007 12:10 PM
 

That makes sense.  Originally, the version I was running was actuall 3.1.1.  I tried upgrading to 4.x.  I am returning to this project after a long time away from it, so I forgot what I actually did.  I guess I'll just have to restore the old version and try starting over.  Is it wise (or even possible) to properly upgrade from 3.1.x to 4.x?  Are there any best practices for that scenario?

 
New Post
12/6/2007 1:26 PM
 

I've tried a couple more things, but I still get that error saying "/Admin/Security/AuthenticationSettings.ascx does not exist." when I go to Admin -> Authentication.

I performed an upgrade straight from 3.1.1 to 4.7.  During the upgrade, I got a couple errors, but I'm not sure if they're related to this:

00:00:20.018 -   Executing Script: 04.03.03.SqlDataProvider Success
00:00:20.236 -   Executing Script: 04.03.04.SqlDataProvider Success
00:00:20.283 -   Executing Script: 04.03.05.SqlDataProvider Error! (see 04.03.05.log for more information)
00:00:20.752 -   Executing Script: 04.03.06.SqlDataProvider Success
00:00:21.143 -   Executing Script: 04.03.07.SqlDataProvider Error! (see 04.03.07.log for more information)
00:00:21.971 -   Executing Script: 04.04.00.SqlDataProvider Error! (see 04.04.00.log for more information)

00:00:24.190 -   Executing Script: 04.04.01.SqlDataProvider Success
00:00:24.346 -   Executing Script: 04.05.00.SqlDataProvider Success
00:00:27.659 -   Executing Script: 04.05.01.SqlDataProvider Success


I looked at the log files to check the errors, and they were related to creating the stored procedures associated with the Files table.  It doesn't really look like they're related to Authentication.

This is how I upgraded:

1. Unzipped the file DotNetNuke_04.07.00_Upgrade.zip into my DNN folder.  I unzipped it into my current 3.1 installation.

2. Updated web.config (setting up SQL connection string, preserving machine and encryption keys)

3. browsing to my DNN url and let the upgrade commence.

I also tried Unzipping the file DotNetNuke_04.07.00_Install.zip into my DNN folder instead of just the upgrade zip file, and I get the same result.  I thought the upgrade would somehow properly resolve the path to Authentication.ascx.  This is pretty critical to my portals, as I am looking to upgrade our existing 3.1 installation.

If it's any help, in my situation, I'm running a few child portals under a parent portal.  Would that have anything to do it?  Any help would be greatly appreciated.

 
New Post
12/6/2007 6:01 PM
 

I cant remember which version this happened (and it may have been for upgrades between 3 and 4) but I do remember reading somewhere that it was a good idea to delete all the *.vb files in an install before copying in the upgrade files. I think it was because .NET 2.0 will attempt to compile a .vb file into a .dll on the fly and there were .vb files that didn't need to be there. Another thing you could try is to use a program like WinMerge (which can compare files and directories) and do a comparison between your upgraded install and the raw DNN Upgrade/Install files.

I'm assuming that when you say you updated the web.config file you mean you took the release.config from the upgrade package, copied your connection string, machine keys, etc from the 3.1.1 and then renamed release.config to web.config correct?

 
New Post
12/10/2007 7:45 PM
 

I solved my problem.  Instead of upgrading from 3.1 to 4.7 directly, I first upgraded from 3.1 to 3.3.7, and THEN upgrading to 4.7 from there.  That seemed to take care of the error I kept getting.

 
New Post
12/17/2008 11:02 AM
 

Hi Charlie,

i am facing same problem,

Can you please tell me how you resolved this issue. Do we need to modify any code or need to set any settings.

can you please help,i am trying to resolve this issue past three days.

Thanks,

Sri

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationQuick AD Auth run down - What works for meQuick AD Auth run down - What works for me


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