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 ...The Resource Cannot Be Found: /Login.aspx - Cannot Get Past Portal HomepageThe Resource Cannot Be Found: /Login.aspx - Cannot Get Past Portal Homepage
Previous
 
Next
New Post
12/10/2009 12:23 AM
 

Boyd

Have you tried the 'old' style of login url?  The /login.aspx url is a rewrite rule, as Sebastian has indicated.  However, on most DNN sites, you *should* be able to still get to the login page using domain.com/default.aspx?ctl=login  - this is the raw url as DNN will use when /login.aspx is rewritten.

Please try giving that a go, and see if you get the login page.  If you get a 404 again, are you able to check your windows event log?  Perhaps there is another error occuring that is showing up as a 404.

-Bruce

 
New Post
12/13/2009 10:46 PM
 

Yep. The old style works fine. But, of course, I can't get any further than each page if I click on other items in the page. IE: Type in the old style URL. When I get to the login page enter the credentials and click "Login", I can then login, but then I get the same error on Home.aspx. So then I type in the old style for the Home page and can get there, etc. Can't get any further when I attempt to do anything that leaves a page.

There's nothing going on in the event logs other than informational items in the Security log about my app domain. No errors and nothing unusual from any other point. I reset IIS and cleared the logs before checking. Got to the portal main page, clicked the "Login" link and got the error, then checked the logs: nothing.

I've suspected the Friendly URL provider since it was the newest item in my config file since my upgrade from v4.x. But with all the messing around with the config item for it, I still couldn't get anywhere and had similar results.

Further thoughts? This is obviously a major showstopper. I've offered a 300 rep bounty on the question on StackOverflow. Thanks Bruce.

 
New Post
12/17/2009 1:24 PM
 

 I am getting the same error. Mine's not installed on port 80 because we have another site already live on 80. This is to be a test version with a different host header name so I put it on 8088 temporarily. Well that seems to be the problem. The default login URL does not "know" the site is on port 8088 so that part of the URL is missing. When I manually type the port into the URL and refresh it finds the login page. So here's the problem. A separate host header name in IIS can't be used until we add that site name to the host configuration, which we can't do until we can log in successfully. :)  So I think I have to take down our live site, put this one on port 80 for a few minutes, do the configuration of the host name, and then put the live site back on port 80. Host header names should then work. Sorry I'm not explaining this in great detail but if it sounds like your issue and you have any questions let me know.

 
New Post
12/17/2009 4:44 PM
 

This seems similar to my problem only I am not seeing an error message. But that might be because I am not running in debug mode.  My login page is simply blank.  But other than that, my problems and setup are the same and I can't log in.  Going to the login.aspx page directly leaves me with only the image for the login, but no actual login form on the page.

It is as if the login module is not there or something.  I'm new to DNN dev work so the under-the-hood aspects of IIS and DNN are a bit of a mystery (Makes me very much miss Apache but anyway!)...... still I have tried the suggestions in this thread to no avail.

Note that I *do* have DNN running on my machine on a different virtual directory just fine.  it seems to only be with the source install and build that I'm having problems.

 

 
New Post
12/17/2009 11:25 PM
 

Jeff! You nailed it man!

I moved my app over to port 80 and everything runs!

So that raises another question then: My portal site in IIS didn't change when I upgraded from v4.x to v5.x. http://localhost:1234/Default.aspx.

Why did things stop working all the sudden? Again, it's obvious something changed in the new version. I'll be reading up more on IIS7 Port assignments to see if I can find the answer. But please feel free to give more advice if you have suggestions. Thanks again!

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...The Resource Cannot Be Found: /Login.aspx - Cannot Get Past Portal HomepageThe Resource Cannot Be Found: /Login.aspx - Cannot Get Past Portal Homepage


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