Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / July 2007

Tip: Looking for answers? Try searching our database.

ASPX page fails to serve up using

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sherman KB - 02 Jul 2007 15:34 GMT
I have an application developed using IIS 5, and the 2.14 version of the .net
framework and SQL 2005. When deployed to two different servers, the pages all
display properly when using the address
http://localhost/mywebapp/default.aspx. If I replace localhost with a DNS
name, the pages will not display... I get a "Internet Explorer Cannot display
this page" message. In reviewing the IIS log files, all of the response codes
are 302 (redirects) for the requested page. Again, the pages serve up as
intended when using localhost in the url. In doing some testing, a plain
vanilla aspx page with no code behind the page dishes up without error. Does
anyone have any ideas?
Signature

Ken S

Peter Bromberg [C# MVP] - 02 Jul 2007 16:46 GMT
"When deployed to two different servers, the pages all
display properly when using the address
http://localhost/mywebapp/default.aspx" -- that's because localhost is your
own machine, you arent' even requesting the page from the other 2 servers.

It needs to be "http://machineNameOrIPAddress/mywebapp/default.aspx"
-- Peter
Site:  http://www.eggheadcafe.com
UnBlog:  http://petesbloggerama.blogspot.com
BlogMetaFinder(BETA):    http://www.blogmetafinder.com

> I have an application developed using IIS 5, and the 2.14 version of the .net
> framework and SQL 2005. When deployed to two different servers, the pages all
[quoted text clipped - 6 lines]
> vanilla aspx page with no code behind the page dishes up without error. Does
> anyone have any ideas?
DOsborn - 02 Jul 2007 20:21 GMT
On Jul 2, 9:34 am, Sherman KB <Sherma...@discussions.microsoft.com>
wrote:
> I have an application developed using IIS 5, and the 2.14 version of the .net
> framework and SQL 2005. When deployed to two different servers, the pages all
[quoted text clipped - 7 lines]
> --
> Ken S

Its possible .Net 2.0 isn't registered properly with IIS.  You could
try reregistering it using aspnet_regiis.exe -i .  This application
can be found in you windows folder under Mircosoft.NET\framework
\v2.0.X.

If you're running .NET 1.1 and 2.0 on the same IIS you need to have
them in seperate application pools as well.

This is all assuming that you were not trying to access localhost from
on the server and were instead trying to do it from a remote machine
like Peter implied.

David
http://blog.ctrlalt313373.com
Sherman KB - 02 Jul 2007 20:50 GMT
There was a problem with some code that would automatically have the site use
https if the site is secured, and the request was not a loop back request
(local host)
Signature

Ken S

> I have an application developed using IIS 5, and the 2.14 version of the .net
> framework and SQL 2005. When deployed to two different servers, the pages all
[quoted text clipped - 6 lines]
> vanilla aspx page with no code behind the page dishes up without error. Does
> anyone have any ideas?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.