470,834 Members | 1,620 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,834 developers. It's quick & easy.

problems in uploading asp.net website!!

Hi all,

I have developed an asp.net( 1.1) website using vb.net and Microsoft
Access and my hosting company does support asp.net1.1. Now I've FTP'd
the website , but whenever i try to access the website using
http://www.domainname.com/applicatio...ame/index.aspx ( where
index.aspx is first page of my application)
I get the following error
-----------------------------
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 <customErrorsconfiguration 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>

-------------------------------------

Any insight or comments will be highly appreciated. I have also
searched google and unfortunately I don't want to either use XCOPY or
web setup method. I am in a situation where I have to manually upload
the asp.net website, but I keep getting above error.
Any insight or suggestions will be appreciated. I appreciate your time
and help in advance.

Thanks,
Erland

Jul 11 '06 #1
2 1442
Hi Erland,

I would start the browser that's on the local server machine and run
the application from there, as recommended in the runtime error
description. The local execution of a web application gives you a detailed
error page which should help you along in finding the cause of the error.
If you haven't access to the server yourself, then ask the server's admin
to do it and that he/she should send the error page to you.

All other recommendations how to configure the web.config so that
the client browser shows detailed app errors has never been my approach
since it should normally not expose such internals, and it was always quicker
to directly run the app once on the server.

Regards
Frank
Hi all,

I have developed an asp.net( 1.1) website using vb.net and Microsoft
Access and my hosting company does support asp.net1.1. Now I've FTP'd
the website , but whenever i try to access the website using
http://www.domainname.com/applicatio...ame/index.aspx ( where
index.aspx is first page of my application)
I get the following error
-----------------------------
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.
Jul 11 '06 #2

Erland wrote:
Hi all,

I have developed an asp.net( 1.1) website using vb.net and Microsoft
Access and my hosting company does support asp.net1.1. Now I've FTP'd
the website , but whenever i try to access the website using
http://www.domainname.com/applicatio...ame/index.aspx ( where
index.aspx is first page of my application)
I get the following error
-----------------------------
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 <customErrorstag within
a "web.config" configuration file located in the root directory of the
current web application. This <customErrorstag 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 <customErrorsconfiguration 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>

-------------------------------------

Any insight or comments will be highly appreciated. I have also
searched google and unfortunately I don't want to either use XCOPY or
web setup method. I am in a situation where I have to manually upload
the asp.net website, but I keep getting above error.
Any insight or suggestions will be appreciated. I appreciate your time
and help in advance.

Thanks,
Erland
Aug 9 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

19 posts views Thread by Bill Davidson | last post: by
3 posts views Thread by Er bengaor | last post: by
1 post views Thread by Chris Kennedy | last post: by
reply views Thread by Luis Esteban Valencia | last post: by
3 posts views Thread by Abul Hasan Lakhani | last post: by
reply views Thread by santoshjsh | last post: by
1 post views Thread by bizt | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.