I have just installled Web Developer 2005 and canpreview the Personal Web Site Starter Kit fine locally. However, when I try to preview it on my remote web space I get the following:
Server Error in '/' 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".
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.
There is an error on the page but you cannot debug remotely using asp.net 2.0. I suggest porting the site locally, get rid of the kinks then put it back on the remote server. Without any erros you should be able to preview the site.
I got DNN 3.1 to install on my godaddy site. Now I get this error when I try to access the admin menu items. Host menu works fine and regular configuring of pages and modules works. Ideas? Thanks.
Server Error in '/DotNetNuke/admin' 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".
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.
2. Rename the Web.Config file in the root of the application folder to web.config (case sensitive). My application is in the public/abc folder so I would put the web.config file there. It does not need to go into the /public folder or the / folder.
If it is 5.1(i.e you r using XP) make shore u r application folder must be shared.
if UR using IIS 6.0 (u r OS ie 2003 server)
do following..
start--->run--->inetmgr--->ur system name--->expand it--->go to u r vertual directory--->right click ----->Permissions--->make shore to provide all Check boxes must be checked.
tan.
go to properties of u r vertual directory ASP.NETtab and see UR vertion of VS.NET
Don't forget to click "Mark as Answer" on the post that helped you.
This credits that member, earns you a point and mark your thread as Resolved for the sake of Future Readers.
glamorgand19
Member
20 Points
4 Posts
Server Error in "/" Application
May 14, 2005 02:37 PM|LINK
I have just installled Web Developer 2005 and canpreview the Personal Web Site Starter Kit fine locally. However, when I try to preview it on my remote web space I get the following:
Server Error in '/' 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".
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.
I have been told the answer is in the details and notes in the error messgaes - but can't make head nor tail of waht these mean!
Any help gratefully recived!!
ferdz
Member
40 Points
8 Posts
Re: Server Error in "/" Application
May 17, 2005 02:10 PM|LINK
cando
Member
25 Points
5 Posts
Re: Server Error in "/" Application
May 17, 2005 08:50 PM|LINK
cd2582
Member
35 Points
7 Posts
Re: Server Error in "/" Application
Jun 10, 2005 04:06 PM|LINK
cando
Member
25 Points
5 Posts
Re: Server Error in "/" Application
Jun 10, 2005 04:18 PM|LINK
There is an error on the page but you cannot debug remotely using asp.net 2.0. I suggest porting the site locally, get rid of the kinks then put it back on the remote server. Without any erros you should be able to preview the site.
cando
Member
25 Points
5 Posts
Re: Server Error in "/" Application
Jun 10, 2005 04:23 PM|LINK
Make sure you are not getting a starter kit for asp.net 2.0 beta1 and trying to run it as a asp.net beta 2 starter kit.
cd2582
Member
35 Points
7 Posts
new error: Server Error in '/DotNetNuke/admin' Application
Jun 10, 2005 08:17 PM|LINK
Server Error in '/DotNetNuke/admin' 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".
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.
fteng
Member
5 Points
1 Post
Re: Server Error in "/" Application
Jun 13, 2005 03:41 AM|LINK
1. Copy and paste the text of the error into the web.config file so that the file only has this in it.
<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>2. Rename the Web.Config file in the root of the application folder to web.config (case sensitive). My application is in the public/abc folder so I would put the web.config file there. It does not need to go into the /public folder or the / folder.Voila. I hope this helps.
vsureshvarma
Member
40 Points
21 Posts
Re: Server Error in "/" Application
Apr 30, 2009 11:12 AM|LINK
Please Specify which version of IIS you r using..
If it is 5.1(i.e you r using XP) make shore u r application folder must be shared.
if UR using IIS 6.0 (u r OS ie 2003 server)
do following..
start--->run--->inetmgr--->ur system name--->expand it--->go to u r vertual directory--->right click ----->Permissions--->make shore to provide all Check boxes must be checked.
tan.
go to properties of u r vertual directory ASP.NETtab and see UR vertion of VS.NET
nareshprakas...
Participant
1396 Points
285 Posts
Re: Server Error in "/" Application
Apr 30, 2009 11:49 AM|LINK
add this line into your web.config. After write below code in your web.config then you will get actual error of your program.
<customErrors mode="off" ></customErrors >
web.config
Naresh Prakash.
Click Here : SKY IS NOT THE LIMIT
Don't forget to click "Mark as Answer" on the post that helped you.
This credits that member, earns you a point and mark your thread as Resolved for the sake of Future Readers.