Runtime Error

Printed From: Illyriad
Category: Strategies, Guides & Help
Forum Name: Technical Support
Forum Description: Post your technical support related questions here.
URL: http://forum.illyriad.co.uk/forum_posts.asp?TID=3033
Printed Date: 17 Apr 2022 at 00:52
Software Version: Web Wiz Forums 12.03 - http://www.webwizforums.com

Topic: Runtime Error

Posted By: Flint FireBlood
Subject: Runtime Error
Date Posted: 05 Jan 2012 at 22:51

i created an account through facebook a few days ago. now everytime i try to log in it redirects me to this page:

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>

now how do i fix this and log in? im not computer literate lol ive no idea how to log in now.

Replies:

Posted By: GM ThunderCat
Date Posted: 06 Jan 2012 at 05:00

This should now be resolved - Facebook would occasionally set a double cookie, which confused the authentication.

Equally closing your browser completely and reopening should sort it.