locked
How to fix this error? RRS feed

  • Question

  • I just logged in to my working machine and I am getting this error.

    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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

    How to fix this?


    Regards, Dilip Nayak, SharePoint Consultant

    Tuesday, June 28, 2016 3:05 PM

Answers

  • Set the custom error mode to remote only in your web.config file and try browsing the site again. you will get the detailed error with the stack trace. You can proceed from there.

    Regards,

    Farshid Mahdavipour, MCSE, PMP

    Blog: www.sharepointjunkies.com
    ---------------------------------------------------------------------
    Please don't forget to mark it as answered, if your problem resolved or helpful.

    • Marked as answer by Dilip Nayak Tuesday, June 28, 2016 3:20 PM
    Tuesday, June 28, 2016 3:09 PM

All replies

  • Set the custom error mode to remote only in your web.config file and try browsing the site again. you will get the detailed error with the stack trace. You can proceed from there.

    Regards,

    Farshid Mahdavipour, MCSE, PMP

    Blog: www.sharepointjunkies.com
    ---------------------------------------------------------------------
    Please don't forget to mark it as answered, if your problem resolved or helpful.

    • Marked as answer by Dilip Nayak Tuesday, June 28, 2016 3:20 PM
    Tuesday, June 28, 2016 3:09 PM
  • Got it, It gave me detailed error. SQL service was down I guess, my admin guy fixed it.

    Regards, Dilip Nayak, SharePoint Consultant

    Tuesday, June 28, 2016 3:20 PM