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 ...Fresh 4.5.0 install upgrade to 4.5.1 canFresh 4.5.0 install upgrade to 4.5.1 can't log in
Previous
 
Next
New Post
4/17/2007 2:08 PM
 

billbayjr wrote

I am having same problem... upgrade from 4.5.0 to 4.5.1 and merging the web.config... now can't log into ANY portal.

I had a similar issue, had to register a new user than manually change the database to make that user a superuser.  Still can't log in under old usernames, can't change the passwords.

Jeff

 
New Post
4/17/2007 2:56 PM
 

Hi did you Copy Machine Key and Validation Key Values to new web.config from old one?

http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/55/DotNetNuke-Upgrade-Tips-Lessons-Learned.aspx

http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/22/Default.aspx

If you are on a shared hosting service like godaddy; you can optionally recylce application pool or ASP.NET version by going to Control Panel

 


Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey
 
New Post
4/17/2007 4:51 PM
 

Well, I thought that I had an easy solution. Since this is a clean install with no content and the use is for testing, I deleted the entry for 4.5.1 in the Version column of the db and re-ran the upgrade. Same results - 404 page not found for login & register. So I deleted the entire site and database, grabbed the 4.5.1 install file and started over from scratch. That has not provided a solution. I now have a 403 Forbidden error on the default.aspx (home) page. The page shows:
Most likely causes:

  • This website requires you to log in.

So I deleted the database again and ran through the install again. Same result.

So I cycled ASP.Net services off and on. Same result.

I guess I will delete the entire site again and start over with 4.5.0.

BTW - now I've lost most of a work day on this and the entire purpose behind this clean install of 4.5.x was to compare is to another CMS. My main client who has 4 DNN sites and 2 new sites in the works is questioning why we are using DNN and if there is a less buggy (his words as an end user) and easier to administer CMS we can switch to. We've been using DNN since V2 and he is tired of buggy modules and upgrade issues.

 
New Post
4/17/2007 6:58 PM
 

I've just completed a new clean install of V 4.5.0 on a shared server using IIS 6.0 and SQL 2005. I wiped the files and deleted the db and started with a new upload of DNN 4.5.0 Install. The install ran without errors and the home page loaded. I am now back to the starting point of the problems.The Register, Login, Terms of Use & Privacy links all return a 404 Page Not Found error. Here is the path to Login:
http://www.networkedneighbors.com/Home/tabid/37/ctl/Login/Default.aspx?returnurl=%2fDefault.aspx

I cycled ASP.Net off and on and cleared the browser cache. Same 404 error on links.

Any other suggestions? Some have tried turning friendly URL's off, but that doesn't solve the issue either.

 
New Post
4/18/2007 10:22 AM
 

It appears to be an issue with friendly URL's as the URL truly doesn't exist and it doesn't appear that Friendly URL's is capturing the request and processing it.

This is a bit of a long shot, but have you validated that the ASP.NET worker process has FULL access to all files in the directory?  For FriendlyURLs to work correctly it must have access to the SiteURLs.confg (I think that is the name) and plus in general DNN needs access to the file system.

If ASP.NET didn't have full permissions, update the permissions then restart the application and try again. 

Again, this isn't necessarily a promised solution but it could work!


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Fresh 4.5.0 install upgrade to 4.5.1 canFresh 4.5.0 install upgrade to 4.5.1 can't log in


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