Rank: Newbie Groups: Member
Joined: 4/24/2010 Posts: 1 Points: 3 Location: Netherland
|
Hello all,
I just started installing Versadev, i am on it for two days now, no matter wat i do (i follow the guidelines and all of that) the following error keeps coming when i try to open the application in my Browser IE8 ( i have the program installed on a windows 2003 server with ISS V6 and Sqlserver 2005)
Server Error in '/versaSRS' 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.
Details: To enable the details of this specific error message to be viewable on the local server machine, 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 "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
<!-- Web.Config Configuration File -->
<configuration> <system.web> <customErrors mode="RemoteOnly"/> </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="On" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
I already made the suggested changes in the web.config file but it won't work. does anybody have the solution?
|
Rank: Advanced Member Groups: Member
Joined: 11/20/2008 Posts: 43 Points: 32 Location: Australia
|
Hi,
This error message doesn't say anything specific. If you make the change suggested in the error message and run it again a more specific error message should being returned.
The setting in the web.config file needs to be:
<configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
If you can run this and get the new error message I will take a look.
Cheers, Philip
|