Search…

X3 Photo Gallery Support Forums

Search…
 
jonathanmizzi
Topic Author
Posts: 1
Joined: 08 Jun 2009, 20:40

Server Error in '/' Application!!! Help!

09 Jun 2009, 12:24

Hi all,

Every now and then when i make changes to my site I get the following error, i then have to wait a few minutes until i can re access my site, any ideas? Below is the error i get, i do not understand where this web.config file is either?

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".

<!-- 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>
 
User avatar
carter2
Experienced
Posts: 206
Joined: 13 Oct 2008, 13:00

09 Jun 2009, 18:03

My first port of call would be the host. As far as i can recall (It's been a while) web.config is tied in with asp.
 
User avatar
Nick
Imagevue Hitman
Posts: 2872
Joined: 02 May 2006, 09:13

10 Jun 2009, 01:28

Hmm yea, you need to contact your hoster first, atleast do as they say here so details of the error are visible. Then if you could provide rdp or ftp login we can try to find out what's wrong with it.
firedev.com