Jump to content

Page not found after copy the ASPX files to IIS

- - - - -

  • Please log in to reply
7 replies to this topic

#1
manfree

manfree

    Newbie

  • Members
  • Pip
  • 5 posts
Hi all,

I'm a .net newbie, I am using VS2008 to develop the aspx web form
All the script are working fine in localhost (i.e. localhost:3267)

However, when I copy all the files to IIS on other machine
and open it...
it returns >>> The page cannot be found

Any body know what is going on here ?
Thanks

#2
manfree

manfree

    Newbie

  • Members
  • Pip
  • 5 posts
I found a thread from other site, it recommends the following deployment for the .NET website
I tried these 2 methods ... but still getting the same result ...
Page not found T_T

1. Just copy all project files to the web server and configure it to use ASP.NET version 2.0. In this scenario it will compile your application on the fly and this will cost you some performance, the good part is that you could very easily update your site, just copy the new files.

2. From VS 2005 click with right mouse button on the project and choose Publish Web Site, after that you have a few options. In this scenario the performance is much better, because you precompiled your website before publishing, but you should precompiled and deploy again the whole site if you have some changes.

#3
manfree

manfree

    Newbie

  • Members
  • Pip
  • 5 posts
I have changed .NET version from 2.0 to 1.1

Can read the default.aspx, but it comes up with other ERROR

I tried to follow the instruction from the system, and modify the customerErros mode = "OFF" in web.config file

but it returns the same error message

Don't know which part I got wrong ??




Server Error in '/WebApp1' Application.
Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

#4
WingedPanther

WingedPanther

    A spammer's worst nightmare

  • Moderators
  • 16,822 posts
  • Location:Upstate, South Carolina
  • Programming Language:C, C++, PL/SQL, Delphi/Object Pascal, Pascal, Transact-SQL, Others
  • Learning:Java, C#, PHP, JavaScript, Lisp, Fortran, Haskell, Others
IIS configuration of virtual folders, permissions, ASP execution, etc can all be factors.
Programming is a branch of mathematics.
My CodeCall Blog | My Personal Blog

#5
manfree

manfree

    Newbie

  • Members
  • Pip
  • 5 posts
Is there any detail description ?
I have created the virtual directory, granted the user permission

What about the ASP execution ??
Or do you have any URL link for me for the reference ?
I have searched via google ~~ but still can't get the result ... =_= ...

Thanks

#6
manfree

manfree

    Newbie

  • Members
  • Pip
  • 5 posts
After I try and play with the IIS, the aspx page is finally can be displayed :)

Here are what I've done. Please advice / comment if there are any missing or incorrect, thanks

Cause:

a) By default, this item is not existed, after installed the IIS and .Net Framework 2.0, that's why I need to add it

b) I am thinking .... VS2008 might defaultly included some .Net Framework 2.0 library during the startup page has been created (i.e. Default.aspx) . That's why the IIS doesn't recognize the .NET 2.0 stuffs ....

Solution

1. 'Add' and 'Allow' the ASP.NET v2.0.50727 in "Web Service Extension"
- File: C:\%windows%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

2. Grant write permission for the "NETWORK SERVICE" to folder >>> C:\%WINDOWS%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files


wish it might help other ppl to solve the same problem ~~ :)

#7
gokuajmes

gokuajmes

    Programming God

  • Members
  • PipPipPipPipPipPipPip
  • 518 posts
.NEt 2 is an essential component if you are using the Visual Studio 2008,as Asp.NET engine was built out of the Framework.As for your problem a simple deployment solves the solution,try Asp.net official website and Msdn documentation on the various ways to deploy a WebApplication

#8
ayachub

ayachub

    Newbie

  • Members
  • PipPip
  • 12 posts
check in tab document.. add for page default




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users